home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.sysv386
- Path: sparky!uunet!ihz.compuserve.com!sam
- From: sam@csi.compuserve.com (Sam Neely)
- Subject: Re: Names no longer being seen (gethostbyname stops) with ISC 2.2.1
- Message-ID: <BxuB4q.GtC@csi.compuserve.com>
- Organization: CompuServe Incorporated
- References: <JTSILLA.92Nov15221020@damon.ccs.northeastern.edu> <Bxsso5.3sF@csi.compuserve.com> <BxtKzH.IL8@gator.rn.com>
- Date: Tue, 17 Nov 1992 03:02:49 GMT
- Lines: 66
-
- In article <BxtKzH.IL8@gator.rn.com> larry@gator.rn.com (Larry Snyder) writes:
- >sam@csi.compuserve.com (Sam Neely) writes:
- >
- >>Now that I've got that off my chest... My guess is that you changed
- >>your nameserver information when you updated sendmail. Check out
- >>what you've got in /etc/resolv.conf. If that looks kosher, make
- >>sure you've got a route to the nameserver(s) with netstat -nr.
- >
- >I'm using uunet for my nameserver as defined in /etc/resolv.conf --
- >how long before entries to uunet's namesever are shared around the
- >world with the various other nameservers?
-
- Gee, that's a little out of the scope of the original question, but
- what the heck, I'll give it a shot...
-
- Here is the SOA record for rn.com from uunet(ns.uu.net):
-
- rn.com 172800 IN SOA ns.UU.NET hostmaster.uunet.UU.NET(
- 921112 ;serial (version)
- 432000 ;refresh period
- 3600 ;retry refresh this often
- 864000 ;expiration period
- 172800 ;minimum TTL
- )
- rn.com 172800 IN NS ns.UU.NET
- rn.com 172800 IN NS uucp-gw-1.pa.DEC.COM
- rn.com 172800 IN NS uucp-gw-2.pa.DEC.COM
- rn.com 172800 IN NS ns.EU.net
- rn.com 172800 IN NS ns1.RUTGERS.EDU
- rn.com 172800 IN MX 200 relay1.UU.NET
- rn.com 172800 IN MX 200 relay2.UU.NET
- Additional information:
- ns.UU.NET 172800 IN A 137.39.1.3
- uucp-gw-1.pa.DEC.COM 133836 IN A 16.1.0.18
- uucp-gw-2.pa.DEC.COM 47487 IN A 16.1.0.19
- ns.EU.net 86400 IN A 192.16.202.11
- ns1.RUTGERS.EDU 133859 IN A 128.6.21.6
- relay1.UU.NET 172800 IN A 137.39.1.5
- relay1.UU.NET 172800 IN A 192.48.96.5
- relay2.UU.NET 172800 IN A 137.39.1.7
- relay2.UU.NET 172800 IN A 192.48.96.7
-
- The SOA record for rn.com at uunet has a serial number of 921112, which
- by convention means that an update was performed on 12-Nov-92. The
- refresh period is set to 432000 seconds, which means the secondary
- nameservers will check every 5 days with the master specified in the
- boot file. (uucp-gw-1.pa.dec.com and uucp-gw-2.pa.dec.com have
- already expired and pulled serial number 921112 down. ns.eu.net and
- ns1.rutgers.edu have not and are still running with serial 921109.)
-
- The minimum time to live is set to 172800 seconds, which means that
- any record that is cached in any nameserver around the world will
- remained cached for 2 days. After that, it will go back to one of the
- nameservers for an update. If it goes to ns.uu.net, or one of the two
- dec.com sites, it will get the newest information. If it goes to
- ns.eu.net or ns1.rutgers.edu, it will get the slightly stale
- information.
-
- In theory, your nameserver info at rutgers and eu.net will time out
- Real Soon Now, and current data will be sucked off of the nameserver
- at uunet, assuming that's how your secondaries get the information.
- --
- Sam Neely, CompuServe Incorporated +1 614 457 8600 (voice)
- 5000 Arlington Centre Blvd, Columbus, OH 43220 +1 614 457 0348 (FAX)
- Electronic Mail: InfoPlex: >CSI:SAM Internet: SAM@CSI.COMPUSERVE.COM
- To err is human, to forgive is against company policy
-