Recent Microsoft outages disrupted email and essential services around the world. Technical failures and cyberattacks remind us how dependent we are on digital infrastructure.
We back up photographs, documents, even electricity. Why not the system that helps us find our way online?
Governments encourage households to prepare for emergencies, sometimes for 72 hours without essential services. Consider what happens if internet naming is disrupted.
DNS turns names into addresses. Without that translation, connections may still function, but finding online services becomes difficult.
Today's DNS has extensive redundancy, but its globally coordinated naming root is shared. More copies of the same root are not an independent naming alternative.
Handshake offers another approach: an independent, blockchain based naming root.
Importantly, Handshake is designed to be compatible with existing DNS, allowing familiar extensions such as .com and .org to continue resolving while offering a separate root for Handshake names through compatible resolvers.
We don't have to rebuild the internet to explore another way of naming it.
Handshake is not yet a universal drop in substitute, it won't automatically restore services during a Microsoft outage. Wider resolver support, infrastructure, adoption and testing would be needed.
If governments prepare for emergencies, they should also investigate independent naming systems
We're not suggesting abandoning DNS. We're suggesting that relying on only one globally coordinated root deserves a second look.
Every essential system needs a backup. Including DNS.
Own The Name | Own The Rules | Own The Dot.