Upcoming DNS changes

[Andrew Drake]

Please add a notice to the dns-blocked page (preferably with a link to this post) that the block was enforced by Sonic.net. At least one of your blacklists has a pretty high false-positive rate and I spent a good hour trying to figure out what was blocking random sites so I could disable it.

[jon]

Looks like the shell server, bolt.sonic.net, is not using DNSSEC (per
http://test.dnssec-or-not.org/. Is that intentional?

[kgc]

No, not really, it looks like it got swung over to our systems-internal resolvers which are not currently running DNSSEC. I've moved it back to use 208.201.224.11 and 208.201.224.33

[cdkeen]

I spent a good hour trying to figure out what was blocking random sites so I could disable it.

Try either of these multi-bl lookup sites to find what is blocking a particular domain:
http://multirbl.valli.org/lookup/
http://www.urlvoid.com/

This can reduce the time spent identifying the blocking party.

[jon]

No, not really, it looks like [the shell server] got swung over to our systems-internal resolvers which are not currently running DNSSEC. I've moved it back to use 208.201.224.11 and 208.201.224.33

Great -- thank you!

[Customer222]

I like the service, however, it took me over a week to figure out that it was Sonic.net that was blocking sites.

Can you put at the very least a link or change the page to show Sonic.net on it? The site is so generic it has no ownership information. Even checking the source code didn't point to the fact that it was Sonic.net doing the filtering.

[kgc]

The problem is that page is shared with wholesale ends users and there is no way to distinguish between reseller and wholesale end users in real time in order to brand the page. We're aware that this isn't an idea situation and may be able to change this in the future after some parts of the fusion service are reworked internally.