Page 1 of 1
External DNS not resolving names
Posted: 29. Oct 2019, 19:09
by tnagdn
I'm using a DHCP server in WIndows Server 2003. I can ping external IP addresses but not the resolved names, for example:
ping 216.58.201.174 (google.com IP) = WORKS
ping google.com = not working
I'm inside a NAT Network (not NAT) with the following settings
Code: Select all
Name: LARED
IP: 10.0.2.0/24
DHCP Support: NO
IP/V6 Support: NO
The server has the following configuration:
Code: Select all
IP Address: 10.0.2.10
Mask: 255.0.0.0
Gateway: 10.0.2.1
DNS: 8.8.8.8
The thing is, changing the DNS won't fix the problem (I tried openDNS and 1.1.1.1 too)
What is the problem here?
Re: External DNS not resolving names
Posted: 29. Oct 2019, 19:27
by socratis
tnagdn wrote:I'm using a DHCP server in WIndows Server 2003
Then why do yo think it's a VirtualBox problem?
tnagdn wrote:I'm inside a NAT Network (not NAT)
Why? Simplify your setup, don't go NATnetwork+External DHCP server, unless you know your networking details. Try the Internal option, or turn-off the Win2003 DHCP server. I still don't understand why are you doing the way you're doing it...
I already told you that
before...
Re: External DNS not resolving names
Posted: 29. Oct 2019, 19:34
by tnagdn
Excuse me, I cannot simplify it since I have to use NAT Network by the imposition of my superior, otherwise I would be using the NAT option
I think I didn't explain very well, I'm not using an "external DHCP server", I'm using a virtual machine as DHCP server. Now the DHCP options are working perfectly due to your help in the last post but I still not able to resolve external sites.
I also have network restrictions, could that be the problem? I'm forced to use a specific DNS that works in the native machine, but in the VM I can't even ping it. Even if I set that DNS in the VM it won't work...
I just wanna make sure if it's my problem or an external restriction
Re: External DNS not resolving names
Posted: 29. Oct 2019, 20:11
by socratis
tnagdn wrote:I'm forced to use a specific DNS that works in the native machine, but in the VM I can't even ping it.
Wait, what? You can't even ping the external DNS? That's not good...
Re: External DNS not resolving names
Posted: 29. Oct 2019, 20:22
by tnagdn
In the host machine, I am forced to use a specific DNS server, ping works and it resolves names without problem
In the virtual machine with the past configuration, ping works but I can't resolve names, no matter which DNS I'm using
Re: External DNS not resolving names
Posted: 1. Nov 2019, 21:27
by scottgus1
Make a new different NAT network with no extras, just accept whatever defaults Virtualbox wants to use. Attach a new no-extra-config guest to this new NAT network, use whatever defaults the guest OS chooses for its network. See if you can ping IP's and names. If you can, then Virtualbox is working and the problem is a config issue in your 2003 guest.