I am trying to remember why you can’t simply set a CNAME from your domain to
<canisterid>.ic0.app, and the relevant components (boundary node and certifying service worker) will query DNS to read the CNAME to get the canister id to resolve to…
Ah, there is TLS. The boundary node would have to aquire a certificate for that domain on the fly. But is that a problem these days, with letsencrypt being a thing?
And then there is the problem that top level domains can’t be CNAMEs. How about a
TXT entry then?
Of course, NIH’ing some completely new system, nicely on chain with governance and everything would be fun. But to move the IC forward and make it usable with arbitrary domains, just matching what, say, GitHub Pages has been supporting for a long while, maybe be prudent? And it only affects the two boundary components.