Can't resolve DNS only in one machine

Question

I have several Vista hosts each with one Ubuntu guest each running in virtual box in bridge mode.

All guests can resolve internal DNS except one.

On the problematic guest machine, if i dig @<internal dns ip> <some internal domain> it always gives timeout, but on that machine, the <internal dns ip> replies to pings and i can even telnet <internal dns ip> 53.

I've checked, and the windows firewall on the host is disabled.

Any ideas on what could be the problem?

Thanks, Joel

score 1 · Answer 1 · answered Nov 25 '09 at 14:54

1

Fixed.

The host user had installed some kind of VPN client that was blocking DNS traffic created by the guest.

answered Nov 25 '09 at 14:54

Joel

31
3

score 0 · Answer 2 · answered Nov 25 '09 at 10:11

0

Compare resolv.conf on problematic and normal machine. Also, check IP configuration.

and iptables -F

answered Nov 25 '09 at 10:11

TiFFolk

1,077
3
15
25

They are the same. iptables isn't installed. – Joel Nov 25 '09 at 11:40

score 0 · Answer 3 · answered Nov 25 '09 at 10:11

0

Usually Bridge mode problems are due to improperly configured guest network settings or a problem with DNS.
If you are trying to use DHCP and it does not work then try setting Static address and see if this helps. Selecting an external DNS server can also help.

Found here.

answered Nov 25 '09 at 10:11

Andrejs Cainikovs

1,621
1
14
20

> Selecting an external DNS server He needs to resolve internal DNS – TiFFolk Nov 25 '09 at 10:14
This is the first part of my answer. – Andrejs Cainikovs Nov 25 '09 at 10:16
it's already static. even using external dns doesn't work – Joel Nov 25 '09 at 11:41
@Joel: That means, you have problem with connecting to 53 UDP port. Try dumping traffic as RainyRat said. – TiFFolk Nov 25 '09 at 12:32

score 0 · Answer 4 · answered Nov 25 '09 at 12:24

If neither of the other two answers are helping you, you could always try grabbing some DNS traffic with Wireshark or something similar, then looking for the actual DNS conversation. Make sure to do it somewhere you can see both sides of the conversation (i.e, is the problem that DNS requests aren't making it to the server, or replies aren't making it back to the client?)

Can't resolve DNS only in one machine

4 Answers4