Reverse DNS not working for new server

[Mark Andrews]

> I added a new webmail server several weeks ago.  I made the pert. DNS  
> entries to the zone file and the reverse lookup file.  Within my  
> domain using my DNS servers everything resolves correctly.  When I do  
> an nslookup for 204.111.40.8 I get newproxy.harrisonburg.k12.va.us.   
> However, outside my domain I get
> UnKnown can't find 204.111.40.10: Non-existent domain.  Now the rest  
> of my ip's resolve correctly.  Heres my zone file:
> 
> $ORIGIN .
> $TTL 259200     ; 3 days
> harrisonburg.k12.va.us IN SOA ns1.harrisonburg.k12.va.us.  
> rlineweaver.harrisonburg.k12.va.us. (
>                                  2006112601 ; serial
>                                  28800      ; refresh (8 hours)
>                                  7200       ; retry (2 hours)
>                                  2419200    ; expire (4 weeks)
>                                  86400      ; minimum (1 day)
>                                  )
>                                  NS      ns1.harrisonburg.k12.va.us.
>                                  NS      ns2.harrisonburg.k12.va.us.
> Heres the entry for newproxy:
> newproxy                        A       204.111.40.10
> 
> Heres my reverse dns file for this zone:
> $ORIGIN .
> $TTL 259200     ; 3 days
> 40.111.204.in-addr.arpa         IN SOA  ns1.harrisonburg.k12.va.us.  
> rlineweaver.harrisonburg.k12.va.us. (
>                                  2006112601  ; serial
>                                  28800      ; refresh (8 hours)
>                                  7200       ; retry (2 hours)
>                                  2419200    ; expire (4 weeks)
>                                  86400      ; minimum (1 day)
>                                  )
>                          NS      ns1.harrisonburg.k12.va.us.
>                          NS      ns2.harrisonburg.k12.va.us.
> Heres the entry for Newproxy in reverse dns
> 10                      PTR     newproxy.harrisonburg.k12.va.us.
> 
> Heres my named.conf spelling out my upstream dns notifiers:
> options {
>          directory "/var/named";
> 
>          forward first;
>          forwarders {
>                  204.111.1.36;
>                  204.111.1.35;
>          };
> Ive added several servers in the past with no issues.  Im using bind  
> 9.2.3.  I cant figure out why other servers arent getting the updates.  
>   Im not seeing any error's logged at all.
> 
> thanks,
> 
> ddh
> 
> Network Administrator
> Harrisonburg City Public Schools

	As has been said many time nslookup is not a good diagnotic
	tool.

; <<>> DiG 9.3.2-P2 <<>> -x 204.111.40.10
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 50451
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

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

;; AUTHORITY SECTION:
40.111.204.in-addr.arpa. 10800	IN	SOA	ns.shentel.net. dnszoneadmin.shentel.net. 2006032200 10800 3600 604800 172800

;; Query time: 234 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Mon Nov 27 14:04:01 2006
;; MSG SIZE  rcvd: 107

	Which shows the answer is not coming from the intance of
	the zone you thought it was.  You either need to also
	update the zone on ns.shentel.net or change the delegation
	to point to your servers.

; <<>> DiG 9.3.2-P2 <<>> +trace -x 204.111.40.10
;; global options:  printcmd
.			38423	IN	NS	H.ROOT-SERVERS.NET.
.			38423	IN	NS	M.ROOT-SERVERS.NET.
.			38423	IN	NS	J.ROOT-SERVERS.NET.
.			38423	IN	NS	G.ROOT-SERVERS.NET.
.			38423	IN	NS	F.ROOT-SERVERS.NET.
.			38423	IN	NS	I.ROOT-SERVERS.NET.
.			38423	IN	NS	E.ROOT-SERVERS.NET.
.			38423	IN	NS	A.ROOT-SERVERS.NET.
.			38423	IN	NS	L.ROOT-SERVERS.NET.
.			38423	IN	NS	B.ROOT-SERVERS.NET.
.			38423	IN	NS	D.ROOT-SERVERS.NET.
.			38423	IN	NS	K.ROOT-SERVERS.NET.
.			38423	IN	NS	C.ROOT-SERVERS.NET.
;; Received 464 bytes from 127.0.0.1#53(127.0.0.1) in 2 ms

204.in-addr.arpa.	86400	IN	NS	chia.arin.net.
204.in-addr.arpa.	86400	IN	NS	dill.arin.net.
204.in-addr.arpa.	86400	IN	NS	basil.arin.net.
204.in-addr.arpa.	86400	IN	NS	henna.arin.net.
204.in-addr.arpa.	86400	IN	NS	indigo.arin.net.
204.in-addr.arpa.	86400	IN	NS	epazote.arin.net.
204.in-addr.arpa.	86400	IN	NS	figwort.arin.net.
;; Received 195 bytes from 2001:500:1::803f:235#53(H.ROOT-SERVERS.NET) in 338 ms

111.204.in-addr.arpa.	86400	IN	NS	ns2.shentel.net.
111.204.in-addr.arpa.	86400	IN	NS	ns.shentel.net.
;; Received 90 bytes from 2001:440:2000:1::21#53(chia.arin.net) in 660 ms

40.111.204.in-addr.arpa. 86400	IN	SOA	ns.shentel.net. dnszoneadmin.shentel.net. 2006032200 10800 3600 604800 172800
;; Received 107 bytes from 204.111.1.36#53(ns2.shentel.net) in 231 ms

-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org