On Jun 12, 2009, at 9:37 AM, Frank Pikelner wrote:
Thank you for everyone's assistance. I have updated the zone files.
After the updates and restarting BIND, I run "dig +trace ptr
170.3.187.64.in-addr.arpa" and the result stops just prior to
getting to
my DNS server and correctly resolving the name of the IP address. I'm
new to dig and do not know whether this is correct for an RFC2317 zone
delegation or whether the trace should be completing at my servers and
resolving the name.
This is normal. "dig +trace" does not follow the dangling CNAME record
that it finds - you'll see it in the last part of the trace. Just re-
run the trace with the altered name shown on the RHS of the CNAME
record - "170.162-27.3.187.64.in-addr.arpa" - or query with that name
against the indicated name servers directly (without using +trace).
$ dig 170.162-27.3.187.64.in-addr.arpa PTR +norec @ns3.blue-dot.ca
; <<>> DiG 9.4.3-P1 <<>> 170.162-27.3.187.64.in-addr.arpa PTR +norec
@ns3.blue-dot.ca
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7189
;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 0
;; QUESTION SECTION:
;170.162-27.3.187.64.in-addr.arpa. IN PTR
;; ANSWER SECTION:
170.162-27.3.187.64.in-addr.arpa. 86400 IN PTR
smtp3.netcraftcommunications.com.
;; AUTHORITY SECTION:
162-27.3.187.64.in-addr.arpa. 86400 IN NS ns2.blue-dot.ca.
162-27.3.187.64.in-addr.arpa. 86400 IN NS ns3.blue-dot.ca.
162-27.3.187.64.in-addr.arpa. 86400 IN NS ns1.blue-dot.ca.
;; Query time: 118 msec
;; SERVER: 64.187.3.170#53(64.187.3.170)
;; WHEN: Fri Jun 12 12:03:34 2009
;; MSG SIZE rcvd: 161
Chris Buxton
Professional Services
Men & Mice
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
