|
PDF Available |
|
|
PDF Available |
Abstract
UF Computing & Networking Services coordinates domain name services for domain ufl.edu. Officialy advertised name servers are:
128.227.128.24 | name.ufl.edu |
128.227.128.254 | lower-name.server.ufl.edu |
128.6.224.82 | rutgers-name.server.ufl.edu |
<editor@cns.ufl.edu>Table of Contents
The Northeast Regional Data Center coordinates domain name services for domain ufl.edu. Officialy advertised name servers are:
128.227.128.24 | name.ufl.edu |
128.227.128.254 | lower-name.server.ufl.edu |
128.6.224.82 | rutgers-name.server.ufl.edu |
If you have a name server running bind and are capable of providing primary name service for your domain, CNS will delegate to you by domain and provide secondary name service. Check the list of currently allocated domain names at
http://nslog.cns.ufl.edu/ns/cgi-bin/domain-info.cgi.
If the domain name you want is not already taken, send e-mail to net-services@lists.ufl.edu to have your choice reserved. Create and activate a zone file with SOA.
Fill out the online form at:
http://nslog.cns.ufl.edu/ns/cgi-bin/domain-reg.cgi
Your SOA will be inspected and the delegation completed. Here is a sample SOA, with explanatory notes:
; Sample SOA for the domain foo.ufl.edu
;
@ in soa name.foo.ufl.edu. postmaster.foo.name.ufl.edu. (
199510171 ; serial in yyyymmddx format
900 ; refresh 15 minutes
400 ; retry 6.67 minutes
864000 ; expire 10 days
1800 ) ; minimum 30 minutes, see rfc 2308
;
; end of soa proper.
; define the mailing address for userid@foo.ufl.edu
;
in mx 10 mail.foo.ufl.edu.
;
; ns and glue records. At least 2 ns records are required.
; The glue records are needed to complete the additional
; information section of nameserver responses.
;
in ns name.foo.ufl.edu.
in ns name.ufl.edu.
name.foobar.ufl.edu. in a 205.129.63.11
;name.ufl.edu in a 128.227.128.24
;
;+end-soa+ (actually, the soa ends with the first )
:
What the serial and timer values do:
serial - A value used to indicate that the contents of the zone defined by the SOA have changed. Secondary name servers check the
serial number and transfer a new copy of the zone when a positive increment in the serial number is detected.
refresh - Secondary name servers check with the primary every refresh seconds. If the serial number has been incremented since the
previous check, the secondary obtains a new copy of the zone from the primary.
retry - If a refresh attempt fails it will be retried every retry seconds.
expire - The secondary nameservers will invalidate the zone after they have been unable to contact the primary for expire seconds. Expire
should be a large value, at least several days. Contrary to popular wisdom, there is no reason to have a short expire value. If you need to
insure that changes are introduced quickly, you need to set the mimimum ttl, or "minimum" value.
minimum - The default time to live value. This value is assigned to resources that do not have a time to live specified on the resource
definition. Answers sent by this nameserver contain time to live values and will commonly be kept by the questioner until expiration.
Minimum is kept fairly small so that changes can be introduced. Note that with rfc 2308 and bind 8.2, this value is the default negative
cache time and the $TTL directive is used to set the default time for positive caches.If you cannot provide your own primary domain name service, CNS will provide a minimum level for you. Minimum services include forward and reverse name resolution. A mail-exchange record will be defined if necessary. An alias for a web server or gopher server will be provided if necessary. An alias (cname) record cannot implicitly create a new domain.
If you wish to remove/discontinue an existing subdomain under your jurisdiction, it is important that you notify net-services@lists.ufl.edu at the earliest possible date, to prevent the generation of unnecessary alerts, alarms, and trouble-reports. Coordination between net-services@lists.ufl.edu and the various subdomains is essential to ensure smooth operations for all users.
It is important for network managers to notify <net-services@lists.ufl.edu> prior to changing the IP address of any name server. Neglecting to do this may result in bounced e-mail and/or other failures of network services.
Coordination between <net-services@lists.ufl.edu> and the various subdomains is essential to ensure smooth operations for all users.
The class A IP network 10.0.0 is used for resources within ufl.edu that do not need to be directly addressable to the entire Internet all the time. An address translation device (PIX) provides for global
addressing on an as needed basis for resources within this space. See http://www.faqs.org/rfcs/rfc1918.html for more information about the private IP address space. See
http://net-services.ufl.edu/provided_services/vpn/vpn-faq.html for information about the implementation of the private address space at ufl.edu .
Class B or C subnets within the private address space are delegated to groups, departments and organizations within the University community.
The primary nameserver for the reverse mapping for network 10 is name.ufl.edu at ip address 128.227.128.24. To correctly resolve reverse pointers in network 10, each DNS nameserver within ufl.edu must include a
secondary statement for 10.in-addr.arpa.
We welcome your comments and suggestions on this and all CNS documentation. Please send your comments to:
UF Computing & Networking Services
112 Bryant Space Sciences Bldg, University of Florida