6 ms·
If you run a pi-hole create a config file in /etc/dnsmasq.d such as 02-archive.is.conf with the following server=/archive.is/8.8.8.8 server=/archive.i
by _l4jh 5y ago
If you run a pi-hole create a config file in /etc/dnsmasq.d such as 02-archive.is.conf with the following
server=/archive.is/8.8.8.8
server=/archive.is/8.8.4.4
server=/archive.li/8.8.8.8
server=/archive.li/8.8.4.4
server=/archive.to/8.8.8.8
server=/archive.to/8.8.4.4
server=/archive.today/8.8.8.8
server=/archive.today/8.8.4.4
And restart dnsmasq (or just reboot the pi)
This will resolve the common archive.is domains using Google's DNS service rather than 1.1.1.1 but everything else via 1.1.1.1 as normal.
- unityByFreedom 5y agoI just installed pi-hole and it says version 4 doesn't use dnsmasq anymore [1]. edit: Nevermind, your configuration worked. I verified after flushing DNS cache that archive.is was at first inaccessible, and now after a pihole reboot it does resolve. Thanks! I wonder if this is another way to set up the same thing with PiHole's "FTL-DNS" [2] [1] https://docs.pi-hole.net/ftldns/dns-resolver/ https://docs.pi-hole.net/ftldns/dns-resolver/ [2] https://docs.pi-hole.net/ftldns/configfile/#pihole_ptr https://docs.pi-hole.net/ftldns/configfile/#pihole_ptr