And you still have some IPv6 connectivity issues:

Jun 20 19:21:58 ns1 named[3178]: error (network unreachable) resolving
'ns1.mweb.co.za/AAAA/IN': 2001:4200:ffff:a::1#53
Jun 20 19:21:58 ns1 named[3178]: error (network unreachable) resolving
'ns2.mweb.co.za/AAAA/IN': 2001:500:2e::1#53
Jun 20 19:21:58 ns1 named[3178]: error (network unreachable) resolving
'ns.coza.net.za/AAAA/IN': 2001:500:14:6055:ad::1#53
Jun 20 19:21:58 ns1 named[3178]: error (network unreachable) resolving
'ns0.plig.net/A/IN': 2001:503:ba3e::2:30#53
Jun 20 19:21:58 ns1 named[3178]: error (network unreachable) resolving
'ns4.iafrica.com/A/IN': 2001:dc3::35#53
Jun 20 19:21:58 ns1 named[3178]: error (network unreachable) resolving
'coza1.dnsnode.net/A/IN': 2001:500:2f::f#53
Jun 20 19:21:58 ns1 named[3178]: error (network unreachable) resolving
'coza1.dnsnode.net/A/IN': 2001:500:1::803f:235#53
Jun 20 19:21:58 ns1 named[3178]: error (network unreachable) resolving
'coza1.dnsnode.net/A/IN': 2001:503:c27::2:30#53
Jun 20 19:21:58 ns1 named[3178]: error (network unreachable) resolving
'coza1.dnsnode.net/A/IN': 2001:7fe::53#53
Jun 20 19:21:58 ns1 named[3178]: error (network unreachable) resolving
'coza1.dnsnode.net/A/IN': 2001:500:3::42#53
Jun 20 19:21:58 ns1 named[3178]: error (network unreachable) resolving
'ns.orange-tree.alt.za/A/IN': 2001:67c:1010:19::53#53
Jun 20 19:21:59 ns1 named[3178]: error (network unreachable) resolving
'secdns1.posix.co.za/A/IN': 2001:42a0:1000:ff02::481#53
Jun 20 19:21:59 ns1 named[3178]: error (network unreachable) resolving
'coza1.dnsnode.net/A/IN': 2001:503:231d::2:30#53
Jun 20 19:21:59 ns1 named[3178]: error (network unreachable) resolving
'ns.orange-tree.alt.za/AAAA/IN': 2001:4200:1010::1#53
Jun 20 19:21:59 ns1 named[3178]: error (network unreachable) resolving
'rain.psg.com/A/IN': 2001:503:a83e::2:30#53
Jun 20 19:21:59 ns1 named[3178]: error (network unreachable) resolving
'arizona.edu/AAAA/IN': 2001:7fd::1#53
Jun 20 19:21:59 ns1 named[3178]: error (network unreachable) resolving
'ns1.iafrica.com/AAAA/IN': 2001:418:1::39#53
Jun 20 19:21:59 ns1 named[3178]: error (network unreachable) resolving
'nlns.globnix.net/AAAA/IN': 2a02:898:31::53:0#53
Bind was getting confused between IPv4 and IPv6,
so after modified the file :  File: /etc/default/bind9  for my master and slave
# run resolvconf?
RESOLVCONF=yes

# startup options for the server
OPTIONS="-4 -u bind"

It seeming like working now :-)

grep named /var/log/syslog on my master:

Jun 21 07:53:44 ns1 named[3835]: automatic empty zone: view internal-localhost: 2.0.192.IN-ADDR.ARPA
Jun 21 07:53:44 ns1 named[3835]: automatic empty zone: view internal-localhost: 100.51.198.IN-ADDR.ARPA
Jun 21 07:53:44 ns1 named[3835]: automatic empty zone: view internal-localhost: 113.0.203.IN-ADDR.ARPA
Jun 21 07:53:44 ns1 named[3835]: automatic empty zone: view internal-localhost: 255.255.255.255.IN-ADDR.ARPA
Jun 21 07:53:44 ns1 named[3835]: automatic empty zone: view internal-localhost: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Jun 21 07:53:44 ns1 named[3835]: automatic empty zone: view internal-localhost: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Jun 21 07:53:44 ns1 named[3835]: automatic empty zone: view internal-localhost: D.F.IP6.ARPA
Jun 21 07:53:44 ns1 named[3835]: automatic empty zone: view internal-localhost: 8.E.F.IP6.ARPA
Jun 21 07:53:44 ns1 named[3835]: automatic empty zone: view internal-localhost: 9.E.F.IP6.ARPA
Jun 21 07:53:44 ns1 named[3835]: automatic empty zone: view internal-localhost: A.E.F.IP6.ARPA
Jun 21 07:53:44 ns1 named[3835]: automatic empty zone: view internal-localhost: B.E.F.IP6.ARPA
Jun 21 07:53:44 ns1 named[3835]: automatic empty zone: view internal-localhost: 8.B.D.0.1.0.0.2.IP6.ARPA

...................

Jun 21 07:53:44 ns1 named[3835]: zone 0.0.10.in-addr.arpa/IN/internal: sending notifies (serial 15)
Jun 21 07:53:44 ns1 named[3835]: zone metropolitanbuntu.co.za/IN/internal: sending notifies (serial 15)
Jun 21 07:53:44 ns1 named[3835]: zone 194.134.41.in-addr.arpa/IN/external: sending notifies (serial 15)
Jun 21 07:53:44 ns1 named[3835]: zone metropolitanbuntu.co.za/IN/external: sending notifies (serial 15)
Jun 21 07:53:48 ns1 named[3835]: received control channel command 'reload'
Jun 21 07:53:48 ns1 named[3835]: loading configuration from '/etc/bind/named.conf'
Jun 21 07:53:48 ns1 named[3835]: reading built-in trusted keys from file '/etc/bind/bind.keys'
Jun 21 07:53:48 ns1 named[3835]: using default UDP/IPv4 port range: [1024, 65535]
Jun 21 07:53:48 ns1 named[3835]: using default UDP/IPv6 port range: [1024, 65535]
Jun 21 07:53:48 ns1 named[3835]: no IPv6 interfaces found
Jun 21 07:53:48 ns1 named[3835]: reloading configuration succeeded
Jun 21 07:53:48 ns1 named[3835]: reloading zones succeeded
----


grep named /var/log/syslog on my slave:
-------------
Jun 21 07:51:25 ns2 named[5838]: running
Jun 21 07:51:25 ns2 named[5838]: client 10.0.0.82#43092: view external-root: received notify for zone 'metropolitanbuntu.co.za': not authoritative
Jun 21 07:51:26 ns2 named[5838]: client 10.0.0.82#52199: view external-root: received notify for zone '0.0.10.in-addr.arpa': not authoritative
Jun 21 07:51:26 ns2 named[5838]: client 10.0.0.82#52199: view external-root: received notify for zone 'metropolitanbuntu.co.za': not authoritative
Jun 21 07:53:01 ns2 named[5838]: client 10.0.0.80#52342: view external-root: received notify for zone '0.0.10.in-addr.arpa': not authoritative
Jun 21 07:53:01 ns2 named[5838]: client 10.0.0.80#48631: view external-root: received notify for zone 'metropolitanbuntu.co.za': not authoritative
Jun 21 07:57:58 ns2 named[5838]: success resolving 'mail.namekom.co.za/AAAA' (in 'namekom.co.za'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jun 21 07:57:58 ns2 named[5838]: success resolving 'ns2.serve-hosting.net/A' (in 'serve-hosting.net'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jun 21 07:57:58 ns2 named[5838]: success resolving 'ns1.serve-hosting.net/A' (in 'serve-hosting.net'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jun 21 07:57:59 ns2 named[5838]: success resolving 'mail.namekom.co.za/A' (in 'namekom.co.za'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jun 21 08:00:22 ns2 named[5838]: zone 194.134.41.in-addr.arpa/IN/external: refresh: non-authoritative answer from master 10.0.0.80#53 (source 0.0.0.0#0)
Jun 21 08:05:00 ns2 named[5838]: unexpected RCODE (SERVFAIL) resolving 'rss.cbc.ca/A/IN': 207.236.176.29#53
Jun 21 08:07:01 ns2 named[5838]: client 10.0.0.80#36783: view external-root: received notify for zone '0.0.10.in-addr.arpa': not authoritative
Jun 21 08:07:02 ns2 named[5838]: client 10.0.0.80#9344: view external-root: received notify for zone 'metropolitanbuntu.co.za': not authoritative

----
Jun 21 08:00:22 ns2 named[5838]: zone 194.134.41.in-addr.arpa/IN/external: refresh: non-authoritative answer from master 10.0.0.80#53 (source 0.0.0.0#0)
Jun 21 08:05:00 ns2 named[5838]: unexpected RCODE (SERVFAIL) resolving 'rss.cbc.ca/A/IN': 207.236.176.29#53
Jun 21 08:07:01 ns2 named[5838]: client 10.0.0.80#36783: view external-root: received notify for zone '0.0.10.in-addr.arpa': not authoritative
Jun 21 08:07:02 ns2 named[5838]: client 10.0.0.80#9344: view external-root: received notify for zone 'metropolitanbuntu.co.za': not authoritative
Jun 21 08:11:59 ns2 named[5838]: zone 194.134.41.in-addr.arpa/IN/external: refresh: non-authoritative answer from master 10.0.0.80#53 (source 0.0.0.0#0)

Please, it is correct this "automatic empty zone" message?

I asked the master to notify the slave about any change but the serials on zone files slave are still the same,

'metropolitanbuntu.co.za': not authoritative?

And you did a reload successfully.

Jun 20 19:22:02 ns1 named[3178]: received control channel command 'reload'
Jun 20 19:22:02 ns1 named[3178]: loading configuration from
'/etc/bind/named.conf'
Jun 20 19:22:02 ns1 named[3178]: reading built-in trusted keys from file
'/etc/bind/bind.keys'
Jun 20 19:22:02 ns1 named[3178]: using default UDP/IPv4 port range:
[1024, 65535]
Jun 20 19:22:02 ns1 named[3178]: using default UDP/IPv6 port range:
[1024, 65535]
Jun 20 19:22:02 ns1 named[3178]: reloading configuration succeeded
Jun 20 19:22:02 ns1 named[3178]: reloading zones succeeded
root@ns1:/var/cache/bind#


This is still an issue for you:

But that does not change that your upstream has not delegated this
in-addr.arpa range to you.
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users



-- 
--  
You Truly

Eric Kom

System Administrator - Metropolitan College

2 Hennie Van Till, White River, 1240
Tel: 013 750 2255 | Fax: 013 750 0105 | Cell: 078 879 1334
eric...@kom.za.net | eric...@namekom.co.za | eric...@erickom.co.za
www.kom.za.net | www.kom.za.org | www.erickom.co.za 

Key fingerprint: 513E E91A C243 3020 8735 09BB 2DBC 5AD7 A9DA 1EF5

_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe 
from this list

bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Reply via email to