Comcast Migrating Customers To DNSSEC Resolvers
ctg1701 passes along this quote from a Comcast announcement:
"Starting today we will begin migrating customers who have opted out of our Domain Helper service over to our production DNSSEC-validating servers. This will happen first in a selected part of our Virginia network, and will later expand to all markets in the following sixty days, at which point all of our customers who have opted out of Domain Helper will be migrated. After this has been completed, we will migrate the rest of our customers, which we anticipate will stretch into the early part of 2011."
You really should be migrating off of Comcast
-- if you mod me down, I will become more powerful than you can possibly imagine
For those of us on Comcast, what does this mean?
Whenever I am offered the opportunity to opt out of something by a company, I know it's probably a good idea to opt out.
Also, I've had very flaky internet service the past week or so, although I am not in this market (Minneapolis area). My equipment all seems to work fine, and of course there could be any number of causes, but this seems interesting.
Domain helper.. is that the crap that automatically relocates you to some ad serving search website when you input an unrecognized dns in the web browser? That kind of crap is why I switched to 4.1.1.1
My router is already set up to ignore Comcast's DHCP provided DNS, and use 8.8.8.8 and 8.8.4.4 anyway... Substitute your own favorite public DNS resolver (or install OpenWRT and use its djbdns if you prefer).
Had no idea what it was either until I read this. http://blogs.techrepublic.com.com/networking/?p=234
How does it feel to be a liar with pants constantly on fire?
what happens if the site doesn't want to sign up for dnssec? would comcast block communications with those sites? also it seems dnssec cost additional to the current cost for a site. (just putting that out there)
What does this mean for webmasters? Are all of us going to need DNSSEC keys on our websites or does this just apply to comcast's array of websites? I wasn't aware that DNS had any kind of security issue which would warrant a revamp. How will this affect the future of the web?
OpensDNS has the same flaws as Comcast's Domain Helper service (ie does not return NXDOMAIN), GoogleDNS has some issues I can't remember and for us has pretty significant latency.
There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
OpensDNS has the same flaws as Comcast's Domain Helper service (ie does not return NXDOMAIN), GoogleDNS has some issues I can't remember and for us has pretty significant latency.
Currently neither support DNSSEC validation and with us enabling DNSSEC on our recursive resolvers, we are disabling Domain Helper. Please check out http://www.dnssec.comcast.net/faq.htm for more details.
Thanks
Chris
Comcast
I've been using these months while they've been available for testing. The very nature of DNSSEC kills the 404 helper service, and provides an extra level of security. For anyone that wants to use them now without being migrated automatically someday, just use 75.75.75.75 and 75.75.76.76 for the DNS.
GoogleDNS with local cache works pretty well for me.
Dilbert RSS feed
Am I tired already? I read that title as "Revolvers", and I wondered what the hell Comcast was doing selling handguns to people. For about thirty seconds. Then I wondered what the hell a "DNSSEC" revolver was for another thirty seconds. Then I smacked myself, re-read the thread title, and decided to make this utterly pointless post.
Sleep deprivation is a wonderful thing...
Google is kind of creepy; they are like cyber stalkers. They want to read all our emails, see what we are searching for, log all our visited domains, know what places we are planning on visiting, track which YouTube videos we watch, transcribe our Google voice calls, and probably much more, so they can send us better targeted ads. Important: The previous statement was a collection of random and fictional thoughts from the author's imaginative head and is not deserving of a suit for libel.
my opportunity to freely express myself with the potential persecution and hangings and such
Point by point:
Is DNSSEC a good thing? (Yes)
Do webmasters need a DNSSEC cert? (No, but it wouldn't be a bad idea. DNS works normally if you do not have one).
Will consumers get 404 redirect pages with DNSSEC? (Not sure here. I'm guessing -- No, because DNSSEC doesn't allow this?)
Will Comcast ever stop sucking? (Probably not.)
GoogleDNS doesn't share info with other Google systems.
Dilbert RSS feed
Your experience with Comcast is very likely related to where you are located. I live in a NW suburb of Chicago. Literally the very worst service I have ever received from any company was from Comcast. Outages that lasted for 2 to 3 weeks at a time. Outages several times a year. Technicians that I stayed home for waiting for them to arrive and they never came. Technicians who eventually came to the house and said "I don't know what's wrong" and left, and closed the ticket. (This happened more than once.) Bandwidth that made dialup look like a miracle it was so bad. Two different routers that literaly over heated and melted. (and yes they were in a ventilated area.) Replacement equipment that was used and dirty and didn't work. Comcast screwed with packets that belong to Skype to make sure the quality was terrible. (Oh but their VOIP brand was just fine.) The list goes on and on. It was so bad that I finally dumped my cable TV completely and switched over to AT&T business DSL. Mind you AT&T is not my favorite company either but the service is rarely if ever down and if I have a problem they fix it. DSL at 6 Mbps is better than Comcast 22 Mbps that delivers 150Kbps and is down more than up. So for those of you who have "never been happier with the amazing orgasmic experice that is Comcast" ... good for you. I certainly won't be doing business with them again anytime soon.
Chris what is your non-biased take on Comcast forging TCP reset packets and terrible quality HD?
Because guys that run DNS servers are obviously the guys who are responsible for video quality-of-service. Same field, and Comcast has only a couple of engineers running their entire network. I bet Chris also is responsible for designing their logos and what's in their cafeterias and whether the cable installers show up on time.
The topic is DNSSEC, not bandwidth caps or video compression or network traffic filtering.
I would have thought that having a primary source, an engineer relevant to the discussion, was welcome. Instead, it's an excuse to get out the haters. IT guys complain about how they're the ones that take the heat for corporate decisions which they don't control, but the moment it's someone else's IT guy, that person gets the heat for corporate decisions which they don't control. Nice consistency there. What's YOUR company, so we know who YOU are a "shill" for?
I'd be surprised if we hear from Chris again. I know I wouldn't come back. Screw Slashdotters, they don't want information or answers, they want scapegoats and straw men.
Whether Comcast, EFF or the Nazis use DNSSEC is irrelevant to the merits and flaws of DNSSEC. Whether Comcast uses DNSSEC is irrelevant to whether they use ad-readirectors for NXDOMAIN results.
By the way, I think I worked on the DNS server and service that Comcast is using for this, at my previous job. I guess that makes me a shill too. But I'll be damned if I'm going to share anything useful about it, even things that aren't under NDA, to Slashdot.
Everybody gets what the majority deserves.
I'm a Comcast subscriber and have had problems with DNS resolution. Just changed to the new DNS servers and magically it is about twenty times faster.
I switched from Comcast to Cricket because the Comcast service was so unreliable. In the end, they could not even get a TV signal through reliably. But that is another story. What I notice though is that even when Comcast was working up to advertised speed, the name server delays were really bad. So, even with lower bandwidth, Cricket seems faster because their name servers work. Hope this move by Comcast makes an improvement.
OpenDNS only does the "domain helper" thing for non-registered users.
Register for an account, specify the IP address (or range) that you'll be making queries from (e.g. your home router), and you can disable all of that. I've been doing that for years with no problems. Way better than Cox's DNS service, which rewrites all TTLs to 30s.
If your home router supports dynamic DNS updating, you can have the router update OpenDNS (I use their DNS-O-Matic service, which also updates DynDNS and EveryDNS) whenever your system gets a new IP address so the settings stick with you, even if the IP address changes.
Actually I am one of the engineers that run the DNS at Comcast, but if you consider me a shill, so be it." - by ctg1701 (311736) on Monday October 18, @06:07PM (#33939512)
Well, at least YOU admitted that you work for COMCAST Chris... HOWEVER:
You also didn't admit what I strongly suspect is true though (myself having worked for CableVision, a like member of your industry in telecommunications)... what is that? Well, ok!
That You are one of your staff, one of a VERY SELECT FEW in fact, who is ALLOWED to speak here on this issue, & others in your firm, specifically lower level techs is my guess, were also STRICTLY WARNED to steer clear of commenting on this publicly online, especially on largely travelled forums like this, or say, DSLReports.com & others like them, or highly trafficked sites like this one is...
Am I right?
Since you're thusfar showing a track-record of 'truth' here at this point?? I trust you will give us a straight answer on this much I just asked above... hopefully!
See, Chris, around here? You have to realize 1 thing: We're pretty aware of "how the show runs" for folks out of any large corporate entity... & that you people can & DO patrol largely travelled sites like this, especially when new news comes out that involves you & yours (COMCAST in this case).
Hell, even "industry notables" who have had enough of that type of crap have sounded-off on it here... & on the very account I am noting (paid trolls/shills etc.- et al) & here is an example thereof:
"It just takes one Ubuntu sympathizer or PR flack to minus-moderate any comment. Unfortunately, once PR agencies and so on started paying people to moderate online communities, and to have hundreds of accounts each, things changed." - by Bruce Perens (3872) on Friday July 30, @04:55PM (#33089192) Homepage Journal
http://linux.slashdot.org/comments.pl?sid=1738364&cid=33089192
APK
P.S.=> Still, do I think you're doing this just to "cover comcast's behind"? No, I think you really MEAN what you're saying about COMCAST now going over to DNSSEC (probably a GOOD THING for you folks & your clientele hopefully)... but, my point is that I know PER MY SUBJECT-LINE NO LESS, just as Mr. Perens quoted above knows from his time @ HP, that only SOME FOLKS from large corporates are "allowed to talk" on various issues online publicly, and I have heard that "go down" myself in fact (but, not a paid shill/troll here, ever) - I am still willing to wager that you are 1 of your companies "Chosen Few" that were allowed to speak on this at all, period... am I right Chris? I wager I am... strongly (but, could be wrong, but... well, we'll see)... apk
After reading their FAQ, looks like Comcast is doing the right thing and also admitting the DNS Redirector/Helper wasn't the right solution.
Are customers who have opted in to or out of Comcast Domain Helper impacted by this?
* When DNSSEC is deployed on all of our DNS servers, the web error redirect function at the core of Comcast Domain Helper will be disabled, as this is not technically compatible with DNSSEC.
* Customers that have opted out of Domain Helper will be the first customers that we migrate to the new DNSSEC servers. Domain Helper will not be active.
* Comcast does plan to turn off Domain Helper when DNSSEC is fully implemented.
What happens to Comcast Domain Helper, which offers DNS redirect services, when you fully implement DNSSEC?
* We believe that the web error redirection function of Comcast Domain Helper is technically incompatible with DNSSEC.
* Comcast has always known this and plans to turn off such redirection when DNSSEC is fully implemented.
* The production network DNSSEC servers do not have Comcast Domain Helper's DNS redirect functionality enabled.
* We recently updated our IETF Internet Draft on this subject, available at http://tools.ietf.org/html/draft-livingood-dns-redirect, to reflect this.
Good to hear, always glad to hear that the Internet is getting a little less broken. Btw do these recursive resolvers support IPv6 yet?
There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
That's what they say, anyway. There's no way to know for sure, though. Their moto is something like "Don't be evil." It makes me wonder if being evil is something they struggle with.
my opportunity to freely express myself with the potential persecution and hangings and such
I'm in a Chicago suburb and got this today:
This is a courtesy email to let you know that Comcast's DNS servers are changing to servers that use DNS Security Extensions (DNSSEC), as part of an evolving suite of security protections that are part of Comcast Constant Guard. These changes, which have started today in some markets, will be completed within the next sixty days or so. You do not need to take any action and you should not notice any changes to your service, though behind-the-scenes your service will be more secure.
Watch a short video about this change at http://www.dnssec.comcast.net/dnssec-video.htm.
Additional Details:
We know you have previously opted out of Comcast Domain Helper, which redirects you if you mistype a website address to a Comcast search page. Your opt-out preference will of course continue to be honored as you migrate to the new DNSSEC servers.
With DNSSEC, a web site name such as www.comcast.net can be signed with a secure key in the Domain Name System. Then, when you try to connect to that website, the Comcast DNS server checks that domain name, and it verifies the special key to ensure that it is valid and has not been tampered with by hackers or other criminals. You will only be connected if this security verification has been passed, which occurs so quickly you won't even notice that it's being done.
We're pleased to enhance Comcast Constant Guard with the addition of DNS Security Extensions (DNSSEC), delivering you a more secure Internet experience. As the first major Internet Service Provider (ISP) to move to DNSSEC in the United States, you should know that you are among the first to be getting these new security capabilities and that we continue to push for a more secure Internet experience for you, as well as a more secure global Internet.
You can learn more by:
- Watching this short video: http://www.dnssec.comcast.net/dnssec-video.htm
- Learning about Comcast Constant Guard: http://security.comcast.net/constantguard/
- Diving deeper at our DNSSEC Information Center: http://www.dnssec.comcast.net/
Warm Regards,
Jason Livingood
Internet Systems Engineering
Comcast
This is a service-related email. Comcast will occasionally send you service-related emails to inform you of service upgrades or new benefits to your Comcast High-Speed Internet service.
Copyright 2009. Comcast. All other trademarks are properties of their respective owners.
Comcast respects your privacy. For a complete description of our privacy policy, click this link.
Comcast
One Comcast Center, 10th Floor
1701 JFK Boulevard
Philadelphia, PA 19103-2838
Attn: CHSI
The preferred solution is to not have a problem.
http://dns-opt-out.comcast.net/help-index.php
So your choice is a Comcraptic DNSSEC testbed, or targeted ads?
While I am forced (alternatives are 5 times slower or 10x as expensive for the same speed) to connect through Comcast, I run my own DNS server -- I wonder how long that will be allowed.
Comcast is so messed up, though the US broadband as a whole is messed up and getting worse...wonder time to live in the US, in it's twilight years...
I am really not a fan of government regulations. But some things work, and some things are appropriate for a government to do. This qualifies as both.
Their other privacy policies are very clear about all the data they record. Why would they lie in this particular case? It's not like people wouldn't use it, when everyone and their mother uses the search engine despite clearly stating they record everything.
Obviously I can never be sure, but the Occam's razor applies here, in my opinion.
It's not official, it's only an item in their corporate philosophy statement, and it's well explained: http://www.google.com/corporate/tenthings.html
Besides, lot's of companies have ethical codes.
Dilbert RSS feed
It really depends on the client you are running and what type of answers it expects.
If the client is expecting answers with DNSSEC records (by setting DO in the query) then any modification of a answer like changing NXDOMAIN to a 1.2.3.4 can be detected if the client has a trust anchor that covers that zone (directly or indirectly though a parent zone).
If the client is not expecting answers with DNSSEC records then the recursive server can still ask for the DNSSEC records and validate the answers it receives but send on modified answers to the clients.
That being said it would just be a bad PR exercise to validate then do NXDOMAIN redirection.
This is also not to say that Comcast won't do some re-writting of responses in the future. If they decide to deploy NAT64 then they will need to also deploy DNS64 which work by re-writting answer to AAAA queries if there are no AAAA records but there are A records. How to do DNS64 with validating DNSSEC clients is still being worked out but will almost certainly require the client to do the DNS64 synthesis itself.
i almost cried when i moved to an area with FiOS. I'm getting 35/35 Mb for only $15 more than what I used to pay Time Warner cable for 15/1 Mb...
Would you mind commenting on why, over 9 years at several different Comcast-served residences, using DHCP in my routers to get and forward DNS server numbers to my systems has resulted in extremely slow lookups? I'm talking easily 5+ seconds per lookup with some complex web pages taking more than a minute to load.
I never had this problem with Verizon or Charter. The only solution for getting decent DNS performance on Comcast has been to use non-Comcast servers.