So because I don't use openDNS, at least that should let me know adguard was the one that blocked it, and it's not a bad connection. Its based on software we use for our tested and trusted public AdGuard DNS servers both share a lot of common code. I like the ease of use, but I'm thinking both IIS and Apache out class Abyss for the most part. To put it simply, it operates as a DNS server that redirects ad and tracking domains to a 'black hole', thus preventing your devices from connecting to those servers. I've checked it out a few times, had it running a few ASP.Net demo sites, but haven't gotten to far with it. While it seems they don't actually show a block page unless you are actually using openDNS, they do a redirect to a big long domain/URL with "id./s/" in the middle. Just curious to see if anyone is using the Abyss Web Server for any projects. One option I just found though is OpenDNS has a list of IP addresses that appear to be exclusively used for block pages: I'd rather not have to run a whole web server on my pi just for a block page. I've been trying to find a public site/IP I could use for the block page IP but haven't had too much success. Unfortunately it doesn't seem to change what's in the URL bar, so it's indistinguishable from an actual Google 404 error. I just got one of Google's IP address and put it in there so at least there's a hint when something is being blocked, I'll see a Google 404 page. Under DNS Settings > DNS Configuration, you can adjust how blocking works, including one where you can specify an IP address to redirect blocked traffic to. I don't think there is a default block page for adguard home.
0 Comments
Leave a Reply. |