Hi
I have blocked two domains from a DVR and since being blocked they are making DNS requests every 15 seconds. Is there a way to make the DVR think the domains have resolved? maybe resolving them to a local IP?
Thanks for any advice.
Sorry to say but frenzied connections are common when apps and services can't connect to the mother ship. I see this all the time with phone apps and appliances like Amazon tablets. Unless they change their application code you will have to either unblock or accept that this is going to happen.
1 Like
Ok thanks
You could try even when I don't think it'll work (they'll still not find what they are looking for at this IP). Just add the domain in the /etc/hosts of your Pi-hole pointing to an address of your choice and see what happens. It's sad that every vendor seems to do its own thing there. Hence, you cannot really predict if solution for product A does anything at all with product B.
Thanks I'll try and see if it works and let you know.
Welcome to the cat and mouse game with apps and services. 
The flooding has stopped for now but it'll probably start again soon. I'll then try adding the domains to /etc/hosts
If that doesn't work I could let them resolve and block them in the router's domain blocking facility.
Good to hear...that trick never worked for any of my devices but I did get the pleasure of sending some traffic to some poor host at Amazon that runs add services for another platform. After a week I backed it out because I didn't want to be traced back.
I don't see how this could work because - at first glance - this seems to be the same Pi-hole does? If you do this in the end and it works better, we may be able to learn from your router. Routers can obviously do some much more involved things in the network (like really taking a device offline). Maybe it'd do something like that.
The flooding started again so I added the domain to /etc/hosts and pointed it to an unused local IP (10.15.0.20) then did sudo systemctl restart pihole-FTL.service and then unblocked the domain from within the Pi-hole admin. This seems to have worked and the domain hasn't been requested since (been approx 7 hrs). Note that I did test first by adding an unblocked domain to /etc/hosts to make sure it was being forwarded to 10.15.0.20 and not just resolving normally.
I don't see how this could work because - at first glance - this seems to be the same Pi-hole does? If you do this in the end and it works better, we may be able to learn from your router. Routers can obviously do some much more involved things in the network (like really taking a device offline). Maybe it'd do something like that.
My router has a basic domain blocking facility and I've tested it by adding an unblocked Pi-hole domain and the router does block it. So I guess before the router connects to a domain it checks if the domain is on the blocklist. I'm using Pi-hole for DHCP and it still seems to work ok.
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.