How to Setup a Name Servers visible on Internet?

[Lyle Giese]

On 06/20/11 10:01, Metropolitan College <Eric Kom> wrote:
> Good Afternoon,
>
>
> Please I used the Views, and still have the same errors:
> /var/cache/bind/194.134.41.in-addr.arpa:2: ignoring out-of-zone data
> (194.134.41.in-addr.arpa)
> /var/cache/bind/194.134.41.in-addr.arpa:9: ignoring out-of-zone data
> (90.194.134.41.in-addr.arpa)
> /var/cache/bind/194.134.41.in-addr.arpa:10: ignoring out-of-zone data
> (91.194.134.41.in-addr.arpa)
> /var/cache/bind/194.134.41.in-addr.arpa:12: ignoring out-of-zone data
> (194.134.41.in-addr.arpa)
> /var/cache/bind/194.134.41.in-addr.arpa:13: ignoring out-of-zone data
> (194.134.41.in-addr.arpa)
> *zone metropolitanbuntu.co.za/IN: has 0 SOA records
> zone metropolitanbuntu.co.za/IN: has no NS records
> zone metropolitanbuntu.co.za/IN: not loaded due to errors.*

Views do not fix errors in zone files.  You still need to fix the zone 
files.

Change 194.134.41.in-addr.arpa to:


$TTL 3H
@ 	IN	SOA	ns1.metropolitanbuntu.co.za.	postmaster.metropolitanbuntu.co.za.	(
				8		; serial
				3600		; refresh
				900		; retry
				1209600		; expire
				43200)		; default_TTL
;
@	IN	NS	ns1.metropolitanbuntu.co.za.
@       IN      NS      ns2.metropolitanbuntu.co.za.
;
@ 	IN 	NS	ns1.mweb.co.za.
@ 	IN	NS	ns2.mweb.co.za.
;
90		IN	PTR	ns1.metropolitanbuntu.co.za.
91		IN	PTR	ns2.metropolitanbuntu.co.za.


But that does not change that your upstream has not delegated this 
in-addr.arpa range to you.


> Jun 20 15:08:31 ns2 named[4797]: network unreachable resolving
> 'ns0.plig.net/AAAA/IN': 2001:503:ba3e::2:30#53
> Jun 20 15:08:31 ns2 named[4797]: network unreachable resolving
> 'ns4.iafrica.com/A/IN': 2001:500:3::42#53
> Jun 20 15:08:31 ns2 named[4797]: network unreachable resolving
> 'ns4.iafrica.com/AAAA/IN': 2001:7fe::53#53
> Jun 20 15:08:31 ns2 named[4797]: network unreachable resolving
> 'ns4.iafrica.com/AAAA/IN': 2001:dc3::35#53
> Jun 20 15:08:31 ns2 named[4797]: network unreachable resolving
> 'ns2.coza.net.za/A/IN': 2001:500:14:6055:ad::1#53
> Jun 20 15:08:31 ns2 named[4797]: network unreachable resolving
> 'coza1.dnsnode.net/AAAA/IN': 2001:503:a83e::2:30#53
> Jun 20 15:08:31 ns2 named[4797]: network unreachable resolving
> 'ns.orange-tree.alt.za/AAAA/IN': 2001:500:2e::1#53
> Jun 20 15:08:31 ns2 named[4797]: network unreachable resolving
> 'ns.orange-tree.alt.za/AAAA/IN': 2001:4200:1010::1#53
> Jun 20 15:08:31 ns2 named[4797]: network unreachable resolving
> 'rain.psg.com/AAAA/IN': 2001:503:231d::2:30#53
> Jun 20 15:08:31 ns2 named[4797]: network unreachable resolving
> 'ns2.iafrica.com/A/IN': 2001:503:231d::2:30#53
> Jun 20 15:08:31 ns2 named[4797]: network unreachable resolving
> 'secdns1.posix.co.za/A/IN': 2001:42a0:1000:ff02::481#53
> Jun 20 15:08:31 ns2 named[4797]: network unreachable resolving
> './NS/IN': 2001:7fd::1#53
> Jun 20 15:08:32 ns2 named[4797]: network unreachable resolving
> 'ns4.iafrica.com/A/IN': 2001:418:1::39#53
> Jun 20 15:08:33 ns2 named[4797]: network unreachable resolving
> 'ns0.firedrake.org/A/IN': 2001:500:48::1#53

The above errors are something different.  It looks like your servers 
may think they have IPv6 connectivity, but don't.

> Jun 20 15:09:00 ns2 named[4797]: client 10.0.0.80#3372: view
> external-root: received notify for zone 'metropolitanbuntu.co.za': not
> authoritative
> Jun 20 15:11:03 ns2 named[4797]: client 10.0.0.80#62174: view
> external-root: received notify for zone 'metropolitanbuntu.co.za': not
> authoritative

Once you get the zones to load some of this may disappear.

Lyle