Share via

Azure DNS A record doesnt work

S H 45 Reputation points
Oct 21, 2024, 4:22 PM

So I have a domain that I purchased from Azure Domain services and added a DNS zone.

then I used A record to point the domain to IP address of my hosting provider. It worked.

Then I was trying to make email work , so to cleanup some record I deleted the DNS zone service and readded then added the A record again , but now I cant access the website as the domain is not really linked to IP and I get DNS_PROBE_FINISHED_NXDOMAIN in brwoser

when I ping my domain the ping cannot resolve the domain to ip

I waited two days , but nothing changed.

I give ttl 5 minutes but no diffrent.

Azure DNS
Azure DNS
An Azure service that enables hosting Domain Name System (DNS) domains in Azure.
699 questions
{count} votes

Accepted answer
  1. TP 99,531 Reputation points
    Oct 29, 2024, 4:09 AM

    Hi,

    First, this is happening because you deleted your Azure DNS Zone. Deleting the DNS Zone breaks DNS resolution. Creating a new zone didn't fix it, because the new zone wasn't placed on the same Azure DNS servers.

    Second, I have a script that gives you full access to your GoDaddy Domain Control Center (DCC) which allows you to make any/all changes to your domain, similar to a regular GoDaddy customer. Unfortunately, my script relies on generateSsoRequest REST API which stopped working several months ago this year (2024). You can try the REST API yourself and see if they fixed it using the "Try it" button. If it is fixed I would be happy to post my script.

    The manual way you can fix your domain is to repeatedly delete/re-create your Azure DNS Zone until it is placed on the correct DNS servers. To do this you need to first check what the "correct" DNS servers are:

    Open whois.com in your web browser, enter your domain in the whois box in upper right corner, click whois button, scroll down to bottom of results and make note of the four name servers, similar to below:

    • Name Server: NS1-37.AZURE-DNS.COM
    • Name Server: NS2-37.AZURE-DNS.NET
    • Name Server: NS3-37.AZURE-DNS.ORG
    • Name Server: NS4-37.AZURE-DNS.INFO

    From the above sample results, we see the correct name server is "37". This is our goal in this sample case--to have the DNS Zone land on 37. There are 47 (1-47). So once we know the correct number, we can carefully create the Zone, check which servers it landed on, delete it if it isn't on correct servers, create it again, etc.

    Your number will be different.

    NOTE: Azure DNS is not free. There is small cost for each zone per month, plus the number of queries (this isn't a concern in this case). I forget the minimum granularity it bills the zones at. For example, if it bills for minimum one hour and you have to create/delete a total of 100 times, then the total cost would be minimal. If the minimum is 1 month, then the cost could add up. Of course you could dispute and they would likely refund since it is same domain name.

    Please let me know if the above isn't clear. If I knew your domain name I could tell you correct server.

    Please click Accept Answer and upvote if the above was helpful.

    Thanks.

    -TP

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.