Hello,
On Thu, Mar 5, 2009 at 12:44 PM, Brian McKerr bmckerr@gmail.com wrote:
thank you, I have the forward zones replicated from the prim. DNS hosted at our Windows DC fine with this config:
# cat /etc/*release CentOS release 5.2 (Final)
# rpm -qa|grep bind bind-libs-9.3.4-6.0.3.P1.el5_2 bind-9.3.4-6.0.3.P1.el5_2 ypbind-1.19-8.el5 bind-utils-9.3.4-6.0.3.P1.el5_2 bind-chroot-9.3.4-6.0.3.P1.el5_2
# cat /var/named/chroot/etc/named.conf options { directory "/var/named"; };
zone "internal.mycompany.com" IN { type slave; file "slaves/internal.mycompany.com"; masters { 10.121.42.40 port 53;}; check-names ignore; };
zone "42.121.10.in-addr.arpa" IN { type slave; file "slaves/10.121.42"; masters { 10.121.42.40 port 53;}; check-names ignore; };
include "/etc/rndc.key";
But the replication of the reverse zone doesn't work yet - I get errors:
named[30219]: zone 42.121.10.in-addr.arpa/IN: refresh: unexpected rcode (NXDOMAIN) from master 10.121.42.40#53 (source 0.0.0.0#0)
Maybe I need to use some other name there?
I'm reading out on "dig" tool currently, trying to find out which zone names are served by the Windows prim. DNS...
Regards Alex