Hi community, I created a new Azure DNS Zone under *.eastus.cloudapp.azure.com and I've waited several hours but it doesn't appear to be propagating outside of the Azure name server that is assigned to (ns1-##.azure-dns.com/net/org/info). I need to create several DNS zones under *.eastus.cloudapp.azure.com in order to generate/validate my LetsEncrypt certificates. Without having the DNS records propagated outside of *.azure-dns.com, the LetsEncrypt validators are unable to generate my certificate requests as it can't resolve to the Azure DNS zone that I created. How long does it take to propagate my records outside of the Azure DNS? I know that within Azure environment, it takes 60 seconds according to the documentation but doesn't mention anything else besides that. Lastly, I am not using a custom domain, I wanted to use the generic Azure DNS zones as it fits my needs for now. Thanks in advance,

Hi, You don't own the domain, so it's not going to propagate outside of the DNS servers you have created the records on. To do what you want you will need to have a custom domain that you own. That way, when someone does a DNS lookup the request will be routed to the DNS servers you specify at your registrar. Please click Accept Answer and upvote if the above was helpful. If something is unclear or you need further assistance please add a comment. Thanks. -TP

Gotcha, I appreciate your suggestion. I've marked it as answered.

Azure DNS Zones propagation time

Accepted answer

TP 78,826 Reputation points

2024-03-06T01:48:16.41+00:00

Hi,

You don't own the domain, so it's not going to propagate outside of the DNS servers you have created the records on.

To do what you want you will need to have a custom domain that you own. That way, when someone does a DNS lookup the request will be routed to the DNS servers you specify at your registrar.

Please click Accept Answer and upvote if the above was helpful. If something is unclear or you need further assistance please add a comment.

Thanks.

-TP
Please sign in to rate this answer.
Jay T 20 Reputation points

2024-03-06T02:27:28.0566667+00:00

Then my question is, how come some of my previous Azure DNS zones are able to resolve outside of the Azure NS? The configuration is exactly the same as the new ones I created (not a custom domain).

TP 78,826 Reputation points

2024-03-06T02:50:10.62+00:00

Can you give me a specific example? By specific example, I'm not asking for you to post the name you used, but to describe the records you created, how precisely you tested that they were resolvable from the global internet, etc.

Please note you can create a DNS name for your VM. For example, testvm.eastus.cloudapp.azure.com would be globally resolvable.

This VM DNS name capability is not the same as creating a new DNS zone under *.eastus.cloudapp.azure.com, creating DNS records (e.g. A, CNAME, TXT, MX, etc.) and then being able to resolve these records from anywhere on the global internet.

Jay T 20 Reputation points

2024-03-06T04:24:46.0966667+00:00

I'm aware that I can create a DNS label name for my VM and it's publicly accessible but I need another globally resolvable DNS A record hence why I wanted to create a DNS zone.

Can you explain why is creating a DNS zone not the same as giving a DNS name label to the VM? Are DNS zones are only internally resolvable within Azure environment and DNS name labels are globally resolvable?

Lastly, can you please provide a suggestion to make this solution work without using a custom domain? All I want is having two publicly accessible A records pointing to the same VM public IP address.

Thanks in advance.

TP 78,826 Reputation points

2024-03-07T03:58:18.0333333+00:00

First, you can purchase a .com custom domain for $9.15/year and be able to create whatever DNS records you would like and obtain free certificates from Let's Encrypt, within minutes. I wanted to mention that in case you were thinking it is expensive and/or too much of a hassle to get a custom domain.

Second, when you create a DNS name for a VM, Azure is creating the A record for you, under the covers, as an included feature. Unfortunately it doesn't allow you to create multiple names for same VM under *.<region>.cloudapp.azure.com.

Perhaps there is some third-party free dynamic DNS service or similar that would allow you to point a FQDN (under their domain) to an Azure VM's IP address and you could do what you want that way.

My recommendation would be to use custom domain, but I understand you've said you don't want to do that.

Think of DNS zone as administrative/legal object that allows the owner to create official records for that domain. The owner of a domain gets to decide the list of official DNS servers for that domain. Only these official designated DNS servers will be authoritative for resolving lookups for the various records.

A DNS zone is the container for A records, as well as other record types.
Sign in to comment

Share via

Azure DNS Zones propagation time

1 additional answer