[ AdGuard Home ] [ 0.107.24 ] Network-wide ads & trackers blocking DNS server

[QNAP_Stephane]

Source : https://adguard.com/ https://github.com/AdguardTeam/AdGuardHome

Download : x64, x86, arm-x41 , arm-x31

Premium

https://www.myqnap.org/product/adguardhome-premium/
Start on all NAS please read information on myqnap.org

Legacy

https://www.myqnap.org/product/adguard-home/

About :

Privacy protection center for you and your devices
Free and open source, powerful network-wide ads & trackers blocking DNS server.

AdGuard Home
AdGuard Home is a network-wide software for blocking ads & tracking. After you set it up, it'll cover ALL your home devices, and you don't need any client-side software for that.

How does AdGuard Home work?
AdGuard Home operates as a DNS server that re-routes tracking domains to a "black hole," thus preventing your devices from connecting to those servers. It's based on software we use for our public AdGuard DNS servers -- both share a lot of common code.

How is this different from public AdGuard DNS servers?
Running your own AdGuard Home server allows you to do much more than using a public DNS server.

Choose what exactly will the server block or not block;
Monitor your network activity;
Add your own custom filtering rules;
In the future, AdGuard Home is supposed to become more than just a DNS server.

[Skeptical.me]

"Router

This setup will automatically cover all the devices connected to your home router, and you will not need to configure each of them manually.

Open the preferences for your router. Usually, you can access it from your browser via a URL (like http://192.168.0.1/ or http://192.168.1.1/). You may be asked to enter the password. If you don’t remember it, you can often reset the password by pressing a button on the router itself. Some routers require a specific application, which in that case should be already installed on your computer/phone.

Find the DHCP/DNS settings. Look for the ’DNS’ letters next to a field which allows two or three sets of numbers, each broken into four groups of one to three digits.
Enter your AdGuard Home server addresses there."

I'm using a QNAP TS-253Be and I've installed the .qpkg that was created for QNAP models and have put 192.168.1.219 (NAS IP) into the DHCP>DNS field (which is what you have to if using your router) and my devices are still showing ads. Also, no devices show in AdGuard Home https://imgur.com/a/xScvcDv


https://github.com/AdguardTeam/AdGuardHome/wiki

If anyone can successfully set this up in their router/ NAS it would be great if you could detial what edits to the router/NAS you made to get it working. Thanks

[QNAP_Stephane]

arm64 version added

[ameer]

arm64 version added

Can you help us regarding port 16553
When we enter DNS in router it suppose to only listen on 53
How to configure router/qnap for the changed dns port?

[QNAP_Stephane]

for coredns port

simply edit /opt/AdGuard/AdGuardHome.yaml to fit on your needs...
and restart

but dont think using :53 will work (cant say for the NAS itself.. but probably somwhere in dnsmasq config )

[ameer]

for coredns port

simply edit /opt/AdGuard/AdGuardHome.yaml to fit on your needs...
and restart

but dont think using :53 will work (cant say for the NAS itself.. but probably somwhere in dnsmasq config )

Thanks for reply, but if we can't use port 53, what our other options? What the purpose of change the default 16553??
I think we only have little options:
- Configure Adguard app to use another IP other than server IP.
- Add a rule in router to forward "port 53" queries to "16553" << I don't know how exactly.

So how you managed to make it work in your system?

I think I like Adguard UI better than pi hole, but I have the same problem with pi-hole regarding port 53 (Was working fine in older firmware)

Look to this topic:
viewtopic.php?t=143406

Specifically:

NOTES
I do not know if this was ultimately necessary, but I did manually kill the dnsmasq process running on the QNAP. I was getting a message from the container saying that port 53 was already being used. From the command line, issue a "ps x | grep dnsmasq" command. Then take the process number and issue a "sudo kill X" where X is the process number. You can reissue the "ps x | grep dnsmasq" to make sure dnsmasq is no longer running.
Top

I tried that, but it give me error in command:
*USER* is not in the sudoers file. This incident will be reported.
I disabled admin account by the way, and logged through a new Adminstrator account (myusername)

[QNAP_Stephane]

ok think i have found a work around

stop adguard

AdGuardHome.yaml and modify to

Code: Select all

coredns:
  port: 53
  protection_enabled: true

edit /etc/dnsmasq.conf

and change port 53 to 1053 (for example)

edit /etc/resolv.conf and modify

Code: Select all

nameserver 127.0.1.1:1053

in ssh restart dnsmask

Code: Select all

killall -9 dnsmasq  # kill dnsmasq process
dnsmasq               # restart dnsmasq

restart adguard.. it is running now on port 53

not sure it will be reboot persistent (i opened a ticket on Qnap bugtracker to make R&D change the binding and ports)

[ameer]

ok think i have found a work around

stop adguard

.
.
.
.

restart adguard.. it is running now on port 53

not sure it will be reboot persistent (i opened a ticket on Qnap bugtracker to make R&D change the binding and ports)

Thanks, it finally work!

[Flyingfufu]

Many thanks @QNAP_Stephane !

This one is working nicely and cover all device very easily (after the small tweak)...

Regards,

[Skeptical.me]

ok think i have found a work around

stop adguard

AdGuardHome.yaml and modify to

Code: Select all

coredns:
  port: 53
  protection_enabled: true

edit /etc/dnsmasq.conf

and change port 53 to 1053 (for example)

edit /etc/resolv.conf and modify

Code: Select all

nameserver 127.0.1.1:1053

in ssh restart dnsmask

Code: Select all

killall -9 dnsmasq  # kill dnsmasq process
dnsmasq               # restart dnsmasq

restart adguard.. it is running now on port 53

not sure it will be reboot persistent (i opened a ticket on Qnap bugtracker to make R&D change the binding and ports)

Sorry for the noob question Stephane, or ayone else. How do I find the .yaml file in SSH terminal?

[Flyingfufu]

Go to "/share/CACHEDEV1_DATA/.qpkg/AdGuard "

[Skeptical.me]

Go to "/share/CACHEDEV1_DATA/.qpkg/AdGuard "

Oh, of course. thank you very much, I forget these things so easily.

[QNAP_Stephane]

or by symlink set in /opt

/opt/AdGuard

[Skeptical.me]

or by symlink set in /opt

/opt/AdGuard

Thanks Stephane.

[ameer]

In the future, AdGuard Home is supposed to become more than just a DNS server.

Request:
I port-forwarded my NAS to be visible from outside, I'm sucessefully used my external IP as dns server (not static ip from my isp by the way).

- Since Android 9 support system wide dns server (regardless of connection on WiFi or cellular network) but only support it over tls, so I failed to add my NAS domain name (or even external IP).

Can you help in this matter?
Thanks.