What each record actually looks like
Pick a type to see a real zone-file line and what it does. All of them are available on the free plan.
@ALIASyour-project.onrender.com.
A CNAME cannot exist at the apex of a zone, because a zone apex must also carry SOA and NS records. ALIAS solves that: keep your SOA and NS where they belong and point the apex at any hostname, which resolves like an A record.
Rejected next to ALIAS
- A
- AAAA
- CNAME
- ALIAS (duplicate target)
Two address records at one name is ambiguous, and a CNAME there would make the zone self-referential. Both are refused at validation.
Allowed next to ALIAS
- NS
- SOA
- MX
- TXT
- SRV
- CAA
These describe something other than the address at that name, so an ALIAS alongside them is unambiguous and is accepted.
Delegate to these two
Both names resolve to the same anycast address, so a query is answered by whichever network reaches it first rather than by one far-away origin. You can confirm that yourself:
dig +short dns1.int.yt @1.1.1.1 dig +short dns2.int.yt @1.1.1.1
dns1.int.yt
First name in the delegation
anycastdns2.int.yt
Second name in the delegation
anycastPublish these records on your own zone
1,000 records per domain, free. Point your nameservers at dns1.int.yt and dns2.int.yt and you are authoritative.