Opened 11 years ago
Closed 10 years ago
#12152 closed defect (obsolete)
DNS fails in NAT mode only after host reboots
Reported by: | SpectrumBX | Owned by: | |
---|---|---|---|
Component: | network/NAT | Version: | VirtualBox 4.2.18 |
Keywords: | DNS failure | Cc: | |
Guest type: | all | Host type: | all |
Description
Hi,
System: Host - Windows 7 running VirtualBox 4.2.18 R88780
Guest OS - Windows 2000 w/NAT networking.
Problem: VirtualBox is freshly installed onto the host PC; then the guest machine is immediately imported (OVA format). DNS resolution within the guest operating system works perfectly (i.e. can resolve names on the network).
If the host machine is powered off / rebooted and the guest machine is re-powered up then DNS will fail to resolve any names on the network. Other computers on the network are still accessible by IP address only. Reinstallation of VirtualBox at this point will again yield working DNS.
I have tried using both DNSproxy and DNShostresolver on the VM with no effect. It is also worth noting that there are 3 DNS servers on the network.
Change History (3)
comment:1 by , 11 years ago
comment:3 by , 10 years ago
Resolution: | → obsolete |
---|---|
Status: | new → closed |
Further info / temporary fix:
Discovered that if the VirtualBox Host only ethernet adaptor is disabled and then re-enabled in the host OS (in this case Win7) then the DNS resolution starts working again.
I Also discovered that if the VirtualBox Host only ethernet adaptor is left in the disabled state then DNS resolution works perfectly. Since I am not using any bridged networking or host only networking this solution has worked for me; however people using mixed networking types will require a better fix.