Home / Blogs

Protecting Intellectual Property is Good; Mandatory DNS Filtering is Bad

Protect your privacy:  Get NordVPN  [73% off 2-year plans, 3 extra months]

It has been about six months since I got together with four of my friends from the DNS world and we co-authored a white paper which explains the technical problems with mandated DNS filtering. The legislation we were responding to was S. 968, also called the PROTECT-IP act, which was introduced this year in the U. S. Senate. By all accounts we can expect a similar U. S. House of Representatives bill soon, so we’ve written a letter to both the House and Senate, renewing and updating our concerns.

Please note that my co-authors and I are all strong advocates for individual property rights and for that matter we’re all copyright owners ourselves. We don’t think that “content wants to be free”. The parts of the proposed legislation that target online advertising and payment networks are solid work and will have a positive impact. But the part describing how ISP’s would filter their DNS results according to lists of bad domains maintained by the U. S. Gov’t is a bad idea—it won’t have much of an effect on counterfeiting or infringement online but it would surely create a lot of new problems—especially with DNSSEC.

I am especially concerned about the growing number of off-shore DNS services promising free, clean, unfiltered results. The letter below references three such services and our white paper from May 2011 predicted this exact outcome. I think it’s now obvious to everybody that there will be dozens or hundreds of “pirate-friendly DNS” services if S. 968 or anything like it becomes law. This would multiply the online perils faced by Internet end users in the United States, as well as mooting the new law.

Let’s stop online infringement and counterfeiting, but let’s do it sensibly—in a way that works and which won’t create new and worse problems.

Internet Engineers’ Letter in Opposition To DNS Filtering Legislation PDF, October 12, 2011

Update: ISC is hosting a webinar on this topic on October 26. Domestic ISP’s and ASP’s should plan to attend. Any interested party is of course welcome.

By Paul Vixie, VP and Distinguished Engineer, AWS Security

Dr. Paul Vixie is the CEO of Farsight Security. He previously served as President, Chairman and Founder of Internet Systems Consortium (ISC), as President of MAPS, PAIX and MIBH, as CTO of Abovenet/MFN, and on the board of several for-profit and non-profit companies. He served on the ARIN Board of Trustees from 2005 to 2013, and as Chairman in 2008 and 2009. Vixie is a founding member of ICANN Root Server System Advisory Committee (RSSAC) and ICANN Security and Stability Advisory Committee (SSAC).

Visit Page

Filed Under

Comments

A hearty "+1" Jothan Frakes  –  Oct 14, 2011 9:32 AM

This legislation in and around clamping via DNS at the ISP level is obtuse to how the system works when combined with the human spirit. 

This article about blockaid.me, a new workaround for any government seized domains, illustrates how thin the premise of any real value the legislation might deliver.

It is unlikely to be much other than a minor nuisance to the true ‘perps’ that the legislature will create.

My concern has always been that a workaround might come in the form of rogue recursive DNS servers being provided to people as a means to mitigate the clampdown their ISP may have made.

Users are still able to override their DNS settings per computer or even per router at the home or enterprise.  Often this might be teens editing their parents machine or one at school.

Once someone can answer DNS authoritatively for every lookup, they can fairly well change ANY site, intercept email or other traffic, disrupt antivirus autoupdates and other bad things.

This is another of the many scenarios that illustrate how the ‘cure’ can create more problems than the disease.

Comment Title:

  Notify me of follow-up comments

We encourage you to post comments and engage in discussions that advance this post through relevant opinion, anecdotes, links and data. If you see a comment that you believe is irrelevant or inappropriate, you can report it using the link at the end of each comment. Views expressed in the comments do not represent those of CircleID. For more information on our comment policy, see Codes of Conduct.

CircleID Newsletter The Weekly Wrap

More and more professionals are choosing to publish critical posts on CircleID from all corners of the Internet industry. If you find it hard to keep up daily, consider subscribing to our weekly digest. We will provide you a convenient summary report once a week sent directly to your inbox. It's a quick and easy read.

Related

Topics

DNS

Sponsored byDNIB.com

Threat Intelligence

Sponsored byWhoisXML API

Domain Names

Sponsored byVerisign

IPv4 Markets

Sponsored byIPv4.Global

Cybersecurity

Sponsored byVerisign

Brand Protection

Sponsored byCSC

New TLDs

Sponsored byRadix