You probably need a system that allows both roots to function together. Maybe a different URL scheme: http: and https: use ICANN, httplr: and httplrs: use LR

You probably need a system that allows both roots to function together. Maybe a different URL scheme: http: and https: use ICANN, httplr: and httplrs: use LR If not specified, browser tries LR first, then falls back on ICANN. Doesn't feel as solid to me, but they could also register a placeholder TLD that would be use for redirecting requests to LR, or the other way around: google.com.lrns would tell the browser to resolve google.com in the LR root (hardcoded), or google.com.icann would tell the browser to resolve google.com in the ICANN root. When falling back from one to the other, the browser would display the hostname with the fallback TLD on it. Just some ideas off the top of my head, I haven't fully considered the implications yet.