blog | ~wheresalice

Infrastructure updates for wheresalice.info

• migrated my main site to European hosting, a European dns provider, and removed the dependency on Cloudflare. It is still a .info domain though, which does depend on the USA
• added HTTP/3 support to subdomains serving dynamic content
• added HTTPS records for wheresalice.info (which means it theoretically works in IPv6 on modern browsers, but probably doesn't)

Why can't we support IPv6 for legacy browsers and other applications? A very good question

• RFC2181 says we can't use a CNAME for the apex. Specifically, it can't be used in combination with NS and SOA records (and historically MX records)
• AAAA records exist for the hostname we would CNAME to but aren't documented as being usable by the hosting provider
• ALIAS records aren't a real thing, they just dynamically return the relevant A/AAAA records. This is a problem because the nameservers would all need the private keys for dnssec signing

Let's hope that HTTPS records become more widely used