Azure Front Door and DNS Configuration for SSL “bare” (without www) Custom Domain

3
votes

I've successfully configured SSL / HTTPS for my custom domain - with a "www" in the URL - using the Azure Front Door product. That configuration required a DNS CNAME entry that forwards "www.cutegoat.com" to "cutegoat.azurefd.net"

I still have an SLL problem when I go to the same URL without the "www" prefix: "https://cutegoat.com"

My A Type DNS record still points to an IP address that Azure gave me for my App Service. I thought about changing that, but the Azure Front Door designer is pretty clear that my "Custom host name" must have a corresponding CNAME record:

Azure Front Door CNAME record required

I'm using GoDaddy for my domains and I've added a CNAME record with a source of "cutegoat.com", but I still get the Azure Front Door "CNAME record required" error. That entry let's me add a mapping to "cutegoat.com.cutegoat.com"

I think the Azure Front Door service is looking for a CNAME record with a source value of "@". But I can't enter that CNAME record, my guess is, because I have an A Type record with a source of "@" already.

enter image description here

Does anyone know the proper DNS / Azure Front Door configuration to get SSL working for my "bare" custom domain?

2
azuressldnsazure-front-door

2 Answers

4
votes

Yes, since you must have an A Type record with a source of @ already. You could not add such host @ in the CNAME record as the CNAME limitation in RFC1034

If a CNAME RR is present at a node, no other data should be present; this ensures that the data for a canonical name and its aliases cannot be different.

As far as I know, currently Azure front door does not support to add Naked or root Domains to the custom host name. If you want to improve this service, you can request feedbacks or upvote this feedback--- Add Custom Apex (Naked) Domains as front end hosts for Azure Front Door Service

3
votes

This appears to be working now, using an Alias type.

I use Azure DNS, so image is from there.

  1. Added a new A record for the @ apex
  2. Set it to an Alias
  3. The Frontdoor service now shows up under the Azure Resource.
  4. Back in Frontdoor, finished up, creating a frontend host for the apex domain then worked.

enter image description here