Alexander Fortin wrote:
Hi folks. I'm having problems trying to set up a DNS forwarding zone for
PTRs records.
The weird thing is that "normal" DNS zones are working fine, but using
same configurations for the correspondent *.in.addr.arpa zone doesn't
work. Very strange to me seems that queries using "host" work but with
"dig" they don't.
The scenario involves my master DNS server trying to ask those records
from a VPN-connected DNS authoritative server (which unfortunately I
cannot transfer from). Of course, if I query directly the remote DNS
server I get answers for both zones:
$ dig @192.168.20.21 hrsrv.mydomain.locale
; <<>> DiG 9.5.1-P3 <<>> @192.168.20.21 hrsrv.mydomain.locale
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50067
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;hrsrv.mydomain.locale. IN A
;; ANSWER SECTION:
hrsrv.mydomain.locale. 3600 IN A 192.168.20.11
;; Query time: 696 msec
;; SERVER: 192.168.20.21#53(192.168.20.21)
;; WHEN: Fri Apr 2 14:45:55 2010
;; MSG SIZE rcvd: 53
but...
$ dig @192.168.20.21 192.168.20.11 PTR
Try dig @192.168.20.21 -x 192.168.20.11
Cheers!
Gary
--
AM Support Staff
Unixservice, LLC.
+1 310-356-6265
+1 630-206-9449
http://unixservice.com
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
