HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials

HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials (http://www.howtoforge.com/forums/index.php)
-   HOWTO-Related Questions (http://www.howtoforge.com/forums/forumdisplay.php?f=2)
-   -   DNS Zone Transfer not complete. (http://www.howtoforge.com/forums/showthread.php?t=14848)

joelee 17th August 2007 22:45

DNS Zone Transfer not complete.
 
Hi All, I've installed both primary and secondary DNS using the 2 following how-to:

Installing Bind9:
http://howtoforge.com/perfect_setup_debian_etch_p4

Setting up Master & Slave DNS:
http://howtoforge.com/debian_bind9_master_slave_system

Setting up a split with views:
http://howtoforge.com/two_in_one_dns_bind9_views

All seems to work fine so far. However, I am not able to see my external zones get transfered to the secondary dns server. I see the internal zones got transfered from primary to secondary but no external zones.

A look at my syslog file on both machines revelas:
Primary Server: /var/log/syslog
Code:

Aug 17 05:50:48 ns1 named[18357]: starting BIND 9.3.4 -u bind -t /var/lib/named
Aug 17 05:50:48 ns1 named[18357]: found 1 CPU, using 1 worker thread
Aug 17 05:50:48 ns1 named[18357]: loading configuration from '/etc/bind/named.conf'
Aug 17 05:50:48 ns1 named[18357]: /etc/bind/named.conf:12: when using 'view' statements, all zones must be in views
Aug 17 05:50:48 ns1 named[18357]: listening on IPv6 interfaces, port 53
Aug 17 05:50:48 ns1 named[18357]: listening on IPv4 interface lo, 127.0.0.1#53
Aug 17 05:50:48 ns1 named[18357]: listening on IPv4 interface venet0:0, 192.168.10.101#53
Aug 17 05:50:48 ns1 named[18357]: command channel listening on 127.0.0.1#953
Aug 17 05:50:48 ns1 named[18357]: command channel listening on ::1#953
Aug 17 05:50:48 ns1 named[18357]: zone 1.168.192.in-addr.arpa/IN/internal: loaded serial 2007081701
Aug 17 05:50:48 ns1 named[18357]: zone MyDomaninName.com/IN/internal: loaded serial 2007081701
Aug 17 05:50:48 ns1 named[18357]: zone 119.20.219.in-addr.arpa/IN/external: loaded serial 2007081701
Aug 17 05:50:48 ns1 named[18357]: zone MyDomaninName.com/IN/external: loaded serial 2007081701
Aug 17 05:50:48 ns1 named[18357]: running
Aug 17 05:50:48 ns1 named[18357]: zone MyDomaninName.com/IN/internal: sending notifies (serial 2007081701)
Aug 17 05:50:48 ns1 named[18357]: zone MyDomaninName.com/IN/external: sending notifies (serial 2007081701)
Aug 17 05:50:48 ns1 named[18357]: zone 1.168.192.in-addr.arpa/IN/internal: sending notifies (serial 2007081701)
Aug 17 05:50:48 ns1 named[18357]: zone 119.20.219.in-addr.arpa/IN/external: sending notifies (serial 2007081701)
Aug 17 05:50:48 ns1 named[18357]: client 192.168.1.102#40667: view internal: transfer of 'MyDomaninName.com/IN': AXFR started
Aug 17 05:50:48 ns1 named[18357]: client 192.168.1.102#40667: view internal: transfer of 'MyDomaninName.com/IN': AXFR ended
Aug 17 05:50:49 ns1 named[18357]: client 192.168.1.102#37504: view internal: transfer of '1.168.192.in-addr.arpa/IN': AXFR started
Aug 17 05:50:49 ns1 named[18357]: client 192.168.1.102#37504: view internal: transfer of '1.168.192.in-addr.arpa/IN': AXFR ended
Aug 17 05:56:07 ns1 named[18357]: client 192.168.1.102#59129: view internal: transfer of 'MyDomaninName.com/IN': AXFR started
Aug 17 05:56:07 ns1 named[18357]: client 192.168.1.102#59129: view internal: transfer of 'MyDomaninName.com/IN': AXFR ended
Aug 17 06:18:35 ns1 -- MARK --

Secondary Server: /var/log/syslog
Code:

Aug 17 05:56:06 ns2 named[18423]: starting BIND 9.3.4 -u bind -t /var/lib/named
Aug 17 05:56:06 ns2 named[18423]: found 1 CPU, using 1 worker thread
Aug 17 05:56:06 ns2 named[18423]: loading configuration from '/etc/bind/named.conf'
Aug 17 05:56:06 ns2 named[18423]: /etc/bind/named.conf:12: when using 'view' statements, all zones must be in views
Aug 17 05:56:06 ns2 named[18423]: listening on IPv6 interfaces, port 53
Aug 17 05:56:06 ns2 named[18423]: listening on IPv4 interface lo, 127.0.0.1#53
Aug 17 05:56:06 ns2 named[18423]: listening on IPv4 interface venet0:0, 192.168.1.2#53
Aug 17 05:56:06 ns2 named[18423]: command channel listening on 127.0.0.1#953
Aug 17 05:56:06 ns2 named[18423]: command channel listening on ::1#953
Aug 17 05:56:06 ns2 named[18423]: zone 1.168.192.in-addr.arpa/IN/internal: loaded serial 2007081701
Aug 17 05:56:06 ns2 named[18423]: zone MyDomainName.com/IN/internal: loaded serial 2007081701
Aug 17 05:56:06 ns2 named[18423]: running
Aug 17 05:56:06 ns2 named[18423]: zone MyDomainName.com/IN/internal: sending notifies (serial 2007081701)
Aug 17 05:56:07 ns2 named[18423]: zone 1.168.192.in-addr.arpa/IN/internal: sending notifies (serial 2007081701)
Aug 17 05:56:07 ns2 named[18423]: client 192.168.1.2#32796: view internal: received notify for zone 'MyDomainName.com'
Aug 17 05:56:07 ns2 named[18423]: zone MyDomainName.com/IN/internal: refused notify from non-master: 192.168.1.2#32796
Aug 17 05:56:07 ns2 named[18423]: client 192.168.1.2#32796: view internal: received notify for zone '1.168.192.in-addr.arpa'
Aug 17 05:56:07 ns2 named[18423]: zone 1.168.192.in-addr.arpa/IN/internal: refused notify from non-master: 192.168.1.2#32796
Aug 17 05:56:07 ns2 named[18423]: zone MyDomainName.com/IN/external: Transfer started.
Aug 17 05:56:07 ns2 named[18423]: zone 119.20.219.in-addr.arpa/IN/external: refresh: non-authoritative answer from master 192.168.1
.101#53 (source 192.168.1.2#0)
Aug 17 05:56:07 ns2 named[18423]: transfer of 'MyDomainName.com/IN' from 192.168.1.1#53: connected using 192.168.1.2#59129
Aug 17 05:56:07 ns2 named[18423]: zone MyDomainName.com/IN/external: transferred serial 2007081701
Aug 17 05:56:07 ns2 named[18423]: transfer of 'MyDomainName.com/IN' from 192.168.1.1#53: end of transfer
Aug 17 05:56:07 ns2 named[18423]: zone MyDomainName.com/IN/external: sending notifies (serial 2007081701)
Aug 17 05:56:07 ns2 named[18423]: client 192.168.1.2#32796: view internal: received notify for zone 'MyDomainName.com'
Aug 17 05:56:07 ns2 named[18423]: zone MyDomainName.com/IN/internal: refused notify from non-master: 192.168.1.2#32796
Aug 17 05:57:05 ns2 named[18423]: zone 119.20.219.in-addr.arpa/IN/external: refresh: non-authoritative answer from master 192.168.1
.101#53 (source 192.168.1.2#0)
Aug 17 05:58:45 ns2 named[18423]: zone 119.20.219.in-addr.arpa/IN/external: refresh: non-authoritative answer from master 192.168.1
.101#53 (source 192.168.1.2#0)
Aug 17 06:02:21 ns2 named[18423]: zone 119.20.219.in-addr.arpa/IN/external: refresh: non-authoritative answer from master 192.168.1
.101#53 (source 192.168.1.2#0)
Aug 17 06:10:05 ns2 named[18423]: zone 119.20.219.in-addr.arpa/IN/external: refresh: non-authoritative answer from master 192.168.1
.101#53 (source 192.168.1.2#0)
Aug 17 06:22:31 ns2 named[18423]: zone 119.20.219.in-addr.arpa/IN/external: refresh: non-authoritative answer from master 192.168.1
.101#53 (source 192.168.1.2#0)

I would appreciate if anyone can help me identify the problem!

Joe

falko 18th August 2007 12:46

I think this could be the problem:
Quote:

Aug 17 05:58:45 ns2 named[18423]: zone 119.20.219.in-addr.arpa/IN/external: refresh: non-authoritative answer from master 192.168.1
Apart from that, there's no indication of problems with the external views in the logs...

joelee 18th August 2007 22:35

Quote:

I think this could be the problem:
Quote:
Aug 17 05:58:45 ns2 named[18423]: zone 119.20.219.in-addr.arpa/IN/external: refresh: non-authoritative answer from master 192.168.1
Apart from that, there's no indication of problems with the external views in the logs...
Falko, thanks for the tip... Any idea/suggestions on how I can fix this? Would this fix be in the named.conf file or zone files. I am not much experience in this area. Any help would be appreciated!

Joe

falko 19th August 2007 14:55

I'd try to replace the nameservers in /etc/resolv.conf on the slave with just your master DNS server.


All times are GMT +2. The time now is 20:08.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.