? HMMM in.addr.arpa

[Mathias Körber]

> While executing nslookup at my bind mashine I experince ....
>=20
> local:~ # nslookup
> Default Server:  l27.0.0.1.0.0.127.in-addr.arpa
> Address:  127.0.0.1

looks like an IP address used instead of a hostname in your
reverse zonefile...

> Bind is answering! ok but I think there is a error in the=20
> in-addr.arpa file.
> Right?

Looks like it..


> the /var/named/pz/192.168.66 file
>=20
> $TTL 3D
> @ IN SOA ns1local.marco.test. root.marco.test. (
> 2001010202       ; Serial
> 8H      ; Refresh
> 2H      ; Retry
> 4W      ; Expire
> 1D )    ; Minimum TTL
>=20
> NS      ns1local.marco.test.

Only 1 NS record is usually not good !

> the /var/named/pz/127.0.0 file
>=20
> $TTL 3D
> @ IN SOA @ root.marco.test. (
           ^
The first field in the SOA record (MNAME) is
supposed to contain the name of the master
nameserver, not the name of the zone!
But this not fatal..

> 1       ; Serial
> 8H      ; Refresh
> 2H      ; Retry
> 4W      ; Expire
> 1D )    ; Minimum TTL

>=20
> IN NS @

Here is one problem. '@' translates to '0.0.127.in-addr.arpa.
which is your zonename, not the name of your nameserver, which should
be the argument to the NS record..
This explains the findns error.


> 1 PTR     l27.0.0.1

The argument to the PTR record is a hostname, not an IP address:

1 PTR		localhost.

This explains the funny servername listed by nslookup.

HTH HAND
Mathias