unable to verify domain name. Ensure you have added the record above at the registrar for doman

Question

unable to verify domain name. Ensure you have added the record above at the registrar for doman

David Acklin 0

i have added the txt to my domain registration and i still can't validate

Vinayteja Lellela 110 Reputation points Microsoft External Staff Moderator

2026-08-08T20:09:24.56+00:00
Hello David Acklin,

It does sound like you added the TXT record, but Azure still can’t validate it. For Azure App Service custom domain verification, the usual causes are DNS record issues, propagation delays, or conflicts with existing verification.

Here are the most common things to check:

1) Confirm the TXT record is exactly what Azure expects

For App Service custom domain verification, the TXT record must be:

Name/host: asuid.<sub-domain> for subdomains, or asuid for the root domain

Value: the Custom Domain Verification ID shown on the Custom Domain blade in your App Service

Also ensure you didn’t introduce typos (even a small mismatch in the TXT value or subdomain part can fail verification).

2) Make sure the other required DNS record(s) are also correct

Depending on your setup, App Service domain validation typically requires:

A record (points to the App Service incoming IP), and/or

CNAME record (points to the App Service azurewebsites.net FQDN)

If any of these are missing or point somewhere else, validation can fail.

3) Wait for DNS propagation

Even after you add the record at the registrar, validation can fail until DNS changes propagate globally.

A good way to confirm propagation is to use DNS Checker.

4) Check for stale or conflicting DNS records

Old/conflicting records can cause validation errors. For example, you may accidentally have conflicting A/CNAME records for the same name.

If you’re troubleshooting Windows resolution issues after changes, you can flush DNS cache:

ipconfig /flushdns

5) If you’re using Private DNS zones, note this limitation

Private DNS zones are not supported for custom domain binding in App Service, and this can interfere with validation.

6) Check for special-character issues

DNS standards don’t support special characters like underscores in domain names.

7) Consider Private Endpoints / networking interference

Private endpoints may interfere with domain validation, causing errors like HTTP 502 or 404. Validate DNS resolution with tcpping as suggested in the troubleshooting guidance.

8) If you have Application Gateway involved, make sure you’re using the correct pattern

There are two supported approaches:

Custom domain at the Application Gateway only (backend uses azurewebsites.net) → App Service custom domain config isn’t required

Custom domain at both Application Gateway and App Service → App Service needs its custom domain config too

Can you please update us if the action plan provided was helpful?

Should there be any follow-up questions or concerns, please let us know and we shall try to address them.

If these answer your question, click "Upvote" which may be beneficial to other community members reading this thread.
Vinayteja Lellela 110 Reputation points Microsoft External Staff Moderator

2026-08-11T18:03:55.7033333+00:00

Hello **David Acklin,

**Following up to see if you had a chance to check the above response and if it was helpful. Please let me know if you have any questions.
Vinayteja Lellela 110 Reputation points Microsoft External Staff Moderator

2026-08-12T15:58:56.06+00:00

Hello David Acklin,

Following up to see if you had a chance to check the above response and if it was helpful. Please let me know if you have any questions.

1 answer

Your answer

Vinayteja Lellela 110 Reputation points Microsoft External Staff Moderator

2026-08-11T18:03:55.7033333+00:00

Hello **David Acklin,

**Following up to see if you had a chance to check the above response and if it was helpful. Please let me know if you have any questions.
Vinayteja Lellela 110 Reputation points Microsoft External Staff Moderator

2026-08-12T15:58:56.06+00:00

Hello David Acklin,

Following up to see if you had a chance to check the above response and if it was helpful. Please let me know if you have any questions.

Answer 1

Hi @David Acklin

If you've already added the TXT record but Azure still reports “Unable to verify domain name”, I would first confirm that the record is publicly resolvable and that the host/name and value exactly match what Azure provided.

From a command prompt, try:

nslookup -type=TXT yourdomain.com

If Azure instructed you to create the verification record under a specific host such as asuid or asuid.<subdomain>, query that exact FQDN instead:

nslookup -type=TXT asuid.yourdomain.com

For example, with Azure App Service, Microsoft documents the verification TXT record as:

Root domain: asuid → Domain Verification ID
Subdomain such as www: asuid.www → Domain Verification ID

Azure needs to be able to retrieve that TXT record before it can verify ownership.

If nslookup doesn't return the expected TXT value, I would check the following:

Verify the authoritative DNS provider. Make sure you're adding the TXT record where the domain's current nameservers actually point. It's possible to manage the domain at one registrar while DNS is hosted somewhere else.
Check the Host/Name field. Some DNS providers automatically append the domain name. For example, entering asuid.example.com instead of just asuid could accidentally create something equivalent to asuid.example.com.example.com.
Check the TXT value carefully. Copy the verification value directly from Azure and make sure there are no extra spaces or other characters.
Allow for DNS propagation. Depending on the DNS provider and TTL, a newly created or modified record might not immediately be visible to Azure.
Check the authoritative nameserver directly. You can find the authoritative servers with: nslookup -type=NS yourdomain.com Then query one directly: nslookup -type=TXT asuid.yourdomain.com <authoritative-nameserver>

Microsoft's Azure DNS troubleshooting guidance specifically recommends checking whether the record exists on the authoritative DNS servers and confirming the record name and type are correct.

If you can share which Azure service you're trying to associate the domain with (App Service, Microsoft Entra ID, Static Web Apps, Communication Services, etc.) and the TXT host/name you're using, you can redact the verification token. We can tell you exactly which DNS record Azure should be looking for.

That last question is important because the screenshot is tagged Azure DNS, but the exact TXT record format depends on the Azure service doing the domain verification.

Please "Accept the Answer" if this information helped you. This will help us and others in the community as well.

Allan Solomon Mejia 7,915 Reputation points

2026-08-11T18:27:00.02+00:00

Hi @David Acklin

Please let me know if you need any further assistance. Otherwise, if the information provided has resolved your issue, please consider clicking “Accept Answer” to help others who may encounter the same problem.

Thank you!