On 20/06/2011 17:14, Lyle Giese wrote:
Maybe I'm still mix up somethings because after change the settings, the grep named /etc/log/syslog still showing errors: Jun 20 19:21:58 ns1 named[3178]: automatic empty zone: view internal-localhost: 254.169.IN-ADDR.ARPA Jun 20 19:21:58 ns1 named[3178]: automatic empty zone: view internal-localhost: 2.0.192.IN-ADDR.ARPA Jun 20 19:21:58 ns1 named[3178]: automatic empty zone: view internal-localhost: 100.51.198.IN-ADDR.ARPA Jun 20 19:21:58 ns1 named[3178]: automatic empty zone: view internal-localhost: 113.0.203.IN-ADDR.ARPA Jun 20 19:21:58 ns1 named[3178]: automatic empty zone: view internal-localhost: 255.255.255.255.IN-ADDR.ARPA Jun 20 19:21:58 ns1 named[3178]: 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 20 19:21:58 ns1 named[3178]: 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 20 19:21:58 ns1 named[3178]: automatic empty zone: view internal-localhost: D.F.IP6.ARPA Jun 20 19:21:58 ns1 named[3178]: automatic empty zone: view internal-localhost: 8.E.F.IP6.ARPA Jun 20 19:21:58 ns1 named[3178]: automatic empty zone: view internal-localhost: 9.E.F.IP6.ARPA Jun 20 19:21:58 ns1 named[3178]: automatic empty zone: view internal-localhost: A.E.F.IP6.ARPA Jun 20 19:21:58 ns1 named[3178]: automatic empty zone: view internal-localhost: B.E.F.IP6.ARPA Jun 20 19:21:58 ns1 named[3178]: automatic empty zone: view internal-localhost: 8.B.D.0.1.0.0.2.IP6.ARPA Jun 20 19:21:58 ns1 named[3178]: command channel listening on 127.0.0.1#953 Jun 20 19:21:58 ns1 named[3178]: command channel listening on ::1#953 Jun 20 19:21:58 ns1 named[3178]: zone 0.0.10.in-addr.arpa/IN/internal: loaded serial 13 Jun 20 19:21:58 ns1 named[3178]: zone metropolitanbuntu.co.za/IN/internal: loaded serial 12 Jun 20 19:21:58 ns1 named[3178]: managed-keys-zone ./IN/internal: loading from master file 3bed2cb3a3acf7b6a8ef408420cc682d5520e26976d354254f528c965612054f.mkeys failed: file not found Jun 20 19:21:58 ns1 named[3178]: managed-keys-zone ./IN/internal: loaded serial 0 Jun 20 19:21:58 ns1 named[3178]: zone 194.134.41.in-addr.arpa/IN/external: loaded serial 14 Jun 20 19:21:58 ns1 named[3178]: zone metropolitanbuntu.co.za/IN/external: loaded serial 12 Jun 20 19:21:58 ns1 named[3178]: managed-keys-zone ./IN/external: loading from master file 3c4623849a49a53911c4a3e48d8cead8a1858960bccdea7a1b978d73ec2f06d7.mkeys failed: file not found Jun 20 19:21:58 ns1 named[3178]: managed-keys-zone ./IN/external: loaded serial 0 Jun 20 19:21:58 ns1 named[3178]: managed-keys-zone ./IN/external-root: loading from master file 67b44ff7c3d7837b9632a71c8718eba864b9b4f6fb18ec48ebdb1821e40d6bee.mkeys failed: file not found Jun 20 19:21:58 ns1 named[3178]: managed-keys-zone ./IN/external-root: loaded serial 0 Jun 20 19:21:58 ns1 named[3178]: zone 0.in-addr.arpa/IN/internal-localhost: loaded serial 1 Jun 20 19:21:58 ns1 named[3178]: zone 127.in-addr.arpa/IN/internal-localhost: loaded serial 1 Jun 20 19:21:58 ns1 named[3178]: zone 255.in-addr.arpa/IN/internal-localhost: loaded serial 1 Jun 20 19:21:58 ns1 named[3178]: zone localhost/IN/internal-localhost: loaded serial 2 Jun 20 19:21:58 ns1 named[3178]: managed-keys-zone ./IN/internal-localhost: loading from master file 7c494d432269c6510ccdc34922639a7222454e4759be924904ddf05eaed6e546.mkeys failed: file not found Jun 20 19:21:58 ns1 named[3178]: managed-keys-zone ./IN/internal-localhost: loaded serial 0 Jun 20 19:21:58 ns1 named[3178]: running Jun 20 19:21:58 ns1 named[3178]: zone 0.0.10.in-addr.arpa/IN/internal: sending notifies (serial 13) Jun 20 19:21:58 ns1 named[3178]: zone metropolitanbuntu.co.za/IN/internal: sending notifies (serial 12) Jun 20 19:21:58 ns1 named[3178]: zone 194.134.41.in-addr.arpa/IN/external: sending notifies (serial 14) Jun 20 19:21:58 ns1 named[3178]: zone metropolitanbuntu.co.za/IN/external: sending notifies (serial 12) 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 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# But that does not change that your upstream has not delegated this in-addr.arpa range to you.Yeah! but I don't have IPV6 connection! Please below the following errors: root@ns1:/var/cache/bind# named-checkzone metropolitanbuntu.co.za 194.134.41.in-addr.arpa zone metropolitanbuntu.co.za/IN: NS 'ns1.metropolitanbuntu.co.za' has no address records (A or AAAA) zone metropolitanbuntu.co.za/IN: NS 'ns2.metropolitanbuntu.co.za' has no address records (A or AAAA) zone metropolitanbuntu.co.za/IN: not loaded due to errors. I hope so!Jun 20 15:09:00 ns2 named[4797]: client 10.0.0.80#3372: view
-- -- 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
