What's new

Diversion Issue with "Exclude devices from ad-blocking feature"

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

bfg100k

New Around Here
I followed the instructions here - https://diversion.ch/diversion/manual/exclude-devices-from-ad-blocking.html and while my device is now bypassing diversion, it is no longer able to resolve local hosts.

Issuing a nslookup on this device yields the following output.
$ nslookup diskstation.home.arpa
Server: 10.1.1.100
Address: 10.1.1.100#53

** server can't find diskstation.home.arpa: SERVFAIL

Just wondering if this is a bug or its meant to be so?
 
Last edited:
I followed the instructions here - https://diversion.ch/diversion/manual/exclude-devices-from-ad-blocking.html and while my device is now bypassing diversion, it is no longer able to resolve local hosts.

Issuing a nslookup on this device yields the following output.
$ nslookup diskstation.home.arpa
Server: 10.1.1.100
Address: 10.1.1.100#53

** server can't find diskstation.home.arpa: SERVFAIL

Just wondering if this is a bug or its meant to be so?
It's not a bug, just maybe I'd have to include Dnsmasq directives for the routers domain.
I'll include an option to include these directives in the next Diversion update if you so wish.
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top