Azure App Service Domain / Azure DNS not resolving

Question

I have a domain (gigkeeping.com) registered as an Azure App Service Domain for quite some time, and have been using Azure DNS. Things worked fine for months until I tried adding a new custom domain name -- which failed. I noticed that, despite everything in Azure looking fine, my domain is no longer registered with a name server, and there is no (public) DNS resolution for the domain. This is over days of waiting, so I know it isn't the classic "wait 24-72 hours for DNS" issue. In all cases, Azure DNS shows my records (A, CNAME, etc.), but those records are never propagated.

According to https://whoisfreaks.com/tools/dns/lookup/gigkeeping.com -- there's no DNS registered for the domain.

{
    "status": true,
    "queryTime": "2024-06-28 21:33:16",
    "domainName": "gigkeeping.com",
    "domainRegistered": true,
    "dnsTypes": {},
    "dnsRecords": []
}

I checked WHOIS at https://whoisfreaks.com/tools/whois/lookup/gigkeeping.com and it does show the name servers for Azure DNS. But, no NS records, no SOA record, in DNS. Odd, because they exist in Azure DNS.

"name_servers": [
        "ns1-34.azure-dns.com",
        "ns2-34.azure-dns.net",
        "ns3-34.azure-dns.org",
        "ns4-34.azure-dns.info"
    ]

I've tried deleting and recreating the Azure DNS service; this did not change anything -- domain simply doesn't exist in name servers.

I've thought about trying to transfer the domain name itself to GoDaddy, but good luck figuring that out in 2024, as it seems all the advanced domain management options are gone from the Azure portal.

Any thoughts on how to resolve this?

Answer 1

Hi Brian DeMarzo,

Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

I understand that you are facing issues with your domain gigkeeping.com.

I could see the Azure dns server are used as authoritative name servers and that is seen even the DNS trace i run for NS records as seen below.

.			516823	IN	NS	a.root-servers.net.
.			516823	IN	NS	b.root-servers.net.
.			516823	IN	NS	c.root-servers.net.
.			516823	IN	NS	d.root-servers.net.
.			516823	IN	NS	e.root-servers.net.
.			516823	IN	NS	f.root-servers.net.
.			516823	IN	NS	g.root-servers.net.
.			516823	IN	NS	h.root-servers.net.
.			516823	IN	NS	i.root-servers.net.
.			516823	IN	NS	j.root-servers.net.
.			516823	IN	NS	k.root-servers.net.
.			516823	IN	NS	l.root-servers.net.
.			516823	IN	NS	m.root-servers.net.
.			516823	IN	RRSIG	NS 8 0 518400 20240714050000 20240701040000 20038 . tue9fr/U44M2xYLqifEEk4R1OTb/475DVJF3/7z7FioqlE7CMw4WhudX Y9QqWm6gUH6aFWR80TXpX6gGU2JtYbPXUpYv6HC7ET6yg4TlW8K7kW9T p22V7Dq5HU3Jazlh5JCKcMBqYNIgtGzSJ9h6GszOswjiQXBzD+admZaK 1VvRsU8HBGH6iGBF9ZQei6rHIddoVQag1bA2rsOqzmZ4uiYUDSeK2kwk 2BZK/QoUwHUI0OlQylsD8DLXqb+w0EYjP6iPSYonSnDjY1snQVLNslBf Z8AqqXaCHrkFo7Uj+yU4AekwI7czpW0k9/DoMR1UfuSbM5Ru2mcIbQWY jQCsNQ==
;; Received 525 bytes from 1.1.1.1#53(1.1.1.1) in 3 ms

com.			172800	IN	NS	h.gtld-servers.net.
com.			172800	IN	NS	m.gtld-servers.net.
com.			172800	IN	NS	a.gtld-servers.net.
com.			172800	IN	NS	e.gtld-servers.net.
com.			172800	IN	NS	g.gtld-servers.net.
com.			172800	IN	NS	i.gtld-servers.net.
com.			172800	IN	NS	f.gtld-servers.net.
com.			172800	IN	NS	b.gtld-servers.net.
com.			172800	IN	NS	j.gtld-servers.net.
com.			172800	IN	NS	c.gtld-servers.net.
com.			172800	IN	NS	d.gtld-servers.net.
com.			172800	IN	NS	k.gtld-servers.net.
com.			172800	IN	NS	l.gtld-servers.net.
com.			86400	IN	DS	19718 13 2 8ACBB0CD28F41250A80A491389424D341522D946B0DA0C0291F2D3D7 71D7805A
com.			86400	IN	RRSIG	DS 8 1 86400 20240714050000 20240701040000 20038 . s37zEwBeSxbi+cbkLo9A2WGAN7I8sJJyqITe6ROwW6VI26DSJ61zZXEE RWkzIAjfmk0GAmTC8wDchOp3vMP+Vzvdq3dP9egWgt/cZt3LkWw1PSaG ZMPAnOdlsZHhP14UuLaBHlssLey1bDKEkr268YkbRxsIc32Vwb1vjRw+ 7RGeDzQmNZa93hI2XuTpYLZ5Vexzzhh1NX3odwjHtShVr7Kccp/fNTqt geTvG3ejkd2hDmnIuVrSFMG9D4QBzv9820bibuON8B6Abaaq7/0nigvr iIlevArhUfedVwSK7rl5FPFGzeJ/xm1xcX0rXEHbBRD/ZuKcUNJjgAlZ n11KrQ==
;; Received 1174 bytes from 192.33.4.12#53(c.root-servers.net) in 1 ms

gigkeeping.com.		172800	IN	NS	ns4-34.azure-dns.info.
gigkeeping.com.		172800	IN	NS	ns1-34.azure-dns.com.
gigkeeping.com.		172800	IN	NS	ns2-34.azure-dns.net.
gigkeeping.com.		172800	IN	NS	ns3-34.azure-dns.org.

CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN NSEC3 1 1 0 - CK0Q2D6NI4I7EQH8NA30NS61O48UL8G5 NS SOA RRSIG DNSKEY NSEC3PARAM
CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN RRSIG NSEC3 13 2 86400 20240707002457 20240629231457 956 com. fUqDTwkfdL3McvJaDUQI8nJAOwYVk7quI5jYU4rLvVQofgJEZ7GJjNZL 7BY4hkQh/xmIjp1M5Ec+n5vVLxAt7A==
KEOP4M6PNB5N7916A0B1ASAUFRD9PDJ9.com. 86400 IN NSEC3 1 1 0 - KEOQ46N51H067D93LVB1OKUQ7V5NH0QR NS DS RRSIG
KEOP4M6PNB5N7916A0B1ASAUFRD9PDJ9.com. 86400 IN RRSIG NSEC3 13 2 86400 20240708015910 20240701004910 956 com. A4CvcwsoEsqgud+lZzfQhaO8yLKd9PaeuHWTHRW4yiZyY+vo6R7txPdE xqp+jZ3w521T88XIlUhXF3p0s5Ii7A==
;; Received 578 bytes from 192.5.6.30#53(a.gtld-servers.net) in 85 ms

;; Received 43 bytes from 150.171.16.34#53(ns2-34.azure-dns.net) in 87 ms

However, i think the DNS domain gigkeeping.com is redacted by the Domain Registrar itself which seems Go daddy in your case.

Kindly refer the below URL to check yourself.

https://lookup.icann.org/en/lookup

        [
            "contact-uri",
            {},
            "uri",
            "https://www.secureserver.net/whois?plid=1387&domain=gigkeeping.com"
          ]
        ]
      ],
      "roles": [
        "administrative"
      ],
      "events": [
        {
          "eventAction": "last changed",
          "eventDate": "2024-06-29T07:40:09Z"
        }
      ],
      "remarks": [
        {
          "title": "REDACTED FOR PRIVACY",
          "type": "object truncated due to authorization",
          "description": [
            "Some of the data in this object has been removed."
          ]

Hence it is advised to kindly also engage with your domain Registrar in this case.

If the below answer addressed your query, please don’t forget to click "Accept the answer" and Up-Vote for the same, which might be beneficial to other community members reading this thread. And, if you have any further query do let us know.

Thanks,

Ujjawal Tyagi