Azure virtual networking DNS/gateway not working

Question

Hi all,

I recently deployed a new virtual machine to a virtual network and when I remote desktop in and try to resolve/ping anything, it just simply fails.

I've created a DNS server (10.17.3.10) but when I use nslookup with that server from the virtual machine, the DNS request simply times out.

The gateway doesn't work either (10.17.3.1).  I can't ping any IPs, can't connect to any websites, etc.

Seems like the virtual networking is a bit buggy.

Any ideas?

Answer 1

Are you saying you're running your own DNS server? Did you look at the "DNS Server Requirements" documentation (http://msdn.microsoft.com/en-us/library/windowsazure/jj156088.aspx#bkmk_BYODNS)? The most significant requirement seems like DDNS.

What DNS software are you using?

Answer 2

Hi

Please leverage tutorials available below to setup VMs and DNS servers in a Virtual Network.

http://www.windowsazure.com/en-us/manage/services/networking/

The tutorial on setting up a DC replica in the virtual networkhas PowerShell snippets that will help you setup VMs that point to your DNS server.

You will also have to add a rule to your VM's firewall to allow ICMPv4 on the inbound path.

Thank you.

Answer 3

Yes, I used these tutorials to set it up, but it provides no assistance.  I simply can't route any traffic outbound from the server.  It has the correct IP configuration for the virtual network, the correct DNS server and the correct default gateway.

I'm not running my own DNS server - I've created one in the Azure management.  DNS requests time out, traffic can't be routed out (tracert gets no response from the default gateway).

I'd really like to get a decent VM setup, but it seems like there are still a few bugs being ironed out.

Answer 4

I think you're confused about how this works, but it could certainly be me who is confused. :-)

If you've specified in the management UI that you want to use a DNS server at a specific IP address, you have to be running a DNS server at that address.

In other words, I don't believe there is such a thing as "I've created [a DNS server] in the Azure management." I believe your options are to either you use Windows Azure's built-in name resolution or run your own DNS server.

Answer 5

No you're right - I was confused.  My mistake.

Still, I can't actually route any traffic (i.e. with a direct IP).  Not sure how to troubleshoot that aspect of it.

Answer 6

Can you elaborate what you tried? Did you ping an public IP, or Azure IP? The default gateway of your VM is not configured to respond to ping. 

---

Jason Chen, Windows Azure PM