User: Password:
|
|
Subscribe / Log in / New account

Increasing the TCP initial congestion window

Increasing the TCP initial congestion window

Posted Feb 10, 2011 18:29 UTC (Thu) by mtaht (guest, #11087)
In reply to: Increasing the TCP initial congestion window by cortana
Parent article: Increasing the TCP initial congestion window

As if breaking NXDOMAIN everywhere wasn't enough?

One DNS provider (name.com), in addition to returning ptrs to ad sites on missing domain names, is ALSO returning completely invalid pointers to IPv6 addresses for the same:

d@cruithne:~$ host no.such.subdomain.bufferbloat.net
no.such.subdomain.bufferbloat.net has address 149.20.54.81
no.such.subdomain.bufferbloat.net has IPv6 address 1400:0:bce5:95ab:1e00:0:2800:0

I've been meaning to discuss this with them once I can summon the needed diplomacy and tact. So far, no luck.

Be careful what you wish for.


(Log in to post comments)

Increasing the TCP initial congestion window

Posted Feb 10, 2011 22:14 UTC (Thu) by cortana (subscriber, #24596) [Link]

Of course, my suggestion was made in jest. However... given that ISPs are already breaking DNS by replacing NXDOMAIN responses with forged records... would we not all be better off if they were allowed to do so by the protocol? As long as there was a flag in each RR indicating that it is an advertising result, users of web browsers could opt in/out of receiving them, and other programs could ignore them altogether. At least we'd be in a better situation to that which we are in now. Of course, DNSSEC presumably fixes all of this, but not in favour of those who are incentivized to present the forged advertising responses.


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds