Re: Dropping support for the .ru top level domain

["J. Hellenthal via NANOG" <nanog () nanog org>]

Thank you for you're support.?.


-- 

J. Hellenthal

The fact that there's a highway to Hell but only a stairway to Heaven says a lot about anticipated traffic volume.






> On Mar 12, 2022, at 04:47, Patrick Bryant <patrick () 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.