[ Date Index ][
Thread Index ]
[ <= Previous by date /
thread ]
[ Next by date /
thread => ]
This sounds horribly familar of having misspelt "nameserver" in /etc/resolv.conf. gethostbyname isn't a shell command its a C funtion, try using "host". Alex. On Sat, 25 May 2002, Paul Sutton wrote:
OK grep hosts /etc/nsswitch.conf give me hosts: files dns which sounds ok to me typeing nslookup gives default server: linux address 0.0.0.0 i tried typing nslookup 80.84.72.20 gives server : [80.84.72.20] address 80.84.72.20 but this failed on repeated attempts, otoh using 80.84.64.20 i get told it can't find this address. for some reason i am now having problems with the 72.20 and 64.20 addresses. as above one worked. i really don't understand what i am doing. if I ping one of these ip addresses in the resolv.conf e,g 80.84.64.20 i send 11 packet and recieve 11, from my limited understanding of this, this is correct i dont have gethostbyname! paulsection of your nsswitch.conf $ grep hosts /etc/nsswitch.conf hosts: files nisplus nis dns for example.Indeed. A good test is to do an nslookup which does not use a resolver and host, which uses gethostbyname. If the nslookup works and host fails, the resolver config is bad. Steve -- The Mailing List for the Devon & Cornwall LUG Mail majordomo@xxxxxxxxxxxx with "unsubscribe list" in the message body to unsubscribe.-- The Mailing List for the Devon & Cornwall LUG Mail majordomo@xxxxxxxxxxxx with "unsubscribe list" in the message body to unsubscribe.
-- -- The Mailing List for the Devon & Cornwall LUG Mail majordomo@xxxxxxxxxxxx with "unsubscribe list" in the message body to unsubscribe.