Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.
I understand that you are reaching the limits with Azure Public DNS Zone.
Per your verbatim,
- You have 10 existing Zones.
- In each zone, you have created a couple of DNS record sets (one "@" and one "www")
- Both of these record sets are created as "Alias Record Set" with target set as "Azure Resource"
- So, in total, you now have 20 "Alias Record Set" pointing to the same "Azure Resource" (Public IP Address)
So, I believe the limit has been met as documented here : Azure DNS limits
I see two workarounds for this.
#1 If you are using a Standard Public IP
- In this case, the IP address will not change
- As Standard SKU IPs are always Static.
- So, instead of using a "Alias Record Set", you can directly use the IP Address of the Standard Public IP.
- You can leave the "domain.com" as it is to point to the "Alias Record Set" but change the "www.domain.com" to point to the Public IP Address of the VM.
#2 For the FQDN, "www.domain.com" - Create a CNAME to "domain.com"
i.e,
- apex domain :
- "www" sub domain :
- This should automatically take care of any IP Changes as you are not explicitly specifying the IP anywhere unlike #1.
- Using Dig interface :
Hope this helps.
Please let us know if you need more info on this.
Cheers,
Kapil