DNS servers for the Nevis particle-physics groups

A DNS resolver or server is a system that's queried to translate an IP name (like mail.nevis.columbia.edu) into an IP address (like For the most part, you don't have to worry about this; the DNS servers have been configured for you on the Linux cluster systems, and laptops automatically pick up this information via DHCP. If you have a system (e.g., a computerized oscilloscope) for which it's useful to manually configure the DNS servers, here are the details.

For a system on the public network, a good set of DNS resolvers is:
This list is our secondary DNS server, our primary DNS server, and the main CU DNS server to act as backup.

For a system on the private network, use:
For a system on Columbia campus, you probably want:
This list is CU's primary DNS server, their secondary DNS server, and a backup Columbia DNS server maintained at the University of Michigan.

For laptops at Nevis, do NOT put in specific DNS servers; let our DHCP servers supply them for you. This is because the IP addresses of some of our systems change if you switch between our wired and wireless networks.

If you have device that only connects via wireless that you carry outside CU or Nevis, you may want to consider using Google's DNS servers:
or OpenDNS, which has a reputation for maintaining additional security features:
Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r2 - 2014-09-25 - WilliamSeligman
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback