Summary: DNS resolution for a Class A address

Nigel Henry (nhenry@scopus.com)
Wed, 28 May 1997 07:44:57 -0700

Original question:

We have just set up our first internal Class A address in the 10
range for a new server at one of our remote sites and I've added the
new
address to the host file and its PTR record to its appropriate
db.<ip.address>. When we do a ping, both of the IP address and the
name
of the server, we see that it is alive. But we can't do an nslookup of
the server or the IP address.

What am I missing?

=======================================================
>From Frank Pardo <fpardo@tisny.com>

I hope I don't insult you by stating the obvious... Did you remember to
"kill -HUP <pid of in.named>"? -- No insult taken. Thank you.
------------------------------------------------------------------------
----------------------------------------

>From Rahul Roy [roy@bluestone.com]

You will need to add the new DNS server name in /etc/resolv.conf as
well....

regards

Rahul Thank you, Rahul
------------------------------------------------------------------------
---------------------------------------
>From Joel Lee [jlee@thomas.com]

You didn't tell us what system are you using. Anyway, if you have
install the BIND distribution (that replaces libc.*, libresolv.*...) and

if you are using nslookup from the local distribution, it would try to
use the old routine to do a query. That may fail. Use dig to see if
you can do a query, if you can, try to use the BIND version of nslookup.

P.S. nslookup uses its own resolver routine. So even if you can use ping

it doesn't mean that nslookup will work.

-- Joel Thank you, Joel
------------------------------------------------------------------------
---------------------------------------
>From Daniel Baker [dbaker@cuckoo.com]

Did you increment the eserver?

Did you download the latest version of bind?

Did you do an NDC reload?

Is it specified in /etc/named.boot
etc
etc
etc

Daniel Thank you, Daniel
------------------------------------------------------------------------
---------------------------------------
>From Subir Grewal [subir@indiaserver.com]

Since you didn't mention named.boot, that's what came to mind, maybe
this
is just a baby answer you don't need to hear, but here goes.

You need to declare yourself primary for network 10. You should do it
in
/etc/named.boot, the following line should do it:

primary 10.IN-ADDR.ARPA db.10

similarly, your nameserver needs to know that it is primary for whatever
domain that machine is in. As long as all the other system syou manage
come to your machine for name service, you should not have a problem
(the
secondaries will need to know that they are secondaries for the
appropriate network and domain, or else they'll be querying the root
nameservers).

Subir Grewal Thank you, Subir