Unable to get correct DNS to respond

[ROSS HANSON]

Hello
I have a HPUX rp3440. The ip is 10.5.6.10
I also have 3 other HPUX boxes with ips of
10.5.6.x. The resolv.conf file has the same DNS
information on all the boxes. The rp3440 will not resolve anything. When I do a nslookup it sits there, the prompt, and then fails.
Yes, I am able to ping this dns server and traceroute to it. I can even telnet to it. I have checked the Nic card setting and all the cards are set the same. I am running out of ideas for this problem. Need help, suggestions

[john kingsley]

What does your /etc/nsswitch.conf look like?

[Sridhar Bhaskarla]

Hi,

Compare your /etc/nsswitch.conf file with other three servers and sync it up if they do not match. Also verify the entries in /etc/resolv.conf for syntax errors.

When you do 'nslookup somehostname', it should see it waiting somewhere like

Using /etc/hosts on: your_host

looking up FILES
Trying DNS
Trying NIS

If it is waiting at "Trying DNS", then a good chance is that the IP address you got for the DNS server in /etc/resolv.conf is bad. In that case it should eventually timeout in approximately 90 seconds.

-Sri

[Victor Fridyev]

Look at your /etc/nsswitch.conf. If you use DNS, there should be the following string in the file:

hosts: dns [NOTFOUND=continue] files
or
hosts: files [NOTFOUND=continue] dns

The order depends on your preference.

HTH

[ROSS HANSON]

My resolv.conf file is:

search mydns.righthere.com
nameserver 10.5.6.20

My nswithch.conf file looks like:

hosts: dns [NOTFOUND=continue UNAVAIL=return TRYAGAIN=return] files

This is also what my other HPUX boxes have on them

[Geoff Wild]

Do you have the FQDN in /etc/hosts for this server (10.5.6.10)?

Rgds...Geoff

[RAC_1]

nslookup

On nslookup prompt type policy

What it says??

Anil

[ROSS HANSON]

At the prompt I type:
# nslookup

It goes to the next line and sits there for the longest time. When it does finally come to the > policy
it shows me: dns [RCRR] files [RRRR]

[RAC_1]

type nslook
which nslookup
chsum nslookup

Compare the results with the nslookup on other systems.

Whar are the perms on /etc/nsswitch.conf file??

Anil

[RAC_1]

type nslook
which nslookup
cksum nslookup

Compare the results with the nslookup on other systems.

Whar are the perms on /etc/nsswitch.conf file??

Anil

[Sundar_7]

I think the search keyword is the culprit.

search keyword should only contain the domain name and not your DNS server's FQDN.

change your resolv.conf to reflect

domain .com
nameserver

[ROSS HANSON]

The permission on /etc/nsswitch.conf file are:
-r--r--r-- 1 root sys /etc/nsswitch.conf

This matches two other HPUX servers I checked on

# which nslookup
/usr/bin/nslookup

#cksum /usr/bin/nslookup
3062363663 122880 /usr/bin/nslookup

These both reflect, but are not exact, of which is on my other machine also

I changed the /etc/resolv.conf to read
domain .......
nameserver ......

I received the same results ( the hung at the prompt stuff mentioned earlier)

[RAC_1]

Iam tempted to use tusc.

tusc -vfp "nslookup"
(Get tusc from porting centre)

Let's see where it is getting stuck.

Anil

[Rgomes]

Hi,

Can you stop/start named and send the named startup logs from syslog.

Regards,
Richard