Dropping support for the .ru top level domain

jim deleskie deleskie at gmail.com
Mon Mar 14 15:56:29 UTC 2022

Terrible idea on so many levels.


On Mon, Mar 14, 2022, 12:30 PM Patrick Bryant <patrick at pbryant.com> wrote:

> I don't like the idea of disrupting any Internet service. But the current
> situation is unprecedented.
> The Achilles Heel of general public use of Internet services has always
> been the functionality of DNS.
> Unlike Layer 3 disruptions, dropping or disrupting support for the .ru TLD
> can be accomplished without disrupting the Russian population's ability to
> access information and services in the West.
> The only countermeasure would be the distribution of Russian national DNS
> zones to a multiplicity of individual DNS resolvers within Russia. Russian
> operators are in fact implementing this countermeasure, but it is a slow
> and arduous process, and it will entail many of the operational
> difficulties that existed with distributing Host files, which DNS was
> implemented to overcome.
> The .ru TLD could be globally disrupted by dropping the .ru zone from the
> 13 DNS root servers. This would be the most effective action, but would
> require an authoritative consensus. One level down in DNS delegation are
> the 5 authoritative servers. I will leave it to the imagination of others
> to envision what action that could be taken there...
> ru      nameserver = a.dns.ripn.net
> ru      nameserver = b.dns.ripn.net
> ru      nameserver = d.dns.ripn.net
> ru      nameserver = e.dns.ripn.net
> ru      nameserver = f.dns.ripn.net
> The impact of any action would take time (days) to propagate.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20220314/ffd4fc07/attachment.html>

More information about the NANOG mailing list