Need I say more? More than half of them are running at least a day old, and the majority of those are running two days old. kate$ dig @a.root-servers.net SOA com. | grep serial 1998091500 ; serial kate$ dig @b.root-servers.net SOA com. | grep serial 1998091500 ; serial kate$ dig @c.root-servers.net SOA com. | grep serial 1998091300 ; serial kate$ dig @d.root-servers.net SOA com. | grep serial 1998091400 ; serial kate$ dig @e.root-servers.net SOA com. | grep serial 1998091300 ; serial kate$ dig @f.root-servers.net SOA com. | grep serial 1998091300 ; serial kate$ dig @g.root-servers.net SOA com. | grep serial 1998091300 ; serial kate$ dig @h.root-servers.net SOA com. | grep serial 1998091500 ; serial kate$ dig @i.root-servers.net SOA com. | grep serial 1998091300 ; serial kate$ dig @j.gtld-servers.net SOA com. | grep serial 1998091500 ; serial kate$ dig @k.gtld-servers.net SOA com. | grep serial 1998091300 ; serial Paul -- Paul Thornton Office Tel: +44 1733 705000 London Internet Exchange www.linx.net Mobile: +44 467 372205
It happens. This is pretty common. It's when they go three-plus days old that you have to worry. Paul Thornton wrote:
From errors-nohumans@merit.edu Wed Sep 16 03:46:12 1998 X-NCC-RegID: uk.linx Date: Wed, 16 Sep 1998 09:37:55 +0100 (BST) From: Paul Thornton <prt@linx.net> To: nanog@merit.edu Subject: COM zone and serials Message-ID: <Pine.GSO.3.93.980916093352.27961B-100000@london.linx.net> Sender: owner-nanog@merit.edu
Need I say more? More than half of them are running at least a day old, and the majority of those are running two days old.
kate$ dig @a.root-servers.net SOA com. | grep serial 1998091500 ; serial kate$ dig @b.root-servers.net SOA com. | grep serial 1998091500 ; serial kate$ dig @c.root-servers.net SOA com. | grep serial 1998091300 ; serial kate$ dig @d.root-servers.net SOA com. | grep serial 1998091400 ; serial kate$ dig @e.root-servers.net SOA com. | grep serial 1998091300 ; serial kate$ dig @f.root-servers.net SOA com. | grep serial 1998091300 ; serial kate$ dig @g.root-servers.net SOA com. | grep serial 1998091300 ; serial kate$ dig @h.root-servers.net SOA com. | grep serial 1998091500 ; serial kate$ dig @i.root-servers.net SOA com. | grep serial 1998091300 ; serial kate$ dig @j.gtld-servers.net SOA com. | grep serial 1998091500 ; serial kate$ dig @k.gtld-servers.net SOA com. | grep serial 1998091300 ; serial
Paul
-- Paul Thornton Office Tel: +44 1733 705000 London Internet Exchange www.linx.net Mobile: +44 467 372205
-- jamie rishaw (efnet:gavroche) American Information Systems, Inc. Tel:312.425.7140, FAX:312.425.7240 Help stop spam! router(config)#no ip routing thirty thousand feet above the earth..youre a beautiful thing..
a friend called the nic yesterday to find out why an update hadn't gone through and was told that the nic had a major database meltdown (or words to that effect). at that point it had been 17 hours since anything had been processed. i this is a correct report from the nic (i can't see them lying about this :-), then i doubt the zone files got updated either.
[ On Wed, September 16, 1998 at 09:37:55 (+0100), Paul Thornton wrote: ]
Subject: COM zone and serials
Need I say more? More than half of them are running at least a day old, and the majority of those are running two days old.
kate$ dig @a.root-servers.net SOA com. | grep serial 1998091500 ; serial [[... and on and on with many similar commands ...]]
FYI the host(1) command offers a MUCH simpler way of checking these sorts of things. Just a single command, and a single option "host -C zone" (or add '-u' to do the query/queries with TCP). IMNSHO host(1) is far easier to use, and far more versatile, than any other DNS query tool. The latest version of host(1) can always be found here: ftp://ftp.nikhef.nl/pub/network/host.tar.Z 14:44 [1292] $ host -C com. com NS H.ROOT-SERVERS.NET A.ROOT-SERVERS.NET hostmaster.INTERNIC.NET (1998091500 1800 900 604800 86400) com NS B.ROOT-SERVERS.NET A.ROOT-SERVERS.NET hostmaster.INTERNIC.NET (1998091500 1800 900 604800 86400) com NS C.ROOT-SERVERS.NET A.ROOT-SERVERS.NET hostmaster.INTERNIC.NET (1998091300 1800 900 604800 86400) !!! C.ROOT-SERVERS.NET and B.ROOT-SERVERS.NET have different serial for com com NS D.ROOT-SERVERS.NET A.ROOT-SERVERS.NET hostmaster.INTERNIC.NET (1998091500 1800 900 604800 86400) !!! D.ROOT-SERVERS.NET and C.ROOT-SERVERS.NET have different serial for com com NS E.ROOT-SERVERS.NET A.ROOT-SERVERS.NET hostmaster.INTERNIC.NET (1998091500 1800 900 604800 86400) com NS I.ROOT-SERVERS.NET A.ROOT-SERVERS.NET hostmaster.INTERNIC.NET (1998091500 1800 900 604800 86400) com NS F.ROOT-SERVERS.NET A.ROOT-SERVERS.NET hostmaster.INTERNIC.NET (1998091300 1800 900 604800 86400) !!! F.ROOT-SERVERS.NET and I.ROOT-SERVERS.NET have different serial for com com NS G.ROOT-SERVERS.NET A.ROOT-SERVERS.NET hostmaster.INTERNIC.NET (1998091500 1800 900 604800 86400) !!! G.ROOT-SERVERS.NET and F.ROOT-SERVERS.NET have different serial for com com NS J.GTLD-SERVERS.NET A.ROOT-SERVERS.NET hostmaster.INTERNIC.NET (1998091500 1800 900 604800 86400) com NS K.GTLD-SERVERS.NET Nameserver K.GTLD-SERVERS.NET not responding com SOA record not found at K.GTLD-SERVERS.NET, try again com NS A.ROOT-SERVERS.NET A.ROOT-SERVERS.NET hostmaster.INTERNIC.NET (1998091500 1800 900 604800 86400) -- Greg A. Woods +1 416 218-0098 VE3TCP <gwoods@acm.org> <robohack!woods> Planix, Inc. <woods@planix.com>; Secrets of the Weird <woods@weird.com>
FYI the host(1) command offers a MUCH simpler way of checking these sorts of things. Just a single command, and a single option "host -C zone" (or add '-u' to do the query/queries with TCP). IMNSHO host(1) is far easier to use, and far more versatile, than any other DNS query tool.
The latest version of host(1) can always be found here:
ftp://ftp.nikhef.nl/pub/network/host.tar.Z
Namespace collision! ftp.nikhef.nl has versions of programs that are very similar to "canonical" distributions but are different in option syntax and features. Usually somewhat more featureful, but not always. For instance, traceroute that differs from the canonical version (ftp.ee.lbl.gov). "host" that differs from any of the canonical versions (like that distributed with bind), etc., etc. I think promulgating their usage as long as they conflict in name with more popular versions of the same programs is A Poor Idea. --jhawk
[ On Wed, September 16, 1998 at 20:11:28 (-0400), John Hawkinson wrote: ]
Subject: Re: COM zone and serials
For instance, traceroute that differs from the canonical version (ftp.ee.lbl.gov).
Although the verions of traceroute at ftp.ee.lbl.gov may be the root of all traceroutes, I'd never consider it to be the most portable one. That said though I must admit I've stopped using Eric's version of traceroute in favour of the version that comes with NetBSD. However in the days I was still using SunOS-4 on my primary server(s), Eric's version was enormously better than the LBL version, and much easier to get working.
"host" that differs from any of the canonical versions (like that distributed with bind), etc., etc.
I think you'll find the 'host' in the "tools" sub-directory of the BIND distribution is an extremely ancient predecessor to the version Eric maintains and that the one in the "contrib/host" sub-directory is in fact a slightly out-of-date version of Eric's host(1). I.e. Eric's host(1) *is* the "canonical" version.
I think promulgating their usage as long as they conflict in name with more popular versions of the same programs is A Poor Idea.
What you call a "canonical" version simply may be the "original predecessor". Even I maintain and distribute enhanced versions of programs that originally came from elsewhere (eg. fingerd, newsyslog, etc.). I rarely, if ever, change their names (though usually I give the distribution tar archive a different version name :-). "Use what works. Use what works best." -- Greg A. Woods +1 416 218-0098 VE3TCP <gwoods@acm.org> <robohack!woods> Planix, Inc. <woods@planix.com>; Secrets of the Weird <woods@weird.com>
participants (5)
-
jamie＠dilbert.ais.net -
Joe Pruett -
John Hawkinson -
Paul Thornton -
woods＠most.weird.com