<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html style="direction: ltr;">
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<style>body p { margin-bottom: 0cm; margin-top: 0pt; } </style>
</head>
<body style="direction: ltr;"
bidimailui-detected-decoding-type="latin-charset" text="#000000"
bgcolor="#ffffff">
On 20/06/2011 17:14, Lyle Giese wrote:
<blockquote cite="mid:4DFF63E6.5050905@lcrcomputer.net" type="cite">
<br>
On 06/20/11 10:01, Metropolitan College <Eric Kom> wrote:
<br>
<blockquote type="cite">Good Afternoon,
<br>
<br>
<br>
Please I used the Views, and still have the same errors:
<br>
/var/cache/bind/194.134.41.in-addr.arpa:2: ignoring out-of-zone
data
<br>
(194.134.41.in-addr.arpa)
<br>
/var/cache/bind/194.134.41.in-addr.arpa:9: ignoring out-of-zone
data
<br>
(90.194.134.41.in-addr.arpa)
<br>
/var/cache/bind/194.134.41.in-addr.arpa:10: ignoring out-of-zone
data
<br>
(91.194.134.41.in-addr.arpa)
<br>
/var/cache/bind/194.134.41.in-addr.arpa:12: ignoring out-of-zone
data
<br>
(194.134.41.in-addr.arpa)
<br>
/var/cache/bind/194.134.41.in-addr.arpa:13: ignoring out-of-zone
data
<br>
(194.134.41.in-addr.arpa)
<br>
*zone metropolitanbuntu.co.za/IN: has 0 SOA records
<br>
zone metropolitanbuntu.co.za/IN: has no NS records
<br>
zone metropolitanbuntu.co.za/IN: not loaded due to errors.*
<br>
</blockquote>
<br>
Views do not fix errors in zone files. You still need to fix the
zone files.
<br>
<br>
Change 194.134.41.in-addr.arpa to:
<br>
<br>
<br>
$TTL 3H
<br>
@ IN SOA ns1.metropolitanbuntu.co.za.
postmaster.metropolitanbuntu.co.za. (
<br>
8 ; serial
<br>
3600 ; refresh
<br>
900 ; retry
<br>
1209600 ; expire
<br>
43200) ; default_TTL
<br>
;
<br>
@ IN NS ns1.metropolitanbuntu.co.za.
<br>
@ IN NS ns2.metropolitanbuntu.co.za.
<br>
;
<br>
@ IN NS ns1.mweb.co.za.
<br>
@ IN NS ns2.mweb.co.za.
<br>
;
<br>
90 IN PTR ns1.metropolitanbuntu.co.za.
<br>
91 IN PTR ns2.metropolitanbuntu.co.za.
<br>
<br>
<br>
</blockquote>
Maybe I'm still mix up somethings because after change the settings,
<br>
the <b>grep named /etc/log/syslog</b> still showing errors:<br>
Jun 20 19:21:58 ns1 named[3178]: automatic empty zone: view
internal-localhost: 254.169.IN-ADDR.ARPA<br>
Jun 20 19:21:58 ns1 named[3178]: automatic empty zone: view
internal-localhost: 2.0.192.IN-ADDR.ARPA<br>
Jun 20 19:21:58 ns1 named[3178]: automatic empty zone: view
internal-localhost: 100.51.198.IN-ADDR.ARPA<br>
Jun 20 19:21:58 ns1 named[3178]: automatic empty zone: view
internal-localhost: 113.0.203.IN-ADDR.ARPA<br>
Jun 20 19:21:58 ns1 named[3178]: automatic empty zone: view
internal-localhost: 255.255.255.255.IN-ADDR.ARPA<br>
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<br>
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<br>
Jun 20 19:21:58 ns1 named[3178]: automatic empty zone: view
internal-localhost: D.F.IP6.ARPA<br>
Jun 20 19:21:58 ns1 named[3178]: automatic empty zone: view
internal-localhost: 8.E.F.IP6.ARPA<br>
Jun 20 19:21:58 ns1 named[3178]: automatic empty zone: view
internal-localhost: 9.E.F.IP6.ARPA<br>
Jun 20 19:21:58 ns1 named[3178]: automatic empty zone: view
internal-localhost: A.E.F.IP6.ARPA<br>
Jun 20 19:21:58 ns1 named[3178]: automatic empty zone: view
internal-localhost: B.E.F.IP6.ARPA<br>
Jun 20 19:21:58 ns1 named[3178]: automatic empty zone: view
internal-localhost: 8.B.D.0.1.0.0.2.IP6.ARPA<br>
Jun 20 19:21:58 ns1 named[3178]: command channel listening on
127.0.0.1#953<br>
Jun 20 19:21:58 ns1 named[3178]: command channel listening on
::1#953<br>
Jun 20 19:21:58 ns1 named[3178]: zone
0.0.10.in-addr.arpa/IN/internal: loaded serial 13<br>
Jun 20 19:21:58 ns1 named[3178]: zone
metropolitanbuntu.co.za/IN/internal: loaded serial 12<br>
Jun 20 19:21:58 ns1 named[3178]: managed-keys-zone ./IN/internal:
loading from master file
3bed2cb3a3acf7b6a8ef408420cc682d5520e26976d354254f528c965612054f.mkeys
failed: file not found<br>
Jun 20 19:21:58 ns1 named[3178]: managed-keys-zone ./IN/internal:
loaded serial 0<br>
Jun 20 19:21:58 ns1 named[3178]: zone
194.134.41.in-addr.arpa/IN/external: loaded serial 14<br>
Jun 20 19:21:58 ns1 named[3178]: zone
metropolitanbuntu.co.za/IN/external: loaded serial 12<br>
Jun 20 19:21:58 ns1 named[3178]: managed-keys-zone ./IN/external:
loading from master file
3c4623849a49a53911c4a3e48d8cead8a1858960bccdea7a1b978d73ec2f06d7.mkeys
failed: file not found<br>
Jun 20 19:21:58 ns1 named[3178]: managed-keys-zone ./IN/external:
loaded serial 0<br>
Jun 20 19:21:58 ns1 named[3178]: managed-keys-zone
./IN/external-root: loading from master file
67b44ff7c3d7837b9632a71c8718eba864b9b4f6fb18ec48ebdb1821e40d6bee.mkeys
failed: file not found<br>
Jun 20 19:21:58 ns1 named[3178]: managed-keys-zone
./IN/external-root: loaded serial 0<br>
Jun 20 19:21:58 ns1 named[3178]: zone
0.in-addr.arpa/IN/internal-localhost: loaded serial 1<br>
Jun 20 19:21:58 ns1 named[3178]: zone
127.in-addr.arpa/IN/internal-localhost: loaded serial 1<br>
Jun 20 19:21:58 ns1 named[3178]: zone
255.in-addr.arpa/IN/internal-localhost: loaded serial 1<br>
Jun 20 19:21:58 ns1 named[3178]: zone
localhost/IN/internal-localhost: loaded serial 2<br>
Jun 20 19:21:58 ns1 named[3178]: managed-keys-zone
./IN/internal-localhost: loading from master file
7c494d432269c6510ccdc34922639a7222454e4759be924904ddf05eaed6e546.mkeys
failed: file not found<br>
Jun 20 19:21:58 ns1 named[3178]: managed-keys-zone
./IN/internal-localhost: loaded serial 0<br>
Jun 20 19:21:58 ns1 named[3178]: running<br>
Jun 20 19:21:58 ns1 named[3178]: zone
0.0.10.in-addr.arpa/IN/internal: sending notifies (serial 13)<br>
Jun 20 19:21:58 ns1 named[3178]: zone
metropolitanbuntu.co.za/IN/internal: sending notifies (serial 12)<br>
Jun 20 19:21:58 ns1 named[3178]: zone
194.134.41.in-addr.arpa/IN/external: sending notifies (serial 14)<br>
Jun 20 19:21:58 ns1 named[3178]: zone
metropolitanbuntu.co.za/IN/external: sending notifies (serial 12)<br>
Jun 20 19:21:58 ns1 named[3178]: error (network unreachable)
resolving 'ns1.mweb.co.za/AAAA/IN': 2001:4200:ffff:a::1#53<br>
Jun 20 19:21:58 ns1 named[3178]: error (network unreachable)
resolving 'ns2.mweb.co.za/AAAA/IN': 2001:500:2e::1#53<br>
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<br>
Jun 20 19:21:58 ns1 named[3178]: error (network unreachable)
resolving 'ns0.plig.net/A/IN': 2001:503:ba3e::2:30#53<br>
Jun 20 19:21:58 ns1 named[3178]: error (network unreachable)
resolving 'ns4.iafrica.com/A/IN': 2001:dc3::35#53<br>
Jun 20 19:21:58 ns1 named[3178]: error (network unreachable)
resolving 'coza1.dnsnode.net/A/IN': 2001:500:2f::f#53<br>
Jun 20 19:21:58 ns1 named[3178]: error (network unreachable)
resolving 'coza1.dnsnode.net/A/IN': 2001:500:1::803f:235#53<br>
Jun 20 19:21:58 ns1 named[3178]: error (network unreachable)
resolving 'coza1.dnsnode.net/A/IN': 2001:503:c27::2:30#53<br>
Jun 20 19:21:58 ns1 named[3178]: error (network unreachable)
resolving 'coza1.dnsnode.net/A/IN': 2001:7fe::53#53<br>
Jun 20 19:21:58 ns1 named[3178]: error (network unreachable)
resolving 'coza1.dnsnode.net/A/IN': 2001:500:3::42#53<br>
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<br>
Jun 20 19:21:59 ns1 named[3178]: error (network unreachable)
resolving 'secdns1.posix.co.za/A/IN': 2001:42a0:1000:ff02::481#53<br>
Jun 20 19:21:59 ns1 named[3178]: error (network unreachable)
resolving 'coza1.dnsnode.net/A/IN': 2001:503:231d::2:30#53<br>
Jun 20 19:21:59 ns1 named[3178]: error (network unreachable)
resolving 'ns.orange-tree.alt.za/AAAA/IN': 2001:4200:1010::1#53<br>
Jun 20 19:21:59 ns1 named[3178]: error (network unreachable)
resolving 'rain.psg.com/A/IN': 2001:503:a83e::2:30#53<br>
Jun 20 19:21:59 ns1 named[3178]: error (network unreachable)
resolving 'arizona.edu/AAAA/IN': 2001:7fd::1#53<br>
Jun 20 19:21:59 ns1 named[3178]: error (network unreachable)
resolving 'ns1.iafrica.com/AAAA/IN': 2001:418:1::39#53<br>
Jun 20 19:21:59 ns1 named[3178]: error (network unreachable)
resolving 'nlns.globnix.net/AAAA/IN': 2a02:898:31::53:0#53<br>
Jun 20 19:22:02 ns1 named[3178]: received control channel command
'reload'<br>
Jun 20 19:22:02 ns1 named[3178]: loading configuration from
'/etc/bind/named.conf'<br>
Jun 20 19:22:02 ns1 named[3178]: reading built-in trusted keys from
file '/etc/bind/bind.keys'<br>
Jun 20 19:22:02 ns1 named[3178]: using default UDP/IPv4 port range:
[1024, 65535]<br>
Jun 20 19:22:02 ns1 named[3178]: using default UDP/IPv6 port range:
[1024, 65535]<br>
Jun 20 19:22:02 ns1 named[3178]: reloading configuration succeeded<br>
Jun 20 19:22:02 ns1 named[3178]: reloading zones succeeded<br>
root@ns1:/var/cache/bind# <br>
<br>
<blockquote cite="mid:4DFF63E6.5050905@lcrcomputer.net" type="cite">But
that does not change that your upstream has not delegated this
in-addr.arpa range to you.
<br>
<br>
<br>
<blockquote type="cite">Jun 20 15:08:31 ns2 named[4797]: network
unreachable resolving
<br>
'ns0.plig.net/AAAA/IN': 2001:503:ba3e::2:30#53
<br>
Jun 20 15:08:31 ns2 named[4797]: network unreachable resolving
<br>
'ns4.iafrica.com/A/IN': 2001:500:3::42#53
<br>
Jun 20 15:08:31 ns2 named[4797]: network unreachable resolving
<br>
'ns4.iafrica.com/AAAA/IN': 2001:7fe::53#53
<br>
Jun 20 15:08:31 ns2 named[4797]: network unreachable resolving
<br>
'ns4.iafrica.com/AAAA/IN': 2001:dc3::35#53
<br>
Jun 20 15:08:31 ns2 named[4797]: network unreachable resolving
<br>
'ns2.coza.net.za/A/IN': 2001:500:14:6055:ad::1#53
<br>
Jun 20 15:08:31 ns2 named[4797]: network unreachable resolving
<br>
'coza1.dnsnode.net/AAAA/IN': 2001:503:a83e::2:30#53
<br>
Jun 20 15:08:31 ns2 named[4797]: network unreachable resolving
<br>
'ns.orange-tree.alt.za/AAAA/IN': 2001:500:2e::1#53
<br>
Jun 20 15:08:31 ns2 named[4797]: network unreachable resolving
<br>
'ns.orange-tree.alt.za/AAAA/IN': 2001:4200:1010::1#53
<br>
Jun 20 15:08:31 ns2 named[4797]: network unreachable resolving
<br>
'rain.psg.com/AAAA/IN': 2001:503:231d::2:30#53
<br>
Jun 20 15:08:31 ns2 named[4797]: network unreachable resolving
<br>
'ns2.iafrica.com/A/IN': 2001:503:231d::2:30#53
<br>
Jun 20 15:08:31 ns2 named[4797]: network unreachable resolving
<br>
'secdns1.posix.co.za/A/IN': 2001:42a0:1000:ff02::481#53
<br>
Jun 20 15:08:31 ns2 named[4797]: network unreachable resolving
<br>
'./NS/IN': 2001:7fd::1#53
<br>
Jun 20 15:08:32 ns2 named[4797]: network unreachable resolving
<br>
'ns4.iafrica.com/A/IN': 2001:418:1::39#53
<br>
Jun 20 15:08:33 ns2 named[4797]: network unreachable resolving
<br>
'ns0.firedrake.org/A/IN': 2001:500:48::1#53
<br>
</blockquote>
<br>
The above errors are something different. It looks like your
servers may think they have IPv6 connectivity, but don't.
<br>
<br>
</blockquote>
Yeah! but I don't have IPV6 connection!<br>
<br>
Please below the following errors:<br>
<b>root@ns1:/var/cache/bind# named-checkzone metropolitanbuntu.co.za
194.134.41.in-addr.arpa <br>
</b>zone metropolitanbuntu.co.za/IN: NS
'ns1.metropolitanbuntu.co.za' has no address records (A or AAAA)<br>
zone metropolitanbuntu.co.za/IN: NS 'ns2.metropolitanbuntu.co.za'
has no address records (A or AAAA)<br>
zone metropolitanbuntu.co.za/IN: not loaded due to errors.<br>
<br>
<br>
<br>
<blockquote cite="mid:4DFF63E6.5050905@lcrcomputer.net" type="cite">
<blockquote type="cite">Jun 20 15:09:00 ns2 named[4797]: client
10.0.0.80#3372: view
<br>
external-root: received notify for zone
'metropolitanbuntu.co.za': not
<br>
authoritative
<br>
Jun 20 15:11:03 ns2 named[4797]: client 10.0.0.80#62174: view
<br>
external-root: received notify for zone
'metropolitanbuntu.co.za': not
<br>
authoritative
<br>
</blockquote>
<br>
Once you get the zones to load some of this may disappear.
<br>
</blockquote>
I hope so!<br>
<blockquote cite="mid:4DFF63E6.5050905@lcrcomputer.net" type="cite">
<br>
Lyle
<br>
<br>
_______________________________________________
<br>
Please visit <a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/bind-users">https://lists.isc.org/mailman/listinfo/bind-users</a> to
unsubscribe from this list
<br>
<br>
bind-users mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:bind-users@lists.isc.org">bind-users@lists.isc.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/bind-users">https://lists.isc.org/mailman/listinfo/bind-users</a>
<br>
</blockquote>
<p><br>
</p>
<br>
<pre class="moz-signature" cols="72">--
--
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
<a class="moz-txt-link-abbreviated" href="mailto:erickom@kom.za.net">erickom@kom.za.net</a> | <a class="moz-txt-link-abbreviated" href="mailto:erickom@namekom.co.za">erickom@namekom.co.za</a> | <a class="moz-txt-link-abbreviated" href="mailto:erickom@erickom.co.za">erickom@erickom.co.za</a>
<a class="moz-txt-link-abbreviated" href="http://www.kom.za.net">www.kom.za.net</a> | <a class="moz-txt-link-abbreviated" href="http://www.kom.za.org">www.kom.za.org</a> | <a class="moz-txt-link-abbreviated" href="http://www.erickom.co.za">www.erickom.co.za</a>
Key fingerprint: 513E E91A C243 3020 8735 09BB 2DBC 5AD7 A9DA 1EF5
</pre>
</body>
</html>