TXT record on a different hostname
Closed this issue · 2 comments
As suggested on Hacker News, it might be wise to put the TXT records used for configuring redirects on a separate hostname, e.g. _redirect.some.hostname.com. This would prevent polluting the actual hostname and allow the use of CNAME records on subdomains (instead of A/ALIAS).
This is what I've actually implemented for my own zones at my own dns servers. I did write ut some of it in the thread at Hacker News.
Since I'm using a custom subdomain, a did not care as much about the format conflicting with others. Therefore I'm just dropping in the status code I want and the url. It is actually a little bit more complex than that, but that is outside the scope of this issue.
You should also take a look at my first attempt to tackle this.
@tellnes Neat! Thanks for that.
I actually wanted to avoid complicated syntaxes as much as possible (see #1) as this services is intended for users that can't or don't care to set up their own server + redirect rules. While it's certainly easier to parse the records in your format, I wanted to focus on the end-user. SPF and other formats cause enough confusion so I meant to keep it as simple as possible.
I'm actually already seeing a bit of confusion by people using the service (substituting redirect.name= with theirowndomain.com=) so I'm leaning more towards the proposed format in #1 along with the TXT record on _redirect.hostname.com.