www.heroesonline.com unresolvable via local unbound instance?

Todd Blake tbblake at gmail.com
Fri May 3 11:44:05 UTC 2019

My ISP is Spectrum (Charter) in the US, from what I can tell, they don't
seem to block much of anything, if anything, at all.

The "fairly common" comment was just a guess on my part as I've never had
to troubleshoot DNS like this.  I see no logical reason why I shouldn't be
able to contact their DNS servers.  I was just at a loss as to what the
issue might be.

Though I also noticed, that if I set my DNS to on my desktop PC,
and can thusly resolve the domain, I still can't reach the website. This
smells less like intentional blocking, and more like maybe routing, or some
other misconfiguration at the host for the domain.

On Fri, May 3, 2019 at 7:37 AM Joe Abley <jabley at hopcount.ca> wrote:

> Hi Tom,
> On May 2, 2019, at 23:24, Tom Samplonius via Unbound-users
> <unbound-users at nlnetlabs.nl> wrote:
> >   It is fairly common for ISPs to block all udp port 53 across their
> network, and only permit udp port 53 to their own DNS servers.  That is
> only two ACL rules, so it is very simple to implement.  I would say that in
> general, port 53 blocking is something that happens less and less.
> That would spell "support apocalypse" in any residential ISP I've ever
> used, and a shortcut to "we can't make payroll" via "all the customers
> have gone". I have never seen it outside hotel/retail guest networks.
> Do you have any measurements to support "fairly common"? If that's
> right and my experience is atypical it's the kind of thing I'd like to
> understand.
> Joe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.nlnetlabs.nl/pipermail/unbound-users/attachments/20190503/36698371/attachment.htm>

More information about the Unbound-users mailing list