nslookup works, ping #'s works, ping domain fails?

nslookup works, ping #'s works, ping domain fails?

Post by Paul Nelso » Sun, 07 Jun 1998 04:00:00



I just upgraded a RH4.2 box to RH 5.0. I can ping ip numbers but when I try
to use a domain name, it can't be resolved


ping: unknown host teleport.com

When I try nslookup, it resolves the number right away.


Default Server:  c3p0.mesd.k12.or.us
Address:  198.236.68.21

Quote:> teleport.com

Server:  c3p0.mesd.k12.or.us
Address:  198.236.68.21

Name:    teleport.com
Addresses:  192.108.254.12, 192.108.254.10

If I just ping the IP # it works fine.


PING 192.108.254.12 (192.108.254.12): 56 data bytes
64 bytes from 192.108.254.12: icmp_seq=0 ttl=244 time=53.0 ms
64 bytes from 192.108.254.12: icmp_seq=1 ttl=244 time=44.8 ms

I have other RH5 linux boxes on our network and they are working just fine.
This is the only one giving me a headache.

Where should I go from here?

;-) Paul

 
 
 

nslookup works, ping #'s works, ping domain fails?

Post by Stephen Meyle » Mon, 08 Jun 1998 04:00:00


Try checking for an /etc/nsswitch.conf file on the upgraded box.  It
determines the order of name resolution on a RedHat 5.0 box.  nslookup
would work fine without it as it is specifically written to utilise DNS.

Hope this helps.

Steve


> I just upgraded a RH4.2 box to RH 5.0. I can ping ip numbers but when I try
> to use a domain name, it can't be resolved


> ping: unknown host teleport.com

> When I try nslookup, it resolves the number right away.


> Default Server:  c3p0.mesd.k12.or.us
> Address:  198.236.68.21

> > teleport.com
> Server:  c3p0.mesd.k12.or.us
> Address:  198.236.68.21

> Name:    teleport.com
> Addresses:  192.108.254.12, 192.108.254.10

> If I just ping the IP # it works fine.


> PING 192.108.254.12 (192.108.254.12): 56 data bytes
> 64 bytes from 192.108.254.12: icmp_seq=0 ttl=244 time=53.0 ms
> 64 bytes from 192.108.254.12: icmp_seq=1 ttl=244 time=44.8 ms

> I have other RH5 linux boxes on our network and they are working just fine.
> This is the only one giving me a headache.

> Where should I go from here?

> ;-) Paul

--
"The biggest cause of trouble in the world today is that the stupid
people are
so sure about things and the intelligent folks are so full of doubts."
-- Bertrand Russell

 
 
 

1. PLEASE HELP: PING, DNS AND NSLOOKUP - NSLOOKUP GOOD PING BAD

The DNS is configured on a server that is standalone.  I am running
Solaris 2.5 and have tried DNS 4.93 (BETA, REL) 4.94P1.  

When I perform a NSLOOKUP on a domain, i.e nslookup www.xxx.com the  
correct information is returned.  When I try and ping www.xxx.com
I receive an unknown host error.  This is true for all of the

A type records.  The local server has an entry in the root.cache file.
The name server complains.  The identical DNS works fine on a node
connected to the internet.

        Can any one possibly point out the error in my ways?

Thanks in advance.

2. ultrix: establishing disk quotas & limiting su

3. Why ping fails but nslookup works?

4. doubling the number of inodes on a partition

5. ping localhost fails; ping 127.0.0.1 works

6. 3.1.1 and S3 hang, any ideas?

7. Ping by IP fails, Ping by name works???

8. 3c509 card

9. Problem: ping works, ping -R fails

10. nslookup works, ping doesn't

11. nslookup works but ping does'nt !?

12. Can't ping by name, But NSLOOKUP works perfectly.

13. nslookup works, but ping, finger, telnet, et al don't : HELP!