Search Again:

Re: Reverse DNS

From: Larry Scott Hastings
Date: Monday, February 14, 2005
Time: 10:40:02 am

From what I can see, the reverse zone _is_ delegated to us. I did the
same host lookup as Chris, and I show my server and the secondaries. I
also called my ISP and confirmed that I am primary for the reverse
domain for our class C.

> host -t ns 208.253.216.in-addr.arpa
> 208.253.216.in-addr.arpa name server ns2.espire.net.
> 208.253.216.in-addr.arpa name server ns3.espire.net.
> 208.253.216.in-addr.arpa name server dns.hastings.com.
> 208.253.216.in-addr.arpa name server ns1.espire.net.


As to whether there is some stateful firewall issues, I may inquire
further. However, even a query _within_ our network explicitly to our
local, primary dns server returns the same problematic info (a request
for PTR records returns nothing, and a request for ANY records returns
the PTR records).

Any ideas? Can I (Should I) try to recreate the reverse domain from
scratch?


On Feb 11, 2005, at 6:20 PM, Men & Mice Support wrote:

> The query you sent (shown in the Question section of the dig output)
> asked for A records instead of PTR records.
>
> The odd thing is the status. When your server is asked for a PTR
> record, it changes the status from "NOERROR" to "NXDOMAIN".
>
> $ dig 4.208.253.216.in-addr.arpa @dns.hastings.com ptr +norec
>
> ; <<>> DiG 9.3.0 <<>> 4.208.253.216.in-addr.arpa @dns.hastings.com ptr
> +norec
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 44923
> ;; flags: qr ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;4.208.253.216.in-addr.arpa. IN PTR
>
> ;; AUTHORITY SECTION:
> 253.216.in-addr.arpa. 10356 IN SOA prisoner.iana.org.
> hostmaster.root-servers.org. 2002040800 1800 900 604800 604800
>
> ;; Query time: 110 msec
> ;; SERVER: 216.253.208.2#53(dns.hastings.com)
> ;; WHEN: Fri Feb 11 16:10:17 2005
> ;; MSG SIZE rcvd: 121
>
>
> This is very strange. In fact, if I query it for any record, it
> returns the PTR record:
>
> $ dig 4.208.253.216.in-addr.arpa @dns.hastings.com any +norec
>
> ; <<>> DiG 9.3.0 <<>> 4.208.253.216.in-addr.arpa @dns.hastings.com any
> +norec
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16016
> ;; flags: qr aa ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4
>
> ;; QUESTION SECTION:
> ;4.208.253.216.in-addr.arpa. IN ANY
>
> ;; ANSWER SECTION:
> 4.208.253.216.in-addr.arpa. 86400 IN PTR mail.hastings.com.
>
> ;; AUTHORITY SECTION:
> 208.253.216.in-addr.arpa. 86400 IN NS dns.hastings.com.
> 208.253.216.in-addr.arpa. 86400 IN NS ns1.espire.net.
> 208.253.216.in-addr.arpa. 86400 IN NS ns2.espire.net.
> 208.253.216.in-addr.arpa. 86400 IN NS ns3.espire.net.
>
> ;; ADDITIONAL SECTION:
> dns.hastings.com. 86400 IN A 216.253.208.2
> ns1.espire.net. 57387 IN A 207.191.50.10
> ns2.espire.net. 57387 IN A 207.191.1.10
> ns3.espire.net. 57387 IN A 206.222.97.50
>
> ;; Query time: 140 msec
> ;; SERVER: 216.253.208.2#53(dns.hastings.com)
> ;; WHEN: Fri Feb 11 16:10:03 2005
> ;; MSG SIZE rcvd: 221
>
>
> Do you have some sort of stateful firewall between your server and the
> Internet that might be interfering here?
>
> Regardless, this zone isn't delegated to your server, as you suggested.
>
> $ host -t ns 208.253.216.in-addr.arpa
> 208.253.216.in-addr.arpa name server dns2.xspedius.net.
> 208.253.216.in-addr.arpa name server dns3.xspedius.net.
> 208.253.216.in-addr.arpa name server dns1.xspedius.net.
>
> Chris Buxton
> Men & Mice - Making DNS Easy
>
>
> At 3:51 PM -0600 2/11/05, Larry Scott Hastings wrote:
>> I've discovered that my reverse DNS is not working for my mail
>> server's IP (or any other IP address, for that matter). [I'm looking
>> forward to pulling out my O'Reilly BIND book when I get home. But in
>> the meantime...]
>>
>> Right now, QuickDNS is generating a reverse zone automatically for
>> me. From within QuickDNS, everything looks OK to me. Now, I
>> understand (to some degree) that reverse dns is usually delegated to
>> one's ISP. BUT, shouldn't my reverse zone work, if I am querying the
>> DNS server directly/explicitly from within the same local network?
>>
>> I'd like to make sure I have things set up properly in QuickDNS
>> before I call my ISP for help.
>>
>> Here's the dirt...
>>
>> In QuickDNS 4, within the zone "208.253.216.in-addr.arpa." I have the
>> line:
>>
>> 4.208.253.216.in-addr.arpa. IN PTR mail.hastings.com. ;
>> Automatically generated by QuickDNS
>>
>>
>> From my laptop I query my local dns server:
>>
>> dig 4.208.253.216.in-addr.arpa @dns.hastings.com
>>
>> And in response I get "ANSWER: 0":
>>
>> ; <<>> DiG 9.2.2 <<>> 4.208.253.216.in-addr.arpa @dns.hastings.com
>> ;; global options: printcmd
>> ;; Got answer:
>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29366
>> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL:
>> 0
>>
>> ;; QUESTION SECTION:
>> ;4.208.253.216.in-addr.arpa. IN A
>>
>> ;; AUTHORITY SECTION:
>> 208.253.216.in-addr.arpa. 86400 IN SOA dns.hastings.com.
>> scott.hastings.com. 2005020902 28800 7200 604800 86400
>>
>> ;; Query time: 76 msec
>> ;; SERVER: 216.253.208.2#53(dns.hastings.com)
>> ;; WHEN: Fri Feb 11 15:43:16 2005
>> ;; MSG SIZE rcvd: 102
>
>




Messages In This Thread:



Return to Digital Point Solutions' Home Page