Almost the same thing as a few years ago happened:
server 1.0.10 NAT: DNS not working
xerces8 wrote (Nov 2, 2009 1:40 PM):
I just updated VMWare Server from 1.0.9 to 1.0.10 and now DNS does not work in guest that have set up NAT networking.
Tried Ubuntu 9.04 and 9.10, also Windows XP. All using default (automatic) network settings.
I can ping any numerical address, but DNS resolution does not work.
If I set manually a DNS server offered by my ISP in the guests, then it works.
Is this some regression with 1.0.10 ? I'm sure the same VM worked before the update.
Regards,
David
This time I was using VMWare Player 5.0.2 on Windows 8 Pro 64 bit.
I had a few VMs working fine.
Then I updated to Player 6.0.0, created a new VM for Windows8 and installed Windows 8.1 Preview into it.
There I noticed tha DNS does not work;
- ping 8.8.8.8 (Google's DNS server) - works
- nslookup www.najdi.si returns:
C:\Users\stein>nslookup www.najdi.si Server: UnKnown Address: 192.168.91.2 Name: www.najdi.si.localdomain Addresses: 89.143.229.238
- ping www.najdi.si gives:
Ping request could not find host www.najdi.si. Please check the name and try again.
- ipconfig /all output:
C:\Users\stein>ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : clearblue Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : localdomain Ethernet adapter Ethernet0: Connection-specific DNS Suffix . : localdomain Description . . . . . . . . . . . : Intel(R) 82574L Gigabit Network Connectio n Physical Address. . . . . . . . . : 00-0C-29-7A-CD-FB DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::8c9b:97f9:f57a:3e7c%5(Preferred) IPv4 Address. . . . . . . . . . . : 192.168.91.128(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Lease Obtained. . . . . . . . . . : 22. september 2013 3:17:54 Lease Expires . . . . . . . . . . : 22. september 2013 3:47:53 Default Gateway . . . . . . . . . : 192.168.91.2 DHCP Server . . . . . . . . . . . : 192.168.91.254 DHCPv6 IAID . . . . . . . . . . . : 83889193 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-19-CF-F0-F8-00-0C-29-7A-CD-FB DNS Servers . . . . . . . . . . . : 192.168.91.2 Primary WINS Server . . . . . . . : 192.168.91.2 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.localdomain: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : localdomain Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes
A Ubuntu guest VM also had problems with DNS resolution (worked fine before), so I decided to revert back to Player version 5.0.2.
It did not help, so I uninstalled it, cleaned up ( "Manually cleaning a Windows system" at VMware KB: Cleaning up after an incomplete uninstallation on a Windows host ) and then reinstalled Player v5.0.2.
After that a quick test with http://www.sysresccd.org ISO worked, but when I tried the Windows 8.1 VM the problems started again.
I started the SystemRescueCd again and I got:
% ping rtv.si PING rtv.si.localdomain (91.185.213.134) 56(84) bytes of data. 64 bytes from 91.185.213.134: icmp_seq=1 ttl=128 time=13.1 ms 64 bytes from 91.185.213.134: icmp_seq=2 ttl=128 time=13.9 ms
This is slightly better, but still not correct (it should say "PING rtv.si" , not "PING rtv.si.localdomain").
It seems the DNS server of VMWare Player is sending broken replies.
Any idea how to resolve this?