Re: New DNS vulnerability: political overreach

[Amir Herzberg via NANOG <nanog () lists nanog org>]

Allan, I agree with Andy: this isn’t a technical concern. Frankly I feel
like your title was a bait, causing people like me working on real dns
security to read your post , although I believe unintentionally. It isn’t a
technical issue since nobody said all companies must use the com tld. If
there’s sufficient demand surely someone will set up an alternative tld out
of the US jurisdiction . So… problem solved? No need in new technology?

And sorry if I’m grumpy today, it has been one of these days…. Amir


-- 
Amir Herzberg

Comcast professor of Security Innovations, Computer Science and
Engineering, University of Connecticut
Homepage: https://sites.google.com/site/amirherzberg/home
`Applied Introduction to Cryptography and Cybersecurity' textbook:
https://www.worldscientific.com/pb-assets/wspc-site/catalogue-pdf/ComputerScience-annual-catalogue-1754962278227.pdf
<https://sites.google.com/site/amirherzberg/crypto-cyber-book>


On Sun, Jul 19, 2026 at 9:37 AM Allan Liska via NANOG <nanog () lists nanog org>
wrote:

> Considering that this is the second time in less than a week that a
> company has had their domain taken off line at the Registrar level (
> https://techcrunch.com/2026/07/14/telegrams-shortlink-domain-is-back-online-after-day-long-suspension/)
> I do think there is a legitmate technical concern here, though I'd argue it
> is far from new.
>
> It is a scenario that most companies don't account for, but depending on
> the type of business you are in, it is a very real concern and you should
> have a response plan in place.
>
>
> allan
> On Sunday, July 19th, 2026 at 9:08 AM, Andy Ringsmuth via NANOG <
> nanog () lists nanog org> wrote:
>
> > Can we keep politics and personal opinions separate and independent of
> the technical aspects of the issue at hand (if there are any)? Per the
> NANOG list info page:
> > "Appropriate topics include: routing; broad-based engineering
> problems/issues/solutions; outages; performance measurement; evolving
> wide-area technologies; exchange points; traffic engineering; operational
> experience; ISP security; and trouble ticket systems."
> > Is there an actual legit technical issue here that needs discussion or
> solving?
> > ----
> > Andy Ringsmuth
> > andy () andyring com
> >
> > Love others, encourage others, help others.
> >
> > > On Jul 19, 2026, at 6:05 AM, Kevin Tillery via NANOG <
> nanog () lists nanog org> wrote:
> > > A Texas court has suspended the .com domain of a Dutch porn site which
> doesn't have any business presence in Texas, because it doesn't comply with
> Texas rules about porn (which are extremely onerous):
> > >
> https://www.texasattorneygeneral.gov/news/releases/attorney-general-ken-paxton-secures-landmark-legal-victory-lock-pornographic-website-domain-and
> > > Clearly the US is not fit to manage top-level domains (other than .us
> of course) even though it ended up with them by historical accident. It
> worked for a while but now it's not working any more. Has anyone come up
> with any plan to solve this and make the DNS more neutral?
> > > As a first step I'd think about experimenting with a DNS resolver that
> would move all US TLDs to subdomains of .us. However that obviously would
> just break the current internet for whoever is using this resolver, at
> least due to widespread use of vhosts.
> > > Kevin
> > > _______________________________________________
> > > NANOG mailing list
> https://lists.nanog.org/archives/list/nanog () lists nanog org/message/55UTA3Q4NIN5455KV7TAY7YTMC7ZUENI/
> > >
> >
> > _______________________________________________
> > NANOG mailing list
> https://lists.nanog.org/archives/list/nanog () lists nanog org/message/EJC2UZCJFBHZKWIRLRP35AOT6R6C63BW/
> _______________________________________________
> NANOG mailing list
>
> https://lists.nanog.org/archives/list/nanog () lists nanog org/message/FARPULLLVBYECCOSDWV65FMNYDHO37MA/
_______________________________________________
NANOG mailing list 
https://lists.nanog.org/archives/list/nanog () lists nanog org/message/DOIBQD4NI7EFS5WCDL6UOXDIAZFWFFP3/