3 ms·
Correct. And it would be a problem if something was listening on 80/443/whatever. That's why '--dest-ip' can be set. from man dnsmasq: -B, --bogus-nxdomain=
by jakeogh 11y ago
Correct. And it would be a problem if something was listening on 80/443/whatever. That's why '--dest-ip' can be set.
from man dnsmasq:
-B, --bogus-nxdomain=<ipaddr>
Transform replies which contain the IP address given into "No such domain" replies.
This is intended to counteract a devious move made by Verisign in September 2003
when they started returning the address of an advertising web page in response to
queries for unregistered names, instead of the correct NXDOMAIN response. This
option tells dnsmasq to fake the correct response when it sees this behaviour. As
at Sept 2003 the IP address being returned by Verisign is 64.94.110.11
Is there another way to get dnsmasq to return NXDOMAIN? If I am reading this correctly, one would need to do 'dnsgate --dest-ip 127.2.2.2' and then tell dnsmasq '--bogus-nxdomain=127.2.2.2'.
- StavrosK 11y agoThat's fantastic, thank you for the tip!
- egwynn 11y agoOnly just followed up on this thread. Yes. My dnsmasq.conf contains: servers-file=/usr/local/etc/dnsmasq-servers.conf and then that file contains a lot of lines like: server=/taboola.com/ The docs don’t tell you that this results in NXDOMAIN for the server whose IP you didn’t specify. It seems to work!
- jakeogh 11y agoMuch better! Fixed: https://github.com/jakeogh/dnsgate/commit/62bfa78ac27586d048a8f193b1290166d0fe6b75 https://github.com/jakeogh/dnsgate/commit/62bfa78ac27586d048...