|
Can't resolve my name when under VMware workstation
I have a VMware workstation on main host running 'CentOS' and 'Windows Server 2008.'
The Main host is behind enterprise network environment with Cisco/Juniper routers and switches. I have an AT&T router/modem that acts my home's gateway that provides internet access to all the devices. (I sometimes connect directly to my AT&T router/modem when my Cisco/Juniper collections are off, but during other times, connect off of Cisco/Juniper).
When connected directly to AT&T router/modem, the main Host computer can resolve by name and its DNS server is the AT&T router/modem's interface. (AT&T router resolves by name and returns it to the host).
The Cisco router's WAN interface gets DHCP from the AT&T router and probably gets the DNS server of the AT&T router/modem as well. AT&T router/modem itself uses AT&T dns.
But the DHCP scopes of the Cisco router define dns-servers as 8.8.8.8 and 8.8.8.4. (To bypass AT&T router/modem and handle dns requests directly from the servers). So all the hosts and guests OS get those addresses. Main host connected off Cisco router can resolve by name with 8.8.8.8/8.8.8.4
Now for guests OS. When under "Bridged Networking," CentOS gets DHCP address and DNS from the Cisco router, just like the Main Host is. (Host acting like a switch in this case). But when I do that, main Host can resolve by name (like going to cnn.com) but CentOS can't resolve by name.
When I change the virtual network adapter setting to "NAT Networking with the Host," it can resolve by name and everything works. But I need the guest OS to directly be bridged to the main network.
What am I doing wrong here?
Not sure what to do next. I tried messing around with DNS servers and still no clue.
Any firewall blocking dns-53? Then how is CentOS resolving when connected via NAT with host?
(Win 2008 hosts can resolve by name when under "Bridged")
Thanks.
Last edited by sndlt; 11-28-2014 at 01:29 PM.
|
