How to Setup a Name Servers visible on Internet?

[erickom at kom.za.net]

On 14/06/2011 08:56, Stephane Bortzmeyer wrote:
> On Tue, Jun 14, 2011 at 08:11:53AM +0200,
>  erickom at kom.za.net <erickom at kom.za.net> wrote
>  a message of 86 lines which said:
>
>> root at ns1:~# named-checkzone metropolitanbuntu.co.za
>> /var/cache/bind/metropolitanbntu.co.za.inv
>> /var/cache/bind/metropolitanbntu.co.za.inv:3: ignoring out-of-zone 
>> data
>> (0.0.10.in-addr.arpa)
>> /var/cache/bind/metropolitanbntu.co.za.inv:13: ignoring out-of-zone
>> data
>> (41.134.194.90)
>
> What is at line 3? At line 13? As BIND's message says, these data are
> outside of the zone.
>
Thanks a lot for your response,


>> Its doesn't point on my public IP who is 41.134.194.90 but on
>> 10.0.0.80!
>
> You did not show us the content of the zone file so everything is
> possible. What is in the zone file?
>
sorry for that, please see below the content for my reverse file data:

File: /var/cache/bind/metropolitanbntu.co.za.inv:

$ORIGIN 0.0.10.in-addr.arpa.
$TTL 864000
@               IN      SOA     ns1.metropolitanbuntu.co.za.
postmaster.metropolitanbuntu.co.za.     (
                                 201105311       ; serial
                                 3600            ; refresh
                                 900             ; retry
                                 1209600         ; expire
                                 43200)          ; default_TTL

                 IN      NS              ns1.metropolitanbuntu.co.za.
                 IN      NS              ns2.metropolitanbuntu.co.za.

41.134.194.90.  IN      PTR     ns1.metropolitanbuntu.co.za.
10.0.0.80.      IN      PTR     ns1.metropolitanbuntu.co.za.
41.134.194.91.  IN      PTR     ns2.metropolitanbuntu.co.za.
10.0.0.82.      IN      PTR     ns2.metropolitanbuntu.co.za.
10.0.0.81.      IN      PTR     www.metropolitanbuntu.co.za.
10.0.0.102.     IN      PTR     backup.metropolitanbuntu.co.za.
10.0.0.108.     IN      PTR     printer-server.metropolitanbuntu.co.za.
10.0.0.31.      IN      PTR     ldap.metropolitanbuntu.co.za.


> Also, never debug DNS with ping (because it involves other actors 
> such
> as the stub resolver and its configuration in /etc/resolv.conf). Use
> dig.
Thanks for this correction.
>
>> My ISP controlling the Cisco router remotely! so I can looking!
>
> You can or you cannot? And, anyway, this is not router's business, 
> but
> a DNS issue.
>
>


-- 
Your Truly

Eric Kom

2 Hennie Van Till, White River, 1240
erickom at kom.za.net | erickom at namekom.co.za | erickom at 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