To:
Harald Alvestrand <Harald@Alvestrand.no>
cc:
dnsop@cafax.se
From:
Robert Elz <kre@munnari.OZ.AU>
Date:
Thu, 08 Feb 2001 16:39:32 +0700
In-reply-to:
Your message of "Thu, 08 Feb 2001 10:14:44 +0100." <4.3.2.7.2.20010208101137.03eeb500@127.0.0.1>
Sender:
owner-dnsop@cafax.se
Subject:
Re: Bogus nic.fr behavior
Date: Thu, 08 Feb 2001 10:14:44 +0100 From: Harald Alvestrand <Harald@Alvestrand.no> Message-ID: <4.3.2.7.2.20010208101137.03eeb500@127.0.0.1> | incompetence is not limited to the registrant side of that relationship... No, of course not. In fact, while one would hope that the people who run the root would have something of a clue, it seems not. Someone apparently made a typo in specifying the glue record for one of the TLDs hosted by a fairly major server in AU - gave the address of a different server instead. Not checked apparently, and sitting there now in the root servers giving out bad information... That wouldn't be so bad of itself, everyone makes mistakes from time to time - but it seems impossible to get anyone in any way responsible for the root servers to do anything about it - neither going through the proper channels, nor attempting some back door approaches (via a few people who have tried their best, and thanks to them). And just in case someone from the root servers is watching, the address that needs fixing if for yarrina.connect.com.au - it should end in "17" not "33" (just check with any of the AU servers - or with that server itself, using either of the possible addresses). And for the future, stick nothing in the root zone file without verifying it with the authoritative servers for the information to be inserted (which should be a rule to apply to all zones). kre ps: if this sounds a bit like my reply to Jerry suggested could be done to his servers, well, now you know where the inspiration came from...