Thanks for the hints, I've read manuals for those tools I didn't know.
Anyway, I've checked named.conf with named-checkconf and it is fine.
About the zone, as I said, I can not do zone transfers from their DNS
server to mine, so I'm trying to use forwarding instead of master/slave
zones.
On
Hope this is helpful:
Your d.c.b.a.in-addr.arpa zone may not have the correct data in it.
Since dig shows no answer for that specific query.
If you have not already learn how to use:
named-checkconf
named-checkzone
Check your named.conf and all files therein included, then check again.
(Mak
On 04/02/2010 03:50 PM, Gary Wallis wrote:
Try dig @192.168.20.21 -x 192.168.20.11
Cheers!
Gary
$ dig @192.168.20.21 -x 192.168.20.11
; <<>> DiG 9.5.1-P3 <<>> @192.168.20.21 -x 192.168.20.11
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status:
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 queri
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
5 matches
Mail list logo