0

Synology CLI - Docker Apps Not Using Synology as DNS server

I have NextDNS running successfully on my Synology (via CLI) and have pointed my router to the Synology's IP as the primary DNS server, so all of my devices are now using Synology as expected. How to do I get Synology apps themselves to use NextDNS, though? I feel like I'm missing a setting within Synology's Control Panel to point to itself as the DNS server.

Under Control Panel » Network » General, I have "Manually configure DNS server" deselected. Under Network Interface, I've set my LAN connection under IPv4 to use a manual configuration so I can set my static IP for the Synology device, and I've left the DNS server setting blank, assuming it will use the gateway (ie, router) defaults.

When I launch a Firefox instance via Docker, however, and I go to the NextDNS setup page, it shows that I'm using Google DNS (my router's secondary DNS) as the DNS resolver.

1 reply

null
    • Phillip_Deackes
    • 7 mths ago
    • Reported - view

    This post is over a year old, and like many posts on here nobody has bothered to respond. For the benefit of anyone arriving here through search I have what I think is a solution.

    In the network section of the Synology control panel select 'manually configure DNS server' and enter the static address of the NAS. That will force DNS traffic through the CLI installed on the NAS. Just remember what you've done so that if you change to something else, like Raspberry Pi, you can go back in and change the DNS address to point to the new device.

Login to reply

Content aside

  • 7 mths agoLast active
  • 1Replies
  • 273Views
  • 2 Following