topic Re: Problem With Hostname Resolving in Operating System - Linux

Problem With Hostname Resolving

Karthik S S — Thu, 24 Jul 2003 08:56:17 GMT

Hi,

I have posted this also at,

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xde2b169fe7a43a40a81e8d2347320349,00.html

Hi,

We have a linux machine with proper network configuration. nslookup is working ok when you try to resolve other hostnames. But ping fails unless otherwise you give a FQDN.

i.e

ping node1 - fails
ping node1.domain.com - passes

What could be the reason. Problem is not only with the ping but due to this automounting of shares also fails. Extract from messages file,

-----------------------------------------------
[root@linux-pc /etc]# more /var/log/messages
Jul 20 04:25:17 linux-pc syslogd 1.4-0: restart.
Jul 20 04:24:55 linux-pc nis_cachemgr[571]: Could not lookup cbin.eng.: NIS+ servers unreachable
Jul 20 04:25:54 linux-pc last message repeated 6 times
Jul 20 04:25:55 linux-pc automount[691]: attempting to mount entry /auto/ecs
Jul 20 04:26:04 linux-pc nis_cachemgr[571]: Could not lookup cbin.eng.: NIS+ servers unreachable
Jul 20 04:26:05 linux-pc automount[9274]: mount(nfs): entry ecs: host coffee: lookup failure
Jul 20 04:26:14 linux-pc nis_cachemgr[571]: Could not lookup cbin.eng.: NIS+ servers unreachable

-----------------------------------------------

Though it says NIS server is not reachable I am able to resolve other tables like passwd, group. DNS is used for hosts. /etc/resolv.conf and /etc/nsswitch.conf are just fine.

Pl. help

Thanks
Karthik S S

Re: Problem With Hostname Resolving

Pete Randall — Thu, 24 Jul 2003 09:01:31 GMT

Karthik,

What do your /etc/resolv.conf and /etc/nsswitch.conf files look like?

Pete

Re: Problem With Hostname Resolving

Karthik S S — Thu, 24 Jul 2003 09:09:39 GMT

Pete,
/etc/resolv.conf
search domain.com
nameserver x.x.x.x
domain domain.com

The point here is Nslookup just works fine even without FQDN

/etc/nsswitch.conf

hosts: files dns

all other services are configured for "files nisplus"

Thanks,
Karthik

Re: Problem With Hostname Resolving

Karthik S S — Thu, 24 Jul 2003 09:11:59 GMT

Pete,

It may sound funny ... but it is working now after a reboot :-))
(It was not a so critical system ... so I could afford rebooting it)
-Karthik S S

Re: Problem With Hostname Resolving

Karthik S S — Thu, 24 Jul 2003 09:21:08 GMT

But I have another question 4 u .. :-)

I was wondering if there is any command to find out the replication status between a Master NIS+ and a Replicated NIS+ Server.

Thanks
Karthik S S

Re: Problem With Hostname Resolving

Pete Randall — Thu, 24 Jul 2003 09:23:49 GMT

Karthik,

Sorry, I don't do NIS. We tried it years ago and found it to be more trouble than it was worth.

I hope things continue to work now that you've re-booted.

Pete

Re: Problem With Hostname Resolving

Steven E. Protter — Thu, 24 Jul 2003 11:18:29 GMT

Check the man pages on the yp commands.

Most of the important stuff is there on HP-UX. I'll check a book and get back to you with specifics when I get to the office.

SEP

Re: Problem With Hostname Resolving

Karthik S S — Thu, 24 Jul 2003 11:43:11 GMT

Hi Stevan,

"nisping -u" does something similar but only shows the last update time.

Thanks,
Karthik S S

Re: Problem With Hostname Resolving

Balaji N — Thu, 24 Jul 2003 13:50:20 GMT

hey
by any chance was the domainname altered by command name.

and hence ping was not working.

once u rebooted, the domain name was set properly and worked?

just a thought.
-balaji

Re: Problem With Hostname Resolving

Karthik S S — Fri, 25 Jul 2003 03:21:29 GMT

No domain name is set properly. Also "search domain.name" is defined in /etc/resolv.conf.

Regards,
Karthik S S