Issue with reverse dns and local caching name server

Jason Crummack jason.crummack at easysoft.com
Wed Jun 10 12:14:30 UTC 2009


Noel Butler wrote:
>
> On Wed, 2009-06-10 at 11:20 +0100, Jason Crummack wrote:
>> dig @82.138.243.4 30.22.203.in-addr.arpa NS
>>
> I get a response from that IP as well, however from mine, I don't, I 
> suspect that's the server cache.
> Is this IP range still delegated to you?
>
>
> dig  30.22.203.in-addr.arpa NS
>
> ; <<>> DiG 9.4.2-P2 <<>> 30.22.203.in-addr.arpa NS
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 14148
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;30.22.203.in-addr.arpa. IN NS
>
>
> I get a response from that as well, however from mine, I don't, I 
> suspect thats the server cache
> Is this IP range still delegated to you?/
>
> dig  30.22.203.in-addr.arpa NS
>
> ; <<>> DiG 9.4.2-P2 <<>> 30.22.203.in-addr.arpa NS
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 14148
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;30.22.203.in-addr.arpa. IN NS
>
>
> dig 47.30.22.203.in-addr.arpa @ns01.opensystems.com.au.
>
> ; <<>> DiG 9.4.2-P2 <<>> 47.30.22.203.in-addr.arpa 
> @ns01.opensystems.com.au.
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 413
> ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
> ;; WARNING: recursion requested but not available
>
> ;; QUESTION SECTION:
> ;47.30.22.203.in-addr.arpa. IN A
>
> ;; AUTHORITY SECTION:
> 30.22.203.in-addr.arpa. 38400 IN SOA ns01.opensystems.com.au. 
> support.opensystems.com.au. 1052091109 10800 3600 604800 38400
>
>
> Querying your server gets a response, but like mine, none others seem 
> to, what changes have you made recently?
> a Te$ltra server I query also knows it, but my secondary DNS (located 
> in California) does not either, nor does ns1.exetel
> so somethings changed
>
>
None of the servers listed other than my local caching lookup server 
belong to us / are maintained by us. The 47.30.22.203 is a customer of 
ours who's email into our domain is being rejected due to reverse lookup 
failing in our local caching nameserver, the other dns mentioned is one 
belonging to a hosting provider of ours where we host external websites, 
so the query currently fails from our local caching server (127.0.0.1) 
but not on 82.138.243.4 and 82.138.243.24 (our hosting providers dns 
servers - will attempt to find our from them what they are running might 
shed some light on things).

Jason



More information about the bind-users mailing list