Header Search Widget
IRIS

Instructional & Research Information Systems

DNS

Domain Name Service

Update to nameservers, NTP servers

by

We have maintained our own recursive nameservers within EECS for many years, enabling client machines to resolve hostnames to IP addresses. These servers also functioned as local NTP (time) servers. In the spirit of simplification, we are retiring these machines and will be utilizing campus servers for these services.

Effective immediately, we are updating our DHCP configuration, to point clients instead to campus nameservers ns1.berkeley.edu (128.32.136.9 and 128.32.206.9) and ns2.berkeley.edu (128.32.136.12 and 128.32.206.12). We are similarly updating the setting for NTP servers, pointing to campus NTP servers ntp1.net.berkeley.edu and ntp2.net.berkeley.edu.

Most machines in EECS are DHCP clients, and will pick up these changes automatically.

If you have statically configured nameservers or NTP servers on your systems, please update your configuration as soon as possible.

DNS disruption for eecs.berkeley.edu, Nov 19

by

Tuesday afternoon and evening, November 19, we had a disruption of DNS resolution for the eecs.berkeley.edu domain on the campus nameservers. This meant that many systems outside of the EECS network were temporarily unable to resolve *.eecs.berkeley.edu hostnames — so people may have been temporarily unable to reach EECS websites or deliver email to some @eecs.berkeley.edu addresses.

[Read more…] about DNS disruption for eecs.berkeley.edu, Nov 19

New DNS Nameserver: themis.eecs

by

System administrators in EECS may be familiar with our DNS nameservers cronus and rhea. We now have a new nameserver, physically located in Cory Hall, named themis. If your systems are typical DHCP clients, or you don’t use the EECS wired network, then you should have nothing to change.

We are planning to replace and retire rhea according to the following schedule:

  • Thu Oct 15 — We will update our DHCP configuration, telling Cory Hall DHCP clients to use themis and cronus, and telling other DHCP clients to use cronus and themis.
  • November/December — We will monitor any continued usage of rhea for DNS, and periodically alert system administrators so they can update their systems to use themis instead.
  • early January — We will retire rhea, but will point its name and IP address at cronus.