Slashdot Mirror
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."
My other choice being.... dialup.
Comcast sucks, but it is the only choice for many of us. Competition doesn't work if there isn't any.
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?
No, Comcast is going to offer DNS servers that properly handle DNSSEC including passing along signed root answers. It is up to the client whether they wish to accept or reject unsigned domains (or in the case of anti-spam appliances probably give additional weight to non-signed domains).
There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
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.
DNSSEC security is an Internet standard and it means that we are enabling it for our domains and will validate others once it is rolled out globally. I suggest you read through http://www.dnssec.comcast.net/faq.htm which explains why we are rolling this out and what it means for our customers.
Thanks
Chris
Comcast
What this means is that COMCST is now going to tell their customers that your only allowed to visit websites that have joined the system. They may be selling this as security, but make no mistake this is also a huge control system. I may have to cancel my service with them, when this happens. The simply fact is you may have some legimate website who choose willfully NOT to partake in such a control scheme. I may need to visit such a site and COMCST is going to essentially tell me I can't visit that site. No thanks, I don't need a big brother. I'm an adult and I can take care of my own computers and I don't need COMCST protecting me. I don't give a crap what they say, I alone should have the right to decide where I can and can't go on the internet, unless of course you don't believe in freedom. Just give me the fully open internet service I pay for ya dern COMCST Commies!!! Quit interferring with my traffic.
-Anonymous Coward (yeah right like they can't track you down by your ip the way the RIAA is racketering everybody)
You have clearly not read anything about DNSSEC and how this actually ensures you get the traffic you requested without anyone - including Comcast - interfering with your DNS requests. I highly recommend you read http://www.dnssec.comcast.net/faq.htm so you can understand why we are doing this and why the global Internet and DNS is moving to this standard.
Thanks
Chris
Comcast
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
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
We will be disabling Domain Helper on our recursive resolvers and you will also get DNSSEC validation by using our Anycast resolvers. There is no redirection and you will also get the protections enabled by DNSSEC.
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.
Oh great. CCast sent shills already.
Actually I am one of the engineers that run the DNS at Comcast, but if you consider me a shill, so be it.
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...
If you're stuck with Comcast, there's an "alternative" that's often the best way to go: Comcast Business Internet service. It's run by a separate division of the company from the residential services, one that actually has competition and a decent customer service mindset. The business side also seems to completely avoid stupid stuff like Domain Helper in the first place. For those of you who still use TV or want other Comcast services, note that you can (and want to) mix-and-match Residential and Business services. For example, Residential for TV and Business for Internet -- the business rep who set up my account actually called this out and recommended it to avoid unnecessary restrictions on TV use applied to business accounts (e.g. no DVRs, etc.).
I don't understand all the hate for Comcast, at least here in Colorado Springs. In the past year and a half I've had service with them I've had less than a couple of hours of downtime (at least that was their fault and not me fiddling with my router). Good bandwidth & pings, who could as for more. It really blew me away after spending the past decade on military bases in the middle of nowhere overseas or downrange (1 second+ ping times, 10-30% packet loss, modem class bandwidth).
http://consumerist.com/2010/09/comcast-wont-give-me-tv-service-because-im-a-home-business-customer.html
"Comcast won't give me TV service because I'm a home business customer"
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.
Stop posting press release posts.
Here is some non-Comcastic information - http://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions
Chris what is your non-biased take on Comcast forging TCP reset packets and terrible quality HD?
Actually I have been working in the IETF to help provide better methods for P2P to work on ISP networks after the issues with the TCP reset packets a few years ago. I am sure you can look up some of the RFC items if you search for them.
If you have a problem with your HD quality, I suggest getting someone to come look at that. Given I am an Internet Engineer, I don't work on that side of the business.
Thanks
Chris
Comcast
Stop posting press release posts.
Here is some non-Comcastic information - http://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions
Chris what is your non-biased take on Comcast forging TCP reset packets and terrible quality HD?
I also should mention that reading Wikipedia isn't the most reliable source, although that one is fairly good. I might suggest looking at the following if you don't care for Comcast's write up:
https://www.dnssec-deployment.org/
or the RFCs:
http://tools.ietf.org/html/rfc4033
http://tools.ietf.org/html/rfc4034
http://tools.ietf.org/html/rfc4035
Thanks
Chris
Comcast
Which is false. Im posting AC because I work in "Business Services" at comcast..
I don't know about this specific case but I do run in to this with "home office" accounts alot.
My bet his he wanted Business class internet and "Residential TV" at "Residential TV" costs.
The difference between Res and Biz TV? Well here in Connecticut mainly the COST.
It doesn't matter if its a night club or a guy running a WebDev company our of his attic...its a commercial account.
Biz class tv costs ALOT more then normal TV.
Biz class tv has all sorts of crazy rules and extra fee's to the content providers.
We can not offer VOD/"Pay Per-View" because the content providers are worried you will order it at your BAR and show everyone there for free...or charge at the door.
We can not offer DVR service because the content providers don't want you skipping all the commercials in your packed restaurant.
We can not offer Adult Content (PlayBoy/Spice/etc) to places of business because of the agreements we have with the city. (think of the children!)
on and on..
My bet is the guy in that linked story did not want to pay all this extra money for "less" TV.
The work around is simple: You get 2 account numbers,2 drops, and 2 bills. One is the biz-class internet which your company pays for and the other is your home TV.
Makes doing the taxes simple and if your company is paying you to telecommute you just hand them the whole Biz internet bill.
From what I can tell comcast doesn't care all that much about pushing Biz Class TV(at least in this state) because its to much of a PITA with the regs/fee's and in the end we don't make all that much on it.Not being able to put "upsells" on it like DVR/VOD hurts. The only thing its really good for is keeping ATT/DISH/etc OUT of your company and getting us in the door with the internet/phone.
I opted out of Domain Helper by using manually configured DNS servers, OpenDNS at the moment. It seems if you manually migrate to their DNSSEC servers, Domain Helper goes away, as according to the FAQs the two are incompatible.
-={(Astynax)}=-
"Darkness beyond Twilight"
Opting out of domain helper is as simple as changing your DNS servers in your router. Mine point to a OpenDNS (paid), and allow me to block a lot of advertising popups and under-lines.
Google also supplies free DNS servers (8.8.8.8 ).
To do this, I just bridged my router (The comcast business service box), they even told me how to do this. Then I use my own linux box to handle routing. But you can also set up your own dns sources using their box if you want.
The Business services bunch are a whole lot easier to deal with than the home services people.
Sig Battery depleted. Reverting to safe mode.
when did Slashdot get populated with a bunch of morons who can't change a freaking router DNS setting?
The US should be breaking-up these monopolies, the same way it broke-up the AT&T monopoly.
The US should just nationalize the last mile, treat it as a utility, and avoid all that icky anti-trust litigation.
While I wait for that to happen I'm going to hold my breath until Steve McQueen rides a rainbow-winged pegasus out of my ass.
The reality will probably involve the encroachment of the insurance industry into the ISP realm. You'll need a co-pay to call customer service, and you can only use an ISP from the approved list.
I can't tell whether or not I'm joking.
"All these years believing you're the signified monkey, only to find out you're just a big hunk of nobody cares."
Dude, I don't even live in the same country, and I'd have modded you down for turning a corporate matter into a personal attack. Comcast is big, and chances are this fellow had no choice but to carry out his orders. If he doesn't do as he is told, a more compliant replacement will be found.
If you hate the company so much, don't take it out on the worker bees, just take your money and go elsewhere. Don't like the alternatives ? Well tough tits, either start your own ISP or STFU. Bitching at a sysadmin will not get you anywhere, at best you will browbeat someone who doesn't deserve your ire, at worst he will mess with your service like any self-respecting BOFH should.
-Billco, Fnarg.com
"Stuck with Comcast"??? From my perspective as a network engineer, Comcast is taking the lead in deploying IPv6, and now DNSSec. They are putting the rest of the corporate world to shame on these fronts. (And I am neither an employee, nor a customer of Comcast.)
In computer security circles Comcast is being congratulated for making this step and I certainly add my congratulations.
Oh, this will also be the end the odious Comcast DNS redirection scheme as DNSSEC will make it impossible once the top level domains (com, net, org, edu, gov etc) are signed. Comcast cannot become involved in any domain other than those they own. (E.g. comcast.com, comcast.net)
Kevin Oberman, Network Engineer, Retired