On-Demand Sandbox Name Resolution

[talong99]

I can't seem to find a definitive answer on whether or not the VMs in an On-Demand Sandbox should be able to resolve DNS queries outside of the sandbox. I have 2 VMs in a sandbox working as expected, I just can't browse Internet sites from them. I can see established connections to the Virtual Lab on 8080 TCP, so proxy feature is working. Is the Virtual Lab supposed to be a DNS Resolver for the sandbox?


Thanks,
Todd

[talong99]

** Update: Got it working! **

1 VM is a Domain Controller which provides DNS to the other VM. I took the Domain Controller out of the Application Group, started the sandbox and now I can browse to Internet sites.

[DasGrog]

I am trying to do the exact same thing but have a related problem.

For simplicity sake, let's say I have two machines in my app group
VM-DC with AD, DNS, and DHCP roles
VM-Web with IIS
VM-Desktop

Both have control panel > internet options > connections > proxy set up to point to the Veeam gateway on port 8080

I can browse vm-web by fqdn just fine. I can browse google.com by IP. I cannot browse google.com by fqdn.

If I do a nslookup and query google.com vm-dc cannot find google.com.

If I do an nslookup, change server to 4.2.2.2 and then query google.com, it fails communication with 4.2.2.2

How do I browse google.com from within the Veeam lab?

Thank you.

[Gostev]

Please review the following support KB article and see if it helps? Thanks.