Hi! On Mon, Dec 17, 2007 at 02:33:25AM +1100, mufurcz wrote: >New DNS server setup, suppose to be authoritative for the >`transylvania.org.au` zone >but reverse lookup is not working - as it suppose to work.
>[...] >----------------------------------------- >lookup local server(s): >------------------------------------------ ># nslookup juno >Server: 127.0.0.1 >Address: 127.0.0.1#53 >Name: juno.transylvania.org.au >Address: 192.168.1.200 ># nslookup selena.transylvania.org.au >Server: 127.0.0.1 >Address: 127.0.0.1#53 >Name: selena.transylvania.org.au >Address: 192.168.1.199 >-------------------------------------------- >reverse lookup >-------------------------------------------- ># nslookup 192.168.1.200 >Server: 127.0.0.1 >Address: 127.0.0.1#53 >** server can't find 200.1.168.192.in-addr.arpa: NXDOMAIN >------------------------------------------- >lookup internet >------------------------------------------- ># nslookup au.sun.com >Server: 127.0.0.1 >Address: 127.0.0.1#53 >Non-authoritative answer: >Name: au.sun.com >Address: 72.5.124.45 ># nslookup 72.5.124.45 >Server: 127.0.0.1 >Address: 127.0.0.1#53 >** server can't find 45.124.5.72.in-addr.arpa: NXDOMAIN So sun hasn't setup a proper reverse mapping for their stuff... >[... openbsd.org has ...] >So, what I am doing wrong? As you see in the output of your reverse lookup using nslookup, the reverse lookup of IP address a.b.c.d involves looking up the DNS name d.c.b.a.in-addr.arpa. More exactly, it's looking up that name, using RR type PTR. So, using dig, you'd use the command dig 199.1.168.192.in-addr.arpa ptr That's one part of the mistake in your dig invocations. However, using nslookup that's not the problem, as nslookup (and host, btw) has magic to handle that on its own. So to handle reverse mappings you'd have to setup a DNS zone file for an appropriate zone above 199.1.168.192.in-addr.arpa. and enter the appropriate record there, for example 199.1.168.192.in-addr.arpa. IN PTR selena.transylvania.org.au. 200.1.168.192.in-addr.arpa. IN PTR juno.transylvania.org.au. *And* you'd have to get a zone delegation for that zone file. And there's the problem. 192.168.x.y is private use (RFC 1918), so you won't get an official delegation for reverse mappings. Kind regards, Hannah.