Change DNS seetings on all DataONE VMs
We've transitioned to using the Amazon Route 53 service as the authoritative name servers for the dataone.org domain, and need to configure each development and production VM to point to the appropriate servers (no longer the nceas name servers), and to the Google servers as secondaries:
On UCSB VMs, modify /etc/network/interfaces to point to the following name servers:
dns-nameservers 126.96.36.199 188.8.131.52 184.108.40.206 220.127.116.11
(ns2.ucsb.edu, ns1.ucsb.edu, google-public-dns-a.google.com, google-public-dns-b.google.com)
On ORC VMs, modify /etc/network/interfaces to point to the following name servers:
dns-nameservers 18.104.22.168 22.214.171.124 126.96.36.199 188.8.131.52
(ns2.utk.edu, ns1.utk.edu, google-public-dns-a.google.com, google-public-dns-b.google.com)
On UNM VMs, modify /etc/network/interfaces to point to the following name servers:
dns-nameservers 184.108.40.206 220.127.116.11 18.104.22.168 22.214.171.124
(ns2.unm.edu, ns1.unm.edu, google-public-dns-a.google.com, google-public-dns-b.google.com)
Per Nick Brand, putting the per-campus name servers first should give us the lowest latency.
#1 Updated by Dave Vieglais over 8 years ago
DNS looks are locally cached and unless forced, a call to a DNS server is typically not made until the TTL expires.
The Google DNS servers are widely used and so notice of any changes to those services are likely to be widely advertised. A change to a campus DNS server may be advertised, but seems less reliable (e.g. recent migration of NCEAS DNS to a network that does not allow external access).
The Amazon servers are not recursive DNS servers and so should not be targeted for general DNS queries.
Suggest using the Google DNS as the primary DNS and fallback to OpenDNS servers (http://www.opendns.com/opendns-ip-addresses/)