DNS changes at Rutgers

DNS changes at Rutgers

As of May 28, 2001, Rutgers is presenting two views of our DNS space. This is being done so we can use private address space which must not be advertised to the rest of the Internet. RUCS/TD has provided a list of DNS servers they have historically maintained and what information they will now provide. They also have a list of recommended servers for use within the University for the general Rutgers community.

What does this mean to LCSR users?

It should not make any difference to you if your machine is already properly configured. Here is what you should check:

If you are dialing into Rutgers, you should be looking at the inside view of our DNS. We recommend that DCS/LCSR users continue to use 128.6.4.4 (ns-lcsr, our private DNS server). This is probably how you are already configured. For second or third servers, you should specify the IP addresses recommended by RUCS/TD (currently, 128.6.224.114 and 128.6.216.19).

If you have an ISP outside Rutgers, (ie, you have a cable modem, DSL, or dial into a commercial service), you should be looking at the outside view of our DNS. You should not be using Rutgers DNS servers for this view. (While Rutgers outside servers will give you the outside view of Rutgers DNS, they will not provide any information for non-Rutgers DNS. Rutgers inside servers will no longer be providing any information to any non-outside Rutgers hosts.) You should be using the DNS servers recommended (and provided) by your ISP. They will in turn only see Rutgers outside view.

You can confirm which view you are using by trying to access (eg, ping or telnet to) either inside.rutgers.edu or outside.rutgers.edu. The hosts inside and outside are only visible in the inside and outside views, respectively.

See also:

Note: The above pages may appear to recommend different IP addresses than this page recommends for LCSR users. Any of the recommended IP addresses should work properly. Different ones are recommended for different network locations to balance load and for network proximity.
This page last updated January 29, 2004.