How to Setup a Name Servers visible on Internet?

[Lyle Giese]

On 06/20/11 12:31, Metropolitan College <Eric Kom> 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]: 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

Managed keys are something else.  See this message:

https://lists.isc.org/pipermail/bind-users/2010-October/081294.html

> Jun 20 19:21:58 ns1 named[3178]: zone
> 194.134.41.in-addr.arpa/IN/external: loaded serial 14

Looks to me like the in-addr.arpa zone is loading now.

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

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 at 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.