DNS anomaly

Roger Keays r.keays at ninthave.net
Wed Jul 23 23:23:42 UTC 2003


Thanks again for your time.

>The problem may be that there are no glue records for
>[abcd].ns.ninthave.net, because the delegation has different nameservers
>(it's delegated to [abcd].ns.bytemark.co.uk).
>  
>
There *are* glue records in [abcd].ns.bytemark.co.uk (see below).

I'm doubly confused as the problem only seems to occur on Telstra DNS 
servers, and triply confused because the domain counsel.com.au which has 
almost identical configuration and the same nameservers works fine (even 
with Telstra servers).

Aside: the machines [abcd].ns.ninthave.net & [abcd].ns.bytemark.co.uk 
have the same IP.

Cheers,

Roger

$ dig @a.ns.bytemark.co.uk ninthave.net any

<snip>
;; ADDITIONAL SECTION:
a.ns.ninthave.net.      259200  IN      A       194.153.169.15
b.ns.ninthave.net.      259200  IN      A       194.153.169.31
c.ns.ninthave.net.      259200  IN      A       212.100.225.215
d.ns.ninthave.net.      259200  IN      A       212.13.198.12
</snip>

>Barry Margolin
>Level(3), Woburn, MA 
>
>  
>
>>-----Original Message-----
>>From: Roger Keays [mailto:r.keays at ninthave.net] 
>>Sent: Wednesday, July 23, 2003 6:00 PM
>>Cc: Margolin, Barry
>>Subject: Re: DNS anomaly
>>
>>
>>Barry,
>>
>>Thanks for the reply,
>>
>>    
>>
>>>I think 61.9.208.24 may have more general routing problems. 
>>>      
>>>
>> I can't get a
>>    
>>
>>>response from it for either query.  And when I traceroute to it, I
>>>encounter a routing loop between a pair of 192.168 addresses.
>>>      
>>>
>>Hmmm... I am now also getting no responses from that server, 
>>although it 
>>is the address that the Telstra support gave me. The servers on their 
>>web site are 139.134.5.51 and 139.134.2.190 which exhibit the 
>>behaviour 
>>from my first post:
>>
>>*** Telstra DNS ***
>>roger at schema:/home/roger$ dig ninthave.net @139.134.5.51 any
>>
>>; <<>> DiG 9.2.2 <<>> ninthave.net @139.134.5.51 any
>>;; global options:  printcmd
>>;; Got answer:
>>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46909
>>;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 4, ADDITIONAL: 0
>>
>>;; QUESTION SECTION:
>>;ninthave.net.                  IN      ANY
>>
>>;; ANSWER SECTION:
>>ninthave.net.           33556   IN      NS      a.ns.ninthave.net.
>>ninthave.net.           33556   IN      NS      b.ns.ninthave.net.
>>ninthave.net.           33556   IN      NS      c.ns.ninthave.net.
>>ninthave.net.           33556   IN      NS      d.ns.ninthave.net.
>>
>>;; AUTHORITY SECTION:
>>ninthave.net.           33556   IN      NS      a.ns.ninthave.net.
>>ninthave.net.           33556   IN      NS      b.ns.ninthave.net.
>>ninthave.net.           33556   IN      NS      c.ns.ninthave.net.
>>ninthave.net.           33556   IN      NS      d.ns.ninthave.net.
>>
>>;; Query time: 20 msec
>>;; SERVER: 139.134.5.51#53(139.134.5.51)
>>;; WHEN: Thu Jul 24 07:28:51 2003
>>;; MSG SIZE  rcvd: 153
>>
>>*** Optus DNS ***
>>roger at schema:/home/roger$ dig ninthave.net @203.2.75.132 any
>>
>>; <<>> DiG 9.2.2 <<>> ninthave.net @203.2.75.132 any
>>;; global options:  printcmd
>>;; Got answer:
>>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32326
>>;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 4, ADDITIONAL: 4
>>
>>;; QUESTION SECTION:
>>;ninthave.net.                  IN      ANY
>>
>>;; ANSWER SECTION:
>>ninthave.net.           189946  IN      NS      c.ns.ninthave.net.
>>ninthave.net.           189946  IN      NS      d.ns.ninthave.net.
>>ninthave.net.           189946  IN      NS      a.ns.ninthave.net.
>>ninthave.net.           189946  IN      NS      b.ns.ninthave.net.
>>
>>;; AUTHORITY SECTION:
>>ninthave.net.           189946  IN      NS      a.ns.ninthave.net.
>>ninthave.net.           189946  IN      NS      b.ns.ninthave.net.
>>ninthave.net.           189946  IN      NS      c.ns.ninthave.net.
>>ninthave.net.           189946  IN      NS      d.ns.ninthave.net.
>>
>>;; ADDITIONAL SECTION:
>>a.ns.ninthave.net.      189946  IN      A       194.153.169.15
>>b.ns.ninthave.net.      189946  IN      A       194.153.169.31
>>c.ns.ninthave.net.      189946  IN      A       212.100.225.215
>>d.ns.ninthave.net.      189946  IN      A       212.13.198.12
>>
>>;; Query time: 37 msec
>>;; SERVER: 203.2.75.132#53(203.2.75.132)
>>;; WHEN: Thu Jul 24 07:29:45 2003
>>;; MSG SIZE  rcvd: 217
>>
>>
>>    
>>
>>>Are you sure that's one of Telstra's DNS servers?  It translates to
>>>CPE-61-9-208-24.qld.bigpond.net.au, which doesn't look like 
>>>      
>>>
>>a DNS server's
>>    
>>
>>>name (CPE usually stands for Customer Premises Equipment, 
>>>      
>>>
>>so I suspect it's
>>    
>>
>>>a router at the customer end of a connection).
>>>      
>>>
>>Telstra's DNS gives no ADDITIONAL response. This behaviour 
>>only seems to 
>>have appeared recently (around Tuesday 22 July).
>>
>>Thanks,
>>
>>Roger
>>
>>
>>
>>-- 
>>--------------------------------------------------------------
>>----------
>>ninth ave                                             p: +61 
>>7 3870 8494
>>  Web Hosting                                          m: +61 
>>405 048 371
>>  Web Design                                   w: 
>>    
>>
>http://www.ninthave.net
>  Programming                                     e:
>r.keays at ninthave.net
>------------------------------------------------------------------------
>
>
>
>
>  
>



More information about the bind-users mailing list