Technology

37747 readers

199 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

alyaza@beehaw.org

TheRtRevKaiser@beehaw.org

gyrfalcon@beehaw.org

rs5th@beehaw.org

coldredlight@beehaw.org

Los@beehaw.org

SemioticStandard@beehaw.org

TheRtRevKaiser@kbin.social

remington@beehaw.org

126

The British government is transferring sovereignty of an island in the Indian Ocean to Mauritius next week, potentially impacting the existence of the .io domain. (every.to)

submitted 1 month ago by PhilipTheBucket@ponder.cat to c/technology@beehaw.org

34 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] bamboo@lemmy.blahaj.zone 71 points 1 month ago (1 children)

the warning for future tech founders is clear: Be careful when picking your top-level domain. Physical history is never as separate from our digital future as we like to think.

Kinda ironic this is published to a website with a .to ccTLD for the Kingdom of Tonga.

[–] lostinfog@reddthat.com 9 points 1 month ago (1 children)

My former company had a .bb domain for internal services because it rhymed with the name. We had constant outages whenever a storm was hitting Barbados…

[–] bamboo@lemmy.blahaj.zone 3 points 1 month ago (1 children)

Interesting, that's not something I ever thought about. I just looked up the nameservers for .bb:

;; ANSWER SECTION:
bb.			86400	IN	NS	ns5.nic.bb.
bb.			86400	IN	NS	ns3.nic.bb.
bb.			86400	IN	NS	ns2.nic.bb.
bb.			86400	IN	NS	ns1.nic.bb.
bb.			86400	IN	NS	ns4.nic.bb.
bb.			86400	IN	NS	ns6.nic.bb.

It seems like ns1.nic.bb doesn't resolve, and for 2-6, they're all in either 64.68.192.0/20 or 64.119.192.0/20, so it does look like a small concentration in root nameservers which could be unavailable in a storm.

[–] lostinfog@reddthat.com 4 points 1 month ago

Some times someone’s clever joke can have unforeseen consequences. There must be a razor for that. Or at least a xkcd comic.