[4] in North American Network Operators' Group
broken glue in .net domain
daemon@ATHENA.MIT.EDU (Michael Dillon)
Wed Jul 19 18:29:28 1995
Date: Wed, 19 Jul 1995 15:29:48 -0700 (PDT)
From: Michael Dillon <michael@memra.com>
To: nanog@merit.edu
We are attempting to get the Internic to change our secondary nameserver
for the junction.net domain but not having much luck. Our change requests
for in-addr.arpa went through in a few days. But the Internic rejected
the first request saying we needed to use a new form. So we resubmitted
but it is now almost two weeks ago. What is the point of a new form if we
cannot get things updated any faster?
Then we noticed that DNS to our new secondary nameserver ns2.bc.net was
acting wierd. So we dug into the .net domain and discovered several A
records with the WRONG IP ADDRESS. I don't know whether it was a typing
error at the Internic or whether somebody at BC.NET screwed up, but why
do changes like this take so long if nobody even verifies such a simple
and obvious thing?
You can see this by trying the whois command on sno.net, infoserve.net or
concordpacific.net Compare the IP address for ns2.bc.net with the one
given by nslookup when talking to an authoratative server for the domain
like jade.bc.net
In addition there is at least one glue record for ns1.bc.net which
erroneously reports its IP address to be 128.198.4.1 which is also wrong
since ns1 is the same as jade.bc.net
Michael Dillon Voice: +1-604-546-8022
Memra Software Inc. Fax: +1-604-542-4130
http://www.memra.com E-mail: michael@memra.com
michael@junction.net
