AdGuard is one of the leaders on the market of ad-blocking software with 10+ years of experience, almost a dozen products for various platforms, and over 30 million user installs
AdGuard Ad Blocker does more than just block ads. It will protect you from online tracking and enhance your privacy in many ways.
Depending on the specific product, AdGuard can also offer such perks as DNS filtering for more rounded-up protection, Parental Control to shield your kids from inappropriate content, Filtering log to have better control over your internet traffic, and more
Why Premium, this intends to fix the problem that Qnap NAS has port 53 already in use
this port need to be available to run any DNS Server
on first install don’t care about the message Network Virtual Switch cannot resolve due to DNS issue (this is a normal message since during the process I am tweaking dnsmasq.conf and resolv.conf)
on first setup, please use the port 3000 for web access (to allow QTS icon to open the web page)
change DNS of your NAS to 127.0.1.1 (you can add also 8.8.8.8 as secondary DNS)
Available for NAS with at least firmware 4.3.6 (Intel / amd64 / armv8 / armv7)
Last update: 31 March 2025
d1a (verified owner) –
Hello,
I am experiencing a DNS configuration issue on my QNAP NAS device. After implementing the following setup:
AdGuard running on port 53 for ad-blocking
dnsmasq configured to run on port 12153 for DNS management
resolv.conf pointing to 127.0.1.1:12153
Problem: My NAS is experiencing widespread service disruptions. Specifically, a range of services are no longer functioning properly, from basic system functions like time synchronization and repository access, to media applications like Plex, and general DNS resolution on the NAS itself. Interestingly, client devices (PCs, phones, etc.) continue to work correctly as AdGuard successfully filters their DNS queries.
Root Cause Analysis:
Port 53 is now occupied by AdGuard, which is necessary for client-side ad-blocking.
dnsmasq was moved to port 12153 (as per your recommendation), but this appears to be causing conflicts.
Certain NAS system services specifically require port 53 for DNS resolution and cannot use the alternative port.
Required Solution: I need a configuration where:
AdGuard continues to filter DNS queries for client devices.
NAS system services can properly resolve DNS.
No port conflicts occur between these services.
Specific Questions:
Is port 12153 an appropriate choice for dnsmasq in a QNAP NAS environment?
Can AdGuard be configured to share port 53 with system services?
Is there an alternative port configuration that would better accommodate both services?
Additionally, after the installation of AdGuard, the NAS seems to no longer receive a public IP address (31.41.xxx.xxx), which it had previously. This change may have affected how DNS queries and routing are handled, contributing to the disruption of services.
As a subscriber to your premium service, I would greatly appreciate your expertise in resolving this configuration issue so I can fully utilize the features I’ve invested in. I’m hoping you might be able to provide some guidance on this matter.
Thank you for your assistance.
PS:
I apologize for the previous review, I needed to add something, so I’m sending it again. Also, I’m not sure how else to contact the software author.
QoolBox –
not sure to all understand, please come on discord for issue.
i use it on a NAS without issue