Memories of .us

2 days ago (computer.rip)

I love the old interent. I'll confess I have three locality domains and they are wonderful.

I'll confess I have successfully registered a locality domain this year (2025) and it was a little bit fun to go through the weird hoops to get this new domain registered.

I'm also working on/helping out a registrar whose owned died and his widow is resolving what to do with the non-profit.

A related quaint couple of blogs[1][2] if you're feeling nostalgic and motivated to register your own:

[1] https://sleepless.seattle.wa.us/2022-07-01-110449/

[2] http://nguyen.cincinnati.oh.us/locality.html

Subdivided geographic TLDs are still common in Ontario govts, such as gov.on.ca [1] and tdsb.on.ca for Toronto schools.[2] Both are still in common use.

[1] https://kagi.com/search?q=site%3Agov.on.ca&r=ca&sh=lUDz_I8Uq...

[2] https://kagi.com/search?q=site%3ATDSB.on.ca&r=ca&sh=jysEnEgZ...

Some minor/trivial corrections:

- gTLD stands for "generic TLD"[1], not a short form of global, comes from their "generic" usage. Both two categories of TLDs are in the domain namespace which is globally resolvable.

- Almost all of two-letter ASCII ccTLDs reflect the ISO country codes, from ISO 3166-1 alpha-2, but there are a few exceptions: the United Kingdom (GB) has ".uk"[2], Ascension Island (now part of SH) has ".ac", etc. (Yes, there are more non-ASCII ccTLDs: .新加坡, .УКР, etc.)

If you want to briefly take a look at how TLD registries structure their second/third level such as "k12.or.us" or "chiyoda.tokyo.jp", see "ICANN DOMAINS" section of the public suffix list[3] (note: it is not complete)

[1] https://icannwiki.org/Generic_Top-level_Domain

[2] https://cddo.blog.gov.uk/2022/11/15/is-it-time-to-retire-the...

[3] https://publicsuffix.org/

Absolutely fascinating history. I thought I knew DNS fairly well and I had no idea that locality-based domains were even a thing.

Ah, what happened to the site design? It used to have a lovely background and monospace text.

> Technically speaking, the top of the DNS tree, the DNS root, is a null label referenced by a trailing dot. It's analogous to the '/' at the beginning of POSIX file paths. "gatech.edu" really should be written as "gatech.edu." to make it absolute rather than relative

I have never seen this, but I just tried it and it seems like browsers, even today will happily handle such URLs.

Neat!

  • If you work much with DNS, you will know about this. It is known as a FQDN, or a "fully qualified domain name", when the name ends with a .

    When you don't use a FQDN, your DNS system is going to try to figure out if you mean a FQDN or actually belong to a subdomain.

    On *nix, your /etc/resolv.conf file can have a "search" entries for search domains... that means that a lookup for "foo" will check "foo.bar.com" if "search bar.com" is in your /etc/resolv.conf

    This does mean your query could end up making multiple queries to determine if you meant foo. OR foo.bar.com

    You can configure how the machine makes the guesses with something called ndots... if you add "ndots 3" to your etc/resolv.conf, then your DNS queries will only try treating the domain as a FQDN if it has at least 3 dots... so for example, it would skip querying for foo as a TLD because it has no dots, and assume you mean "foo.bar.com", saving an unneeded DNS query.

    This usually doesn't matter to people, but it can have big performance implications for things like Kubernetes, with lots of .svc.local bits being left off of internal queries and relying on search domains; by increasing the ndots, you avoid a ton of wasted queries.

  • They need to, as when the "." is not present, your search domains are used, but they are not used when the trailing "." is present.

    For example, if you enter "ajdfajkhdfkajd.com", and your search domains contain one item called "mycompany.tld", then the browser will first query DNS servers for "ajdfajkhdfkajd.com.", and when an NXDOMAIN is returned, they will try "ajdfajkhdfkajd.com.mycompany.tld." next. If you type "ajdfajkhdfkajd.com." in the browser directly, only the first query is attempted.

  • Presumably they just split the “domain” part out of the URL on // and the first / and feed that into getaddrinfo, with the OS and DNS doing the rest?

    But I agree, it’s definitely neat :)

  • > Even today

    It's not like it's archaic. You still use the trailing dot when setting up DNS records to ensure they're unambiguous.

If you want to create a subdomain, you need DNS delegation (authorization) from the owner/manager of the domain.

So if you want to register xyz.ci.pemberton.nj.us, you need to ask for DNS delegation from the owner/manager of ci.pemberton.nj.us or a higher level.

It's a lot easier to buy the xyz-ci-pemberton-nj.us domain.

> ccTLDs reflect the ISO country codes of each country, and are intended for use by those countries, while gTLDs are arbitrary and reflect the fact that DNS was designed in the US. The ".gov" gTLD, for example, is for use by the US government, while the UK is stuck with ".gov.uk".

Fun fact, the UK's ISO country code is not actually "uk", but "gb". IIRC, ".uk" was grandfathered in (from JANET?) as an exception: ".gb" officially existed for a while in parallel, but no one ever used it and I think it's now defunct.

.su is available for registration, I'm not sure what the "in a limited way" is about. In Russia it's used to communicate old-schoolness, approximately.

  • Outside Russia it’s limited to renewals of existing domains due to sanctions. I believe ICANN is trying to eliminate the domain entirely due to it being obsolete, although I don’t know if a formal timeframe has been established for that yet.

  • It definitely is. In Germany, somebody was selling fraudulent public transit e-tickets on an .su domain for a while last year.

    Not sure who the “.su” was supposed to appeal to, but they were slightly cheaper than officially licensed ones, which probably helped more than the TLD :)

  • Outside Russia it's used to communicate spamming scumbaggery and is almost universally blackholed.

> "gatech.edu" really should be written as "gatech.edu."

https://www.gatech.edu./ does seem to work for me.

It is interesting that URLs often contain two hierarchies in opposite directions:

https://something.myorg.org/something/more/specific/

  • Yeah of course adding the extra dot will work. The dot at the end simply means do not try to append the local search domain. Interestingly bad “security” software will often block domains without the trailing dot but permit the one with the trailing dot.

    The problem of having two hierarchies in opposite directions means that it is advantageous to store it while reversing one of the hierarchies. I think the earliest Google Search backend used a format like org.myorg.something/something internally. This representation worked great for key-value storage systems where the keys are sorted.

I had one but the "Delegated Manager" was a local dsl isp that went out of business and I lost the ability to update the name servers for it

I didn’t realize how far these had fallen out of fashion. I maintained http://kenn.cr.k12.ia.us for a time, and it was so hard to remember that domain (scarcely easier than an IP address) until I tried to understand it. It’s now kennedy.crschools.us.

  • My high school is still at www-bths.stjohns.k12.fl.us, and if it wasn’t embedded in my fingertips from working IT there I’d have no idea how anyone is supposed to remember it.

  • I did sysadmin work for both a .k12.oh.us and a co.countyname.oh.us. Users at both hated the suffix on email addresses. The hierarchy appeals to the nerd in me but I understand the difficulty people had trying to communicate the addresses to others. (Both now use a .com and .gov domain, respectively...)

The notion that community colleges can't use .edu no longer seems true. When I took community college classes, I got an @my.smccd.edu email address.

  • The rules changed several times.

    My community college was occ.cccd.edu when I attended, where cccd.edu was the community college district, and they had registered their domain in 1993, but now the individual colleges have their own domain names, registered in 2002, 2004 and 2007. But there definitely was a time where only 4 year schools and museums were getting new .edus

Cloudflare refuses to accept most locality based domains as delegated because they aren’t listed in the Public Suffix List[1]. So for example you can’t use Cloudflare DNS or get a TLS cert for it from them.

Fortunately they seem to be one of the few (only?) providers who does that. So use another DNS provider and Letsencrypt and you’re good to go.

[1] https://en.wikipedia.org/wiki/Public_Suffix_List

My school didn't have a domain name or even an email address, or even an internet connection. I think it had 1 or 2 BBC Micros though. I remember playing a game where you had to fire a cannon (choose angle and power) and hit something. Funny how memory works - I assumed I'd remember nothing as so long ago, but remember sitting in the room playing that game now, can't remember why I could though (why I had free access).

Wow yes, I also remember my high school's k12 domain name! What an interesting trip down memory lane; wonderful, like most of computer.rip!

Is it possible to register e.g. X.ca.us domains today? What are the criteria required to do so?

  • > Is it possible to register e.g. X.ca.us domains today? What are the criteria required to do so?

    I don't think so. Godaddy won't delegate new third level domains, and I don't think the second level (states) were ever delegated?? But if you can find a city.ca.us that is delegated and that person/organization is willing to register a new name, you could maybe do that.

I grew up with *.pinellas.k12.fl.us and that domain remains seared into my memory.

It did always make me really annoyed they didn’t deprecate .gov, .edu and .mil and transition to moving those under .us (as .gov.us, .edu.us and .mil.us).

Having them as basically US-only just reeks of American exceptionalism which most of the world finds very distasteful.