Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have a m0n0wall router
a VMWare workstation running ubuntu
a windows 7 workstation running the VM

The ubuntu hostname is "renraku" From the windows machine I can't resolve dns automatically for this host. For example, when I

ping renraku
Ping request could not find host renraku. Please check the name and try again.

However nslookup seems to work

nslookup renraku
Server:  m0n0wall.local
Address:  192.168.123.254

Name:    renraku
Address:  192.168.123.248

I don't get how to have ping to work with hostnames. The main goal behind this is to have my web server to work with hostnames instead of ip addresses

EDIT :

ping 192.168.123.248 works

share|improve this question
    
What happens if you do ping 192.168.123.248? –  Jeff Leyser Oct 24 '10 at 22:30
1  
What is the output of ipconfig /all on your Windows box? –  Steven Monday Oct 24 '10 at 22:45
add comment

4 Answers

Did you try a ipconfig /flushdns on the windows machine?

share|improve this answer
add comment

Your DNS client is not appending the DNS suffix to it's queries, probably because it's not configured with one.

It appears that the moonwall router will append the DNS suffix of the zone it hosts to an unqualified query when running nslookup on the queryer but not when another program uses the DNS client on the queryer.

share|improve this answer
add comment

Do you have multiple connections configured on the Windows box? Do all of them have 192.168.123.254 as the DNS server?

share|improve this answer
    
I only have one physical cable. I have multiple adapters since VMWare creates many by default. The adapter I'm using has the correct DNS server –  Eric Oct 24 '10 at 22:29
add comment

Not a direct answer to your problem, but a couple things to consider:

  1. nslookup and other bind related tools do not use the same configuration code as most system programs. In particular they don't read /etc/hosts; but typically, unlike your situation, that means that ping will find a host that nslookup won't. However it's possible that non standard content in /etc/resolv.conf could be interpreted differently by either code paths, causing the problem you're seeing. You should post the content of /etc/resolv.conf

  2. nslookup is deprecated, use "host" instead

share|improve this answer
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.