VirtualBox

Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#6833 closed defect (fixed)

DNS Proxy Problems: ID Mismatch -> fixed in svn

Reported by: jjnoakes Owned by:
Component: network/NAT Version: VirtualBox 3.2.0
Keywords: dns proxy id mismatch Cc:
Guest type: Linux Host type: Windows

Description

Host: Windows XP Guest: Ubuntu 10.04 LTS VirtualBox: 3.2.0

I have one NAT network and one host-only network.

I set up DNS Proxy:

$ VBoxManage modifyvm "MyVM" --natdnsproxy1 on

and then I booted up.

In the Ubuntu guest, I can't resolve domain names.

$ cat /etc/resolv.conf nameserver 10.0.2.3 domain search

$ nslookup

server

Default server: 10.0.2.3 Address: 10.0.2.3#53

google.com

;; Warning: ID mismatch: expected ID 9436, got 5376

If I change the nameserver to my ISP's, or anything else (like OpenDNS), things are fine.

My suspicion is that the DNS Proxy is taking in the DNS request from the guest (with ID 9436 in this case), making a request to the Windows resolver (which uses a different ID), getting a response (with that different ID) and forwarding that response directly back to the guest (with the wrong ID). The guest resolver won't accept it.

Or is something else going on?

Either way, this looks to be a bug in the DNS Proxy.

Attachments (1)

vbox.log (49.0 KB ) - added by malattia 15 years ago.
Virtual Box logfile

Download all attachments as: .zip

Change History (9)

comment:1 by vasily Levchenko, 15 years ago

Component: networknetwork/NAT

Thanks for report. Could you please add the log?

comment:2 by malattia, 15 years ago

Having the same problem, here is some data:

[mattia@localhost ~]$ cat /etc/resolv.conf
; generated by /sbin/dhclient-script
search <dnssuffix>
nameserver 10.0.2.3

Mismatch:

[mattia@localhost ~]$ dig google.com
;; Warning: ID mismatch: expected ID 1382, got 55557
;; Warning: ID mismatch: expected ID 1382, got 55557
;; Warning: ID mismatch: expected ID 1382, got 55557
;; Warning: ID mismatch: expected ID 1382, got 55813

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> google.com
;; global options:  printcmd
;; connection timed out; no servers could be reached

on the real DNS:

[mattia@localhost ~]$ dig @<myrealdns> google.com

; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2 <<>> @<myrealdns> google.com
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 1963
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com.                    IN      A

;; AUTHORITY SECTION:
com.                    3540    IN      SOA     <...>. 2010053001 28800 7200 604800 3600

;; Query time: 7 msec
;; SERVER: <myrealdns>#53(<myrealdns>)
;; WHEN: Tue Jun  1 15:08:30 2010
;; MSG SIZE  rcvd: 83

In addition, on the host machine (XP) I can see the DNS queries returning a valid reply to the host's DNS proxy when I get the ID mismatch warnings. Unsurprisingly the transaction IDs on the host match those that dig is complaining about in the guest (0xd905 and 0xda05).

comment:3 by vasily Levchenko, 15 years ago

thanks for reporting. I've been able reproduce the issue. anyway I'd like to get log file, to provide right bits for verification.

by malattia, 15 years ago

Attachment: vbox.log added

Virtual Box logfile

comment:5 by vasily Levchenko, 15 years ago

Summary: DNS Proxy Problems: ID MismatchDNS Proxy Problems: ID Mismatch -> fixed in svn

comment:6 by Frank Mehnert, 15 years ago

Resolution: fixed
Status: newclosed

comment:7 by malattia, 15 years ago

works fine now, thanks!

comment:8 by Frank Mehnert, 15 years ago

Thanks for the feedback!

Note: See TracTickets for help on using tickets.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette