You have been redirected to this page because you are using a retired DNS server. Below are instructions to correct this problem by updating your DNS server references.
DNS / DHCP / NTP Migration
Domain Name System (DNS), Dynamic Host Configuration Protocol (DHCP) and Network Time Protocol (NTP) Campus services that are provided by Computing and Networking Services (CNS) are migrating to the new BlueCat platform. This new platform gives CNS extended functionality as well as new hardware to replace aging servers. Below you will find detailed information about each service and what the migration means to you.
If after reading this document you still have questions and/or comments please send an email to cns-dcns-l@lists.ufl.edu or call Data Center and Network Support at (352) 273-1363.
Domain Name System (DNS)
This service will be the most involved of the migrations and as such will take the longest to complete. Please select one of the following to view the required changes.
What does DNS migration mean to me?
Your DNS settings are set automatically with DHCP
Please see the section below titled "Dynamic Host Configuration Protocol (DHCP)".
You administer your own computer
If you currently resolve DNS using any of these UF Name Servers:
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)
128.227.128.11 (hai-dns.cns.ufl.edu)
You will need to change to these UF Name Servers:
128.227.30.254 (ns.name.ufl.edu)*
8.6.245.30 (rns.name.ufl.edu)
* Although this is only one IP address, using Anycast there are currently two Servers (more to be added in the future) that can answer your request.
You administer computers in a Group or Department
If you currently resolve DNS using any of these UF Name Servers on any computer:
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)
128.227.128.11 (hai-dns.cns.ufl.edu)
You will need to change to these UF Name Servers:
128.227.30.254 (ns.name.ufl.edu)*
8.6.245.30 (rns.name.ufl.edu)
* Although this is only one IP address, using Anycast there are currently two Servers (more to be added in the future) that can answer your request.
You administer servers in the Data Center
If you currently resolve DNS using any of these UF Name Servers:
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)
128.227.128.11 (hai-dns.cns.ufl.edu)
You will need to change to these UF Name Servers:
128.227.30.254 (ns.name.ufl.edu)*
8.6.245.30 (rns.name.ufl.edu)
* Although this is only one IP address, using Anycast there are currently two Servers (more to be added in the future) that can answer your request.
If you use NTP on your servers please see the section below titled "Network Time Protocol (NTP)".
You have an external domain that references UF Name Servers
If you have an external domain (i.e. facts.org, wuft.tv, ufadventures.com, etc.) that references any of the following UF Name Servers:
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)
You will need to contact your registrar and change the listed DNS Servers to these UF Name Servers:
128.227.30.254 (ns.name.ufl.edu)*
8.6.245.30 (rns.name.ufl.edu)
* Although this is only one IP address, using Anycast there are currently two Servers (more to be added in the future) that can answer your request.
You or your Department run their own Name Server
If any of your Name Server's Zones are reliant on any of the main UF Name Servers (i.e. your Name Server is running as a stealth/hidden master and UF's Name Servers are the primary or we have delegated a Zone to your Name Server and UF is a secondary/slave) then this migration pertains to you.
If you have an external domain (i.e. facts.org, wuft.tv, ufadventures.com, etc.) hosted on your Name Server that references UF Name Servers please see the section "You have an external domain that references UF Name Servers" for any changes that are necessary.
Zone Files
In your Zone files, if you reference any of these UF Name Servers as NS statements:
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)
The references will need to be changed to these UF Name Servers:
128.227.30.254 (ns.name.ufl.edu)*
8.6.245.30 (rns.name.ufl.edu)
* Although this is only one IP address, using Anycast there are currently two Servers (more to be added in the future) that can answer your request.
Zone Transfers
Because we are using Anycast, multiple servers will need to be allowed to initiate Zone transfers. Some of the new servers listed below are not in service right now but adding them should not cause a problem and it will alleviate changes in the future.
Remove Zone transfer authorization from these UF Name Servers:
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)
Allow Zone transfers from these UF Name Servers:
128.227.30.234 (ns1.name.ufl.edu)*
128.227.30.238 (ns2.name.ufl.edu)*
128.227.30.242 (ns3.name.ufl.edu)*
128.227.30.246 (ns4.name.ufl.edu)*
8.6.245.30 (rns.name.ufl.edu)
* Please do not add these name/addresses as NS records in your Zones files.
Also Notify
As you make changes to your Zones, notifications are sent to all Name Servers listed in that Zone file. rns.name.ufl.edu (8.6.245.30) is notified as it is a single server with a single IP address. That is not the case with the Anycast address, ns.name.ufl.edu (128.227.30.254). Only one server in the Anycast group will get the notify. Because of this we need to notify all servers in the Anycast group.
Please make sure these Name Servers get notified for Zone changes:
128.227.30.234 (ns1.name.ufl.edu)*
128.227.30.238 (ns2.name.ufl.edu)*
128.227.30.242 (ns3.name.ufl.edu)*
128.227.30.246 (ns4.name.ufl.edu)*
8.6.245.30 (rns.name.ufl.edu)
* Please do not add these name/addresses as NS records in your Zones files.
For example, in BIND you would add this line in your Zone definition:
also-notify { 128.227.30.234; 128.227.30.238; 128.227.30.242; 128.227.30.246;};
If you have questions and/or comments on any section in this topic please contact us via the information given above.
Dynamic Host Configuration Protocol (DHCP)
Changing DHCP configurations should be straight forward and will be one of the easiest to migrate. Please select one of the following to view the required changes.
What does DHCP migration mean to me?
You use the CNS managed DHCP Server
If you use the CNS managed DHCP Server all changes necessary for this migration will be done for you. Beginning in late February 2012, we will start migrating current DHCP pools to the BlueCat platform. With this migration we will gain failover (peering) capability giving us the ability to ride though a single server failure (hardware or network).
You run your own DHCP Server
If you use the 'option domain-name-servers' statement in your DHCP configuration that references any of the following UF Name Servers:
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)
You will need to change that option to reference these UF Name Servers:
128.227.30.254 (ns.name.ufl.edu)*
8.6.245.30 (rns.name.ufl.edu)
* Although this is only one IP address, using Anycast there are currently two Servers (more to be added in the future) that can answer your request.
If you use the 'option time-servers' statement in your DHCP configuration please see the section below titled "Network Time Protocol (NTP)"
Network Time Protocol (NTP)
NTP can be setup manually or automatically via DHCP. Below are the changes that are necessary.
What does NTP migration mean to me?
If in your NTP configuration you reference any of the following UF NTP Servers:
128.227.128.24 (name.ufl.edu)
128.227.128.254 (lower-name.server.ufl.edu)
You will need to change to these UF NTP Servers:
128.227.30.234 (ns1.name.ufl.edu)
128.227.30.238 (ns2.name.ufl.edu)
If you happen to be using any of these NTP Servers:
ntps2-1.server.ufl.edu
ntps2-2.server.ufl.edu
ntps3-1.nerdc.ufl.edu
ntps3-2.nerdc.ufl.edu
As these are aliases to the Servers mentioned above, we will change the underlying DNS records and no changes will be needed by you.
Time frame to complete these Migrations
Below are the sunset dates for these services on the old CNS Servers. Please start these migrations at your earliest convenience. Do not wait until the last minute as you run the risk of your services failing. We do not expect these migrations to take until the sunset dates to complete but we understand what we are asking you to do and want to give everyone ample time to complete it. We will be sending out reminders at key intervals during these periods.
DHCP
CNS will be completed with our DHCP migration on March 25th, 2012. After that date we will discontinue our current DHCP service on lower-name.server.ufl.edu.
If you are running your own DHCP server, the necessary changes are tied to the NTP and DNS migrations and as such need to be completed by the dates listed below.
NTP
This migration should be completed no later than Sunday April 7th, 2013.
DNS
The DNS migration will be the most involved of the three and will take the longest to complete. Please start your DNS migration as soon as you can. This migration should be completed no later than Sunday April 7th, 2013.