locked
Delete Post RRS feed

  • Question

  • Delete Post
    • Edited by T88W Friday, December 11, 2015 10:51 AM Delete Post
    Wednesday, May 20, 2015 10:51 AM

Answers


  • Hello T88W,

    The DNS Server is failing to resolve the Domain names and hence you are not able to ping using the names.

    You will need to reset the DNS settings from the Azure Portal to promote the Virtual Machine as the Domain Name Server.

    I request you to follow the steps below to do that:

    1.Reset the DNS forwarder setting on the new DC/DNS server.

    a.In Server Manager, click Tools > DNS.
    b.In DNS Manager, right-click the name of the DNS server and click Properties.
    c.On the Forwarders tab, click the IP address of the forwarder and click Edit. Select the IP address and click Delete.
    d.Click OK to close the editor and Ok again to close the DNS server properties.

    2.Update the DNS server setting for the virtual network from the Azure Management portal.

    a Go to the Azure management portal and click Virtual Networks > double-click the virtual network you created > Configure > DNS servers, type the name and the DIP of one of the VMs that runs the DC/DNS server role and click Save.

    b.Select the VM and click Restart to trigger the VM to configure DNS resolver settings with the IP address of the new DNS server.

    Thanks,
    Syed Irfan Hussain


    Thursday, May 21, 2015 9:42 AM
  • Hi T88W,

    First, you will need to reserve an ip address for the DC. The information can be found here.

    Get-AzureVM -ServiceName Cloudservicename Name VMNAME |Set-AzureSubnet –SubnetNames SUBNETNAME| Set-AzureStaticVNetIP -IPAddress 192.168.44.4| Update-AzureVM

    Now in the Management portal go to >> Virtual networks > Dns server Tab and add this DC’s internal ipaddress as part of the registered Dns server ipaddress.

    Once this Operations completes you need to assign this DNs server to the Vnet /Subnet. Go to Virtual network >> Click on the Vnet >> Configure option

    Delete the Forwarders which are not required.Once this completes restart the DC and the Vms inside the Vnet to get the new DNS configuration.

    Please let me know what happens.

    Regards,

    Mekh.


    Thursday, May 21, 2015 9:44 AM

All replies


  • Hello T88W,

    The DNS Server is failing to resolve the Domain names and hence you are not able to ping using the names.

    You will need to reset the DNS settings from the Azure Portal to promote the Virtual Machine as the Domain Name Server.

    I request you to follow the steps below to do that:

    1.Reset the DNS forwarder setting on the new DC/DNS server.

    a.In Server Manager, click Tools > DNS.
    b.In DNS Manager, right-click the name of the DNS server and click Properties.
    c.On the Forwarders tab, click the IP address of the forwarder and click Edit. Select the IP address and click Delete.
    d.Click OK to close the editor and Ok again to close the DNS server properties.

    2.Update the DNS server setting for the virtual network from the Azure Management portal.

    a Go to the Azure management portal and click Virtual Networks > double-click the virtual network you created > Configure > DNS servers, type the name and the DIP of one of the VMs that runs the DC/DNS server role and click Save.

    b.Select the VM and click Restart to trigger the VM to configure DNS resolver settings with the IP address of the new DNS server.

    Thanks,
    Syed Irfan Hussain


    Thursday, May 21, 2015 9:42 AM
  • Hi T88W,

    First, you will need to reserve an ip address for the DC. The information can be found here.

    Get-AzureVM -ServiceName Cloudservicename Name VMNAME |Set-AzureSubnet –SubnetNames SUBNETNAME| Set-AzureStaticVNetIP -IPAddress 192.168.44.4| Update-AzureVM

    Now in the Management portal go to >> Virtual networks > Dns server Tab and add this DC’s internal ipaddress as part of the registered Dns server ipaddress.

    Once this Operations completes you need to assign this DNs server to the Vnet /Subnet. Go to Virtual network >> Click on the Vnet >> Configure option

    Delete the Forwarders which are not required.Once this completes restart the DC and the Vms inside the Vnet to get the new DNS configuration.

    Please let me know what happens.

    Regards,

    Mekh.


    Thursday, May 21, 2015 9:44 AM