[CLUE-Tech] host -l and subdomains, reverse DNS

[David Anselmi]

Keith Christian wrote:
[...]
> 
> The thing still failing is the reverse zone, neither "host 192.168.1.153" nor
> "dig 192.168.1.153" succeeds:

Seems that it should be dig ptr 153.1.168.192.in-addr.arpa.  Host turns 
it around for you.

[...]
> I have checked the reverse zone file and it looks OK.  (I'm using examples
> from the RHCE certification book.)

I can think of two possibilities.  Either your zone file is wrong or 
you're asking the wrong name server.  Here's what dig shows me:

me at myhost:~$ dig ptr 153.1.168.192.in-addr.arpa.

; <<>> DiG 9.2.2 <<>> ptr 153.1.168.192.in-addr.arpa.
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 31108
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;153.1.168.192.in-addr.arpa.    IN      PTR

;; AUTHORITY SECTION:
168.192.in-addr.arpa.   6917    IN      SOA     prisoner.iana.org. 
hostmaster.root-servers.org. 2002040800 1800 900 604800 604800

;; Query time: 31 msec
;; SERVER: 63.122.16.3#53(63.122.16.3)
;; WHEN: Fri Aug  8 18:40:07 2003
;; MSG SIZE  rcvd: 124

You can see from the SERVER line where the query went.  You can see that 
the server went looking for the record, found the authority, and was 
told NXDOMAIN.

If you don't manage to query your name server, the one you do get has no 
way to  find you an answer (for an RFC-1918 address).  If dig tells you 
it can't contact a server, probably you're asking the wrong one.

Can you run dig like I did, and does that help at all?

Dave