0

Previously I've used Unbound as a DNS resolver, but whenever I checked on dnsleaktest.com I got results for Google DNS only. Then moving to systemd-resolved fixed that issue. Now I'm using pdnsd, and that issue has showed up again.

I've blocked Google DNS server from /etc/hosts, added them to reject list in pdnsd.conf also blocked them from my router then how come they are still accessible?

3
  • 2
    "blocked Google DNS server from /etc/hosts" ... how that does that even work? O.o
    – muru
    Dec 7, 2021 at 5:26
  • @muru by adding the entries with localhosts? Dec 8, 2021 at 11:52
  • What entries would you add to do that?
    – muru
    Dec 8, 2021 at 12:50

1 Answer 1

-1

You could make a manual route like:

8.0.0.0/8 accessible via 192.168.0.254 (Or some other IP that is not a router)

That would mean, that your device would try to get to 8.8.8.8 via 192.168.0.254, but this device either is non-existent or is not a router, so you cant get to 8.8.8.8 this way.

On Linux you might achieve it with this command. Replace eth0 with proper device name, check with "ip a" command.

ip route add 8.0.0.0/8 via 192.168.0.254 dev eth0

I have no idea if this will make anything important inaccessible. Some examples for ip route command: https://www.cyberciti.biz/faq/howto-linux-configuring-default-route-with-ipcommand/

2
  • 2
    Blocking a /8 does not seem a particularly good idea. Dec 7, 2021 at 14:10
  • Can there be a route to 1 address? like 8.8.8.8
    – pormulsys
    Dec 9, 2021 at 7:00

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.