locked
DNS for Azure VM RRS feed

  • Question

  • I'm told my DNS for the VM I created needs to have an IP address of 10.0.0.4.  Anybody know how to get this to be that?
    Wednesday, April 9, 2014 2:14 AM

Answers

  • this is the case only if you have deployed your own DNS server on that IP address.

    If you've just set up some VM with or without a Virtual Network, your machines get IP addresses assigned by DHCP through Azure, and also get an Azure-provided DNS server assigned.

    If you want to use your own DNS server (such as for AD deployments), you will typically deploy an AD DS host first in your Azure service, and this (first) VM gets the 10.0.0.4 address (given that you selected the 10.0.0.0 address space for your VNET). Therefore instead of using the Azure-DNS, you will rather configure the DNS server to be 10.0.0.4 . However keep in mind, you don't have to or should change any IP option in the VM itself, as it's assigned by Azure DHCP. To configure the DNS, go in the Azure Portal to --> Networks --> DNS Server, create an entry for your DNS server, and also remember to assigned that server entry to the corresponding VNET (Networks --> Virtual Networks --> yournetworkhere --> Configure --> DNS Servers.

    There is also some good documentation whether you want to use Azure-provided name resolution or roll your own http://msdn.microsoft.com/en-US/library/azure/jj156088.aspx

    • Proposed as answer by Susie Long Sunday, April 13, 2014 8:46 AM
    • Marked as answer by Susie Long Monday, April 21, 2014 2:41 AM
    Wednesday, April 9, 2014 4:26 PM
  • Hi,
    In addition, if you want to specify the static internal IP for an Azure VM which is going to run DNS, you can create your VM using PowerShell cmdlets. More information:
    Configure a Static Internal IP Address (DIP) for a VM
    Best regards,
    Susie

    • Proposed as answer by Susie Long Sunday, April 13, 2014 8:46 AM
    • Marked as answer by Susie Long Monday, April 21, 2014 2:41 AM
    Thursday, April 10, 2014 1:33 AM

All replies

  • this is the case only if you have deployed your own DNS server on that IP address.

    If you've just set up some VM with or without a Virtual Network, your machines get IP addresses assigned by DHCP through Azure, and also get an Azure-provided DNS server assigned.

    If you want to use your own DNS server (such as for AD deployments), you will typically deploy an AD DS host first in your Azure service, and this (first) VM gets the 10.0.0.4 address (given that you selected the 10.0.0.0 address space for your VNET). Therefore instead of using the Azure-DNS, you will rather configure the DNS server to be 10.0.0.4 . However keep in mind, you don't have to or should change any IP option in the VM itself, as it's assigned by Azure DHCP. To configure the DNS, go in the Azure Portal to --> Networks --> DNS Server, create an entry for your DNS server, and also remember to assigned that server entry to the corresponding VNET (Networks --> Virtual Networks --> yournetworkhere --> Configure --> DNS Servers.

    There is also some good documentation whether you want to use Azure-provided name resolution or roll your own http://msdn.microsoft.com/en-US/library/azure/jj156088.aspx

    • Proposed as answer by Susie Long Sunday, April 13, 2014 8:46 AM
    • Marked as answer by Susie Long Monday, April 21, 2014 2:41 AM
    Wednesday, April 9, 2014 4:26 PM
  • Hi,
    In addition, if you want to specify the static internal IP for an Azure VM which is going to run DNS, you can create your VM using PowerShell cmdlets. More information:
    Configure a Static Internal IP Address (DIP) for a VM
    Best regards,
    Susie

    • Proposed as answer by Susie Long Sunday, April 13, 2014 8:46 AM
    • Marked as answer by Susie Long Monday, April 21, 2014 2:41 AM
    Thursday, April 10, 2014 1:33 AM