| My county government started w/ a "co.Name.oh.us" domain name back in the late 90s. People in the government hated it. The complaint I heard most frequently was that the public couldn't get it right-- too many dots. I was a fan of the ".co.name.oh.us" naming because it made logical sense. I could easily find any County website in the state. My intuition now is that anything logical (or, perhaps, just anything I like) will be hated by the public. >sigh< The county moved to "NameCountyOhio.gov". It's 5 characters longer than the old domain name but isn't hated. The public still gets it wrong often, expecting it to be "NameCountyOH.gov". Edit: Okay, so I got this totally wrong. Chalk it up to poor memory for stuff 20+ years ago. There's RFC 1480, first of all: https://datatracker.ietf.org/doc/html/rfc1480 The old County domain was "co.name.oh.us". I completely forgot the hierarchy was flipped for localities, with the locality being the higher level domain and the designation for type of locality (city, county, etc) being second. For K-12 school districts, libraries, colleges, and others, the hierarchy comes first (like "name.lib.oh.us"). |
Would be better to just get rid of the “co” layer.