{"id":663,"date":"2021-07-05T19:57:02","date_gmt":"2021-07-05T19:57:02","guid":{"rendered":"https:\/\/www.spktechfit.com\/?p=663"},"modified":"2021-07-05T19:57:02","modified_gmt":"2021-07-05T19:57:02","slug":"21-configure-name-resolution","status":"publish","type":"post","link":"https:\/\/www.spktechfit.com\/?p=663","title":{"rendered":"21. Configure Name Resolution"},"content":{"rendered":"

Azure DNS Services<\/h1>\n

DNS is like the phone book for the internet, it is how the domain names get translated to IP addresses.<\/p>\n

Azure DNS Service Options<\/h2>\n

There are 3 main options<\/p>\n

    \n
  1. Azure provides DNS (default)
    \n<\/b>– no configuration required
    \n– can use hostnames to connect to machines on the same VNet without requiring FQDN<\/li>\n
  2. You provide DNS (run your own DNS server)
    \n<\/b><\/li>\n
  3. Azure Private DNS<\/b>
    \n– this allows you run your own DNS services
    \n– create your own custom domain names and have them recognised by your VMs. EG: dev.local, staging.local
    \n– Only valid your own VNet, not valid on the internet
    \n– Doesn’t have to be registered
    \n– can have 2 – 34 labels: something.something
    \n– works from VNet to VNet for VMs
    \n– does not work for App Services<\/li>\n<\/ol>\n

     <\/p>\n

    Create a Private DNS Zone<\/h1>\n
      \n
    1. From the Azure portal, search for “Private DNS zones”<\/li>\n
    2. Click on Create<\/li>\n
    3. Set subscription and Resource Group<\/li>\n
    4. Give the zone a name, eg: myzone.local<\/li>\n
    5. Set the location<\/li>\n
    6. Click on Create<\/li>\n<\/ol>\n

      Link DNS zone to VNet<\/h2>\n

      To use the DNS zone we need to link it to a Virtual Network<\/p>\n

        \n
      1. Go to the newly created DNS zone<\/li>\n
      2. Go to “Virtual Network Links”<\/li>\n
      3. Click on Add<\/li>\n
      4. Give the Network Link a name<\/li>\n
      5. Set the subscription<\/li>\n
      6. Choose the VNet from the dropdown list<\/li>\n
      7. Enable Auto registration: as servers are created in the resource group they will get auto added to the DNS zone.<\/li>\n
      8. Click OK<\/li>\n<\/ol>\n

        Testing DNS Zone<\/h3>\n
          \n
        1. Now add two VM’s to the VNet that the DNS zone is linked to.<\/li>\n
        2. Go to the Private DNS Zone and you should see the two VMs records listed\u00a0 with their names and IP addresses<\/li>\n
        3. From here you can also manually add records<\/li>\n
        4. Now you should be able to access the VMs using their names<\/li>\n<\/ol>\n

           <\/p>\n

          Create a Public DNS Zone<\/h1>\n

          Before setting this up you will need a registered domain name that can be recognised from the internet. By setting this up Azure will be managing your Domains DNS.<\/p>\n

            \n
          1. From the Azure portal, search for “DNS zones”<\/li>\n
          2. Click on Create DNS Zone<\/li>\n
          3. Set subscription and Resource Group<\/li>\n
          4. Give the zone a name, this is the registered domain name<\/li>\n
          5. Set the location<\/li>\n
          6. Click on Create<\/li>\n<\/ol>\n

             <\/p>\n

            Managing the Public DNS Zone<\/h2>\n

            Go to the zone once It is created. You will see the existing records and the name servers for your domain.<\/p>\n

            Using Azure DNS for your domain:<\/p>\n

              \n
            1. Go to the registrar of your domain and login<\/li>\n
            2. Go to the DNS settings and enter the Azure Name servers found in your Azure DNS Zone<\/li>\n<\/ol>\n","protected":false},"excerpt":{"rendered":"

              Azure DNS Services DNS is like the phone book for the internet, it is how the domain names get translated to IP addresses. Azure DNS Service Options There are 3 main options Azure provides DNS (default) – no configuration required – can use hostnames to connect to machines on the same VNet without requiring FQDN […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[13,3],"tags":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.spktechfit.com\/index.php?rest_route=\/wp\/v2\/posts\/663"}],"collection":[{"href":"https:\/\/www.spktechfit.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.spktechfit.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.spktechfit.com\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.spktechfit.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=663"}],"version-history":[{"count":1,"href":"https:\/\/www.spktechfit.com\/index.php?rest_route=\/wp\/v2\/posts\/663\/revisions"}],"predecessor-version":[{"id":664,"href":"https:\/\/www.spktechfit.com\/index.php?rest_route=\/wp\/v2\/posts\/663\/revisions\/664"}],"wp:attachment":[{"href":"https:\/\/www.spktechfit.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=663"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.spktechfit.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=663"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.spktechfit.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=663"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}