topic Re: named & DNS problem in Operating System - HP-UX

named & DNS problem

parolin franco — Tue, 21 May 2002 07:37:58 GMT

Sorry for my english,
We have a server DNS (Aserver.pippo.it) and we have configured on db.cache :
. 99999999 IN NS bserver
bserver.pluto.it. 99999999 IN A 172.16.123.50

the nslookup response for a machine present on the pluto.it is:
nslookup wsD
Using /etc/hosts on: Aserver

looking up FILES
Trying DNS
*** localhost can't find wsD: Server failed
or
nslookup wsD.puto.it
Using /etc/hosts on: Aserver

looking up FILES
Trying DNS
*** localhost can't find wsD.pluto.it: Server failed

thanks

Re: named & DNS problem

Hartmut Lang — Tue, 21 May 2002 08:45:45 GMT

I think your question is: "why can't we lookup wsD"?

I don't know about Uppercase in hostnames, but it might be a problem (who can help)?

I would suggest you start to ask your primary server, if he knows the hostname:
nslookup wsD bserver.

Then you should do the same with your Caching-Server:
nslookup wsD Aserver.

And you should give more information about your /etc/resolv.conf
and
/etc/nsswitch.conf

Hartmut

Re: named & DNS problem

parolin franco — Tue, 21 May 2002 08:56:10 GMT

the messages is the same with name "wsd"
the resolv.conf is:
search pippo.it pluto.it
nameserver 127.0.0.1 # server pippo.it
nameserver 172.16.123.50 #server pluto.it
nameserver 172.16.159.116 # server pluto.it
the nsswithch is:
hosts: files [NOTFOUND=continue UNAVAIL=continue TRYAGAIN=continue] dns [NOTFOUND=return UNAVAIL=continue TRYAGAIN=return]

Bye

Re: named & DNS problem

sven verhaegen — Tue, 21 May 2002 09:31:18 GMT

In this you are not sure wether this is related to the setup of the caching server or to a fault in the primary DNS server itself , try looking up the same name on the server it self if that works its the cache server, named allows for tracing , use NSLOOKUP without parameyers it will put you in interactive mode

then type 'set debug'

you can then do lookups and see nslookup try and describe the steps it does perhaps this generates more info

type 'set no debug' to stop tracing

CTRL-D to exit

Re: named & DNS problem

U.SivaKumar_2 — Tue, 21 May 2002 09:39:33 GMT

hi,
DNS names are not case-sensitive.
Server.mydomain.com is same as server.mydomain.com
Can you do this
#ping wsD.puto.it.
#nslookup WsD.puto.it.
get back with results.

regards,
U.SivaKumar

Re: named & DNS problem

Hartmut Lang — Tue, 21 May 2002 10:16:53 GMT

Again,

check if your primary server can resolve the hostname:

nslookup wsd aserver

If primary server can resolve the name, check if caching server is running (do you see the named process?).

How did you start the named (give us the content of named.boot)?

Hartmut

Re: named & DNS problem

parolin franco — Tue, 21 May 2002 11:09:09 GMT

the machine if I ping with the name or FQDN no response, if i ping with IP address I have

Re: named & DNS problem

parolin franco — Tue, 21 May 2002 11:12:08 GMT

The server DNS if I ping "wsd" with the name or FQDN or IP address I have the correct response.
The debug stop the trace on our root server.

Re: named & DNS problem

parolin franco — Tue, 21 May 2002 11:18:28 GMT

Hi,

If I make nslookup of aserver on aserver I receive the answer by root server instead of the same aserver.

Re: named & DNS problem

Hartmut Lang — Tue, 21 May 2002 12:08:15 GMT

Sorry, but i'm a little bit confused, about what you are doing.

Just to clearify:
You have two DNS domains (pippo.it and pluto.it). Right?

You have two DNS servers aserver and bserver. Which server servs which domain?

The db.cache file you where talking about in your first post. Is it part of one of these servers or of a third server?

Hartmut

Re: named & DNS problem

parolin franco — Tue, 21 May 2002 14:00:05 GMT

we have 2 domain:
aserver and aserver1 for pippo.pluto.it
bserver for pluto.it

on the db.cache of pippo.it, I specify :
. 99999999 IN NS bserver.pluto.it.
bserver.pluto.it 99999999 IN A 172.16.99.16
"secondary"
. 99999999 IN NS cserver.pluto.it.
cserver.pluto.it 99999999 IN A 172.16.99.17

the machine "wsd" is defined in pluto.it.
the result of nslookup wsd is:

servera.pluto.it can't find wsd:server failed.
this is our configuration.

Re: named & DNS problem

Sachin Patel — Tue, 21 May 2002 15:21:16 GMT

Hi Parolin,

Your db.cache file should be like this. You have your d.cache file wrong.

; Initial cache data for root domain servers.
;
; <<>> DiG 2.0 <<>> @ns.internic.net . ns Last update 2/1/96

;; ANSWERS:
. 518400 NS G.ROOT-SERVERS.NET.
. 518400 NS A.ROOT-SERVERS.NET.
. 518400 NS H.ROOT-SERVERS.NET.
. 518400 NS B.ROOT-SERVERS.NET.
. 518400 NS C.ROOT-SERVERS.NET.
. 518400 NS D.ROOT-SERVERS.NET.
. 518400 NS E.ROOT-SERVERS.NET.
. 518400 NS I.ROOT-SERVERS.NET.
. 518400 NS F.ROOT-SERVERS.NET.
;
; Prep the cache (hotwire the addresses). Order does not matter.
;
;; ADDITIONAL RECORDS:
G.ROOT-SERVERS.NET. 518400 A 192.112.36.4
A.ROOT-SERVERS.NET. 518400 A 198.41.0.4
H.ROOT-SERVERS.NET. 518400 A 128.63.2.53
B.ROOT-SERVERS.NET. 518400 A 128.9.0.107
C.ROOT-SERVERS.NET. 518400 A 192.33.4.12
D.ROOT-SERVERS.NET. 518400 A 128.8.10.90
E.ROOT-SERVERS.NET. 518400 A 192.203.230.10
I.ROOT-SERVERS.NET. 518400 A 192.36.148.17
F.ROOT-SERVERS.NET. 518400 A 192.5.5.241

Sachin

Re: named & DNS problem

MANOJ SRIVASTAVA — Wed, 22 May 2002 03:29:28 GMT

Hi Parolin

The issue is like this , if you ahve configured in nsswitch.conf file to look for dns server to resolve the name then it will look in the resolv.conf for the name server and then read that server to resolve the name and IP for wsD. Now if you knwo the IP for this server you can just add the entry in /etc/
hosts. and rename /etc/resolv.conf to say resoolv.old and try nslookup the server will resolve using /etc/hosts , then may be u can look at the solving the nameserver issue.

Manoj Srivastava