On Tue, Mar 10, 2015 at 07:36:57PM +0000, Dan York wrote: > > As far as I know, DynaDot *is* unrelated to Dyn… but I didn’t identify the > registrar because I didn’t really think they were as relevant to the > analysis. Dyn’s name is visible via the NS records (and yes, DynaDot comes > up through WHOIS) and they have the role in the signing process. >
It's worth observing that, if a customer went to Dyn and added a zone without setting it up to be signed, Dyn wouldn't have anything to do with the signing process. I'm not in a position to comment on this particular case, of course, because it has to do with customer data; it is possible that Dyn will be able to comment further on the record. (For those who don't know, Dyn is my employer.) > To the uninitiated, this might give the impression that Comcast actively or > intentionally did something to block HBO. > > I get your point… but I’m also trying to keep the post understandable in > simple terms. And to the users out on Comcasts network, from *their* > perspective, Comcast *was* blocking HBO’s site. > In my view, Comcast was validating the DNS data and doing the right thing. I don't think it's fair to call this "blocking". Best regards, A -- Andrew Sullivan [email protected]
