nslookup using localhost.0.0.0.127.in-addr.arpa as a nameserver

[Kevin Darcy]

The name shown for the nameserver ultimately doesn't matter much as long
as the queries are going to the right address. Apparently the address of
whatever nameserver your resolver is using reverse-maps back to the name
"0.0.0.127.in-addr.arpa". If you want that to map back to something more
reasonable, then you need to set up the appropriate reverse zone files. It
is not strictly necessary to be delegated the reverse domain, as long as
all of the servers which need to answer for the reverse zone(s) internally
are explicitly configured with it. If you have a *lot* of internal
servers, which would make explicit configuration difficult to maintain, or
wish to provide this reverse-zone information to the Internet, then you
would need to be delegated the reverse domain.


- Kevin

Star Night wrote:

> Hi
> I recently set up my DNS servers. my domain is registered. But nslookup
> deafults to using 0.0.0.127.in-addr.arpa as the default name server. I
> have two static IP's and using them for my primary & secondary name
> servers. the lookups of internal and external hosts works fine with
> 0.0.0.127.in-addr.arpa. But I am wondering why its not using my
> primary server(say xxx.domain.com). Does reverse lookup needs to be in
> place before name server is operational. I can provide with more
> information.
>
> The reverse lookup is is not delegated. Will this cause any problems?
> Also outside name servers are not able to lookup my domain.
>
> Any help is appreciated.
>
> Thanks
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.