search

scripting / Scripting-News

I'm starting to use GitHub for work on my blog. Why not? It's got good communication and collaboration tools. Why not hook it up to a blog?
121 stars 10 forks source link

Hover used to allow CNAMEs in place of A records? #220

Open scripting opened 3 years ago

scripting commented 3 years ago

Blog post here...

http://scripting.com/2021/08/15.html#a140054

Screen shot...

image

mcenirm commented 3 years ago

Sorry, this isn't really actionable information, but the Wayback Machine confirms that CNAME-at-apex was definitely an option that Hover used to support (but with a warning). Their DNS help page changed between 2019 and 2020, from:

Note on CNAMES: A blank (@) CNAME record will cause other blank records to fail, such as MX records, or blank A records. This can have a negative impact on the resolution of your website or sending/receiving of email.

... to:

Note: Hover is unable to support any CNAME records which use the root (@) as the hostname.

That new wording is misleading, since they choose to be "unable to support" it. They also don't support the nascent (or dead?) an equivalent to the non-standard "ANAME" DNS record.

scripting commented 3 years ago

@mcanirm -- thanks -- i just wanted to confirm that there was no workaround. it was such a nice thing.

davidkaufman commented 3 years ago

Cloudflare DNS allows this using a method they call “CNAME Flattening”, which they describe as “a better solution to this same problem”. Read more in their knowledge base about RFC-compliant support for CNAME at the root

jimfenton commented 3 years ago

I don't think it's so much a matter of Hover supporting this or not, but how resolvers would respond to this (which is out of Hover's hands). IMO it's responsible for them to not allow users to do things that wouldn't work properly, especially if it would cause an intermittent or subtle problem.