Dns-operations mailing list

[opennic AT lewman.us]

On Wed, 16 May 2012 07:12:44 -0400
opennic AT lewman.us wrote:

> On Wed, May 16, 2012 at 12:39:33AM -0700, me AT travismccrea.com wrote
> 5.0K bytes in 118 lines about: : Before a server is removed from
> service, I feel the T2 operator should redirect all queries to a page
> telling them that their DNS server will be disabled soon and that
> they should use new servers… this way people don't just have their
> DNS queries just stop responding
> 
> Just curious, how does one redirect dns queries to a web page?

The answer is to do dns hijacking [0]. I think opennic should not
perpetuate this model. If the DNS server doesn't respond, the user will
figure it out.  Most of my dns queries are not through a browser but
through console-based applications. Lying to my local resolver isn't
nice and will break many applications.

I've been running a non-public T2 server for months now. At some
point, I'll make it public. If I need to change IP addresses (whether v4
or v6), it would be good to send the announcement to opennic-announce or
something more specific. I'm not going to install some dns hijacking
software to lie to users about where the server has gone. 

Users should also be encouraged to use multiple T2/T3 servers so if one
server moves, their queries seem slower, but aren't disabled. Users are
actively choosing to use opennic, therefore they have incentives to
keep up with changes for now.

[0] https://en.wikipedia.org/wiki/DNS_hijacking

-- 
Andrew
pgp 0x6B4D6475