Operating System - Linux
1819791 Members
3166 Online
109607 Solutions
New Discussion юеВ

nslookup failure - no servers could be reached

 
MikeL_4
Super Advisor

nslookup failure - no servers could be reached

I have a new server that I cannot resolve server names through DNS... and when I try a nslookup it fails with:

[root@odccdds01 ~]# nslookup mailhost
;; connection timed out; no servers could be reached

and even if DNS isn't working why it doesn't look in /etc/hosts, as I put an entry in there also...

I have iptables off on the server:
[root@odccdds01 ~]# service iptables status
Firewall is stopped.

/etc/nssswitch.conf has following for hosts:
#hosts: db files ldap nis dns
hosts: files dns

/etc/resolv.conf contains:
search convergys.com
nameserver 155.90.250.207
nameserver 155.90.248.206

I'm not sure where to look at, or what next to try and resolve the issue.... any assistance would be appreciated...
4 REPLIES 4
Ivan Ferreira
Honored Contributor

Re: nslookup failure - no servers could be reached

The nslookup or hosts command on Linux won't search for a host in the /etc/hosts file even when specified in nsswitch.conf.

Use the ping commando to probe name resolution in that case or configure a working DNS server.

Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
Andrew Cowan
Honored Contributor

Re: nslookup failure - no servers could be reached

Mike can you simply ping these name servers? Remember that your IP parameters must be set so that there is a valid route to them.
Steven E. Protter
Exalted Contributor

Re: nslookup failure - no servers could be reached

Shalom,

The dns servers in /etc/resolv.conf are not providing answers.

Check that they can be pinged, and are providing answers. Check with their admins if needed.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
B. Hulst
Trusted Contributor

Re: nslookup failure - no servers could be reached

And you could also trace the ethernet interface with tcpdump on what packets go where and there contents...

# tcpdump