Synology DNS Server Setup: Faster & Private Local Network

Did you know I can do more than store data with my Synology NAS? It offers a powerful DNS server package for free. This feature speeds up my internet and lets me access all my internal devices by name. No more trying to remember or deal with IP address changes.

Join me as I set up my Synology NAS to become a master DNS server.

Quick answer (DSM 7.x): What is the Synology DNS Server?

The Synology DNS Server is a free package you install from the DSM Package Center. It turns your NAS into a local DNS server, translating domain names into IP addresses for every device on your network. It handles forward zones (name-to-IP) and supports DNS forwarding to external resolvers such as Cloudflare or Google for anything outside your local network.

DNS queries remain within your network, improving privacy and potentially reducing latency. You need a Synology NAS running DSM, a static local IP for the NAS, and about 10 minutes.

Synology DNS Server for Local Network

When I first explored my Synology NAS, I discovered a game-changer for my home network: the Synology DNS Server. This tool was a revelation, promising to simplify how I connect to my devices at home or in my small business.”

Understanding the Basics of DNS

To get started, let’s break down what DNS means. DNS stands for Domain Name System. It’s like the phonebook of the internet, translating website names we understand, like google.com, into IP addresses that computers use to identify each other. But DNS domains aren’t just for the internet. Inside my local network, DNS helps me access devices like my computer, printer, or NAS by name instead of by complex IP addresses. This simplicity was exactly what I needed.

Why Choose Synology for DNS Services?

Most ISP routers do not let you change DNS settings at all. You get what they give you, and that is it.

Running the DNS Server package on my Synology NAS solves that. It is free, it runs on hardware I already own, and it gives me full control over my local zones. I can assign friendly hostnames to every device on my network, use a privacy-focused resolver like Cloudflare for external queries, and block specific domains network-wide without installing anything extra.

The practical difference is noticeable. I access my NAS, my home server, and my printer by name instead of remembering IP addresses that change. Any device on the network gets that automatically once you point your router’s DHCP to the Synology

Synology DNS Server Setup

Getting your Synology DNS Server up and running involves two main steps: installing the DNS package and then setting up zones and records. Here’s how I did it:

Install the DNS Package

Log into DSM: First, I logged into the DiskStation Manager (DSM) on my Synology NAS. The DSM is the operating system that runs on Synology NAS devices, where you manage all the settings.
Open Package Center: I navigated to the Package Center from the main menu. This is Synology’s app store, where you can find helpful packages to enhance your NAS.

Find DNS Server: In the Package Center, I searched for “DNS Server” in the search bar. It’s a free package provided by Synology.

Install: Once I found the DNS Server package, I clicked ‘Install.’ It took a couple of minutes to download and install. After installation, the DNS Server appeared in my main menu, ready to be configured.

Setting Up Zones and Records

Open DNS Server: I launched the DNS Server app from the main menu. This opened the DNS Server interface, where I could set up my zones and records.
Create a Master Zone (zone file): I needed to create a Primary Zone. This is a default domain name that I control within my network.
I clicked ‘Create’ and then ‘Primary Zone.’ I used a domain name I own for the zone name, but you can use any name if it’s just for your local network, like ‘myhome.local.’

For “Primary DNS Server” enter the IP address for your Synology NAS. In my case, it is 192.168.1.11. You can leave all the other options as they are.

Add A Record: With my Primary Zone created, it was time to add records. An A record maps a domain name to an IP address, crucial for accessing devices by name. I clicked on my newly created zone and selected ‘Edit, Resource records’ and ‘A Record.’ Here, I entered the hostname (like ‘nas’) and the IP address of my Synology NAS. This enabled me to access my NAS using ‘nas.myhome.local’ instead of its IP address.

The picture above shows that the Synology DNS Server automatically added two records. NS stands for Nameserver and there is an A zone records for ns.myhome.local too.

I added another A record for the same IP with another name, ‘nas’. Adding more than one A record for the same IP is possible.

Now, you can add more A records for your devices in the local network.

Configure the Synology DNS Server: Setting Up DNS Forwarding

After installing the DNS package and setting up zones and records, there’s one more critical step to ensure your Synology DNS Server manages your local network efficiently and provides seamless internet access: DNS forwarding. Here’s how I configured DNS forwarding on my Synology NAS, using the example where the DNS server IP is 192.168.1.11:

Understanding DNS Forwarding

DNS forwarding is like having a personal assistant for your network. When a device asks for the address of a website, the Synology DNS Server checks if it’s something within your local network. If not, it forwards the DNS requests to another DNS server on the internet, which knows how to find all those websites you and your network want to access.

How to Set Up DNS Forwarding

Open DNS Server Application: Log into your Synology DSM and open the DNS Server application from the main menu.
Navigate to the Resolution Settings: Look for the ‘Resolution’ tab in the DNS Server application. This is where you’ll set up forwarding.
Enable Forwarding: There should be an option to enable forwarding. Check this option to turn it on.
Specify Forwarder IP Address: Enter the IP addresses of the DNS servers you want to forward queries to. These can be public DNS servers like Google’s 8.8.8.8 and 8.8.4.4, Cloudflare’s 1.1.1.1, or any other DNS servers provided by your ISP. It’s a good practice to use at least two for redundancy.
Apply and Save: After entering the forwarder IP addresses, apply and save your settings.

My pick

My Synology NAS recommendations

Synology DS725+ 2-Bay Diskstation NAS (Ryzen R1600, 4GB Ram), 1x 2.5GbE, 1x 1GbE, 2X M.2 NVMe Steckplätze 8TB Bundle with Seagate Ironwolf 2X 4TB

$1,161.04

Buy on Amazon

06/29/2026 10:13 am GMT

How to Point Devices to the New DNS Server

Now that you’ve set up the Synology DNS Server let’s ensure your devices use it for DNS resolution. We’ll use the example where your Synology DNS Server has the IP address 192.168.1.11.

For Individual Devices (example Windows 11)

Access Network Settings: Open ‘Settings, Network & Internet” on your device.
Select the Connected Device, in my case it is Ethernet.
Click DNS server assignment: change to manual from ‘Automatic DHCP’
Enter DNS Server Address: In the DNS server settings, replace any existing addresses with 192.168.1.11, the IP of your Synology NAS.
Save and Restart Device: Save your settings and restart your device to apply the new DNS configuration.

For Your Entire Network via the Router

To make sure all devices on your network automatically use the Synology DNS Server, you’ll need to update the DNS settings in your router’s DHCP configuration:

Log into Your Router: Open a web browser and type your router’s IP address into the address bar to access the router’s interface. You’ll need to log in with your username and password.
Locate DHCP/DNS Settings: Find the DHCP settings, which might be under ‘Internet,’ ‘LAN,’ or ‘Network Settings.’ Within the DHCP settings, look for an option to specify DNS servers.
Update DNS Server to 192.168.1.11: In the DNS server fields provided by the DHCP settings, enter 192.168.1.11 as the primary DNS server to direct all connected devices to use your Synology NAS for DNS queries. It’s a good idea to add a secondary DNS server, such as 1.1.1.1 or 8.8.8.8, for redundancy and to ensure uninterrupted internet access if the primary server becomes unreachable.
Apply Changes and Reboot Router: Save your changes after entering the new DNS server address. It’s often recommended to reboot your router to ensure all changes take effect properly. This action will cause the router to assign the new DNS server address to all devices connecting to the network moving forward.

I recommend changing DNS settings at your router and not on your device.

Testing your Setup

To verify that your DHCP settings, specifically the DNS server change to your Synology NAS (192.168.1.11), have been successfully applied across your network, you can use the ipconfig /all command on a Windows machine. This command provides detailed information about your network configuration, including the DNS servers your device is using. Here’s how you can test your DHCP settings:

Open Command Prompt: On your Windows computer, press the Windows key + R to open the Run dialog box. Type cmd and press Enter to launch the Command Prompt.
Run ipconfig /all: In the Command Prompt window, type ipconfig /all and press Enter. This command displays all your network configuration details.
Review the Output: Look for the output section corresponding to your active network connection. This might be labeled as “Ethernet adapter,” “Wireless LAN adapter Wi-Fi,” or something similar, depending on how you’re connected to your network.
Check the DNS Servers Listing: Within this section, find the line that reads “DNS Servers.” If your DHCP settings update was successful, you should see the IP address of your Synology NAS (192.168.1.11) listed as one of the DNS servers. It should also be listed if you entered a secondary DNS server, such as 1.1.1.1 or 8.8.8.8.
Verify Changes: If you see the correct DNS server addresses listed, your device is now using your Synology NAS as its DNS server, thanks to the updated DHCP settings on your router. If the expected DNS server IP addresses are not listed, you may need to disconnect and reconnect your device to the network or restart it to force it to request new DHCP information from the router.

This test is a straightforward way to confirm that your network devices are correctly using the new DNS settings provided by your router’s DHCP configuration. It ensures that all DNS queries from your device are being routed through your Synology NAS, leveraging its DNS server capabilities for name resolution.

Frequently Asked Questions

What happens if my Synology NAS goes offline?

If your NAS goes offline and it is the only DNS server on your network, devices will lose DNS resolution, and internet access will effectively stop working. The fix is simple: always add a secondary DNS server in your router’s DHCP settings. I use 1.1.1.1 (Cloudflare) as a fallback. If the NAS becomes unreachable, devices automatically switch to the secondary and keep working.

What DNS records does Synology create automatically?

When you create a Master Zone, the Synology DNS Server automatically generates three resource records: an SOA (Start of Authority) record, an NS (Nameserver) record, and an A record for the nameserver. The SOA record defines the zone’s authority and contains a serial number that increments with each change. You only need to add your own A records on top of those.

What is a reverse zone, and do I need one?

A reverse zone does the opposite of a forward zone. Instead of translating a name to an IP address, it translates an IP address back to a fully qualified domain name (FQDN) using PTR records. On a Synology DNS Server, a reverse zone only works for your internal private IP range, such as 192.168.x.x. For public IP addresses, reverse DNS is controlled by your ISP and cannot be managed from your own DNS server unless they explicitly delegate it to you. For most home and small business setups, an internal reverse zone is optional.

Does using a local DNS server improve privacy?

It does. When your Synology NAS handles DNS, queries for local devices never leave your network. Only requests for external domains get forwarded to your chosen resolver, such as Cloudflare or Google. Your ISP no longer sees every DNS query your devices make, and your browsing history stays local. Switching your forwarder to a privacy-focused resolver, such as 1.1.1.1, takes this a step further.

Can I use the Synology DNS Server to block websites?

Yes. You can create a Master Zone for any domain you want to block and point the A record to 0.0.0.0. Any device on your network using the Synology DNS Server as its resolver will fail to reach that domain. Keep in mind it only blocks the exact domain, not subdomains, unless you add wildcard records. It is a lightweight approach to network-wide content filtering, though a dedicated tool like Pi-hole gives you more control.

One more option worth knowing: you can use your Synology as a public authoritative DNS server and point a registered domain name to it as the primary zone. If you want to go deeper on hosting your own public nameserver, my DNS Server at Home guide covers that using ISPConfig. And if you plan to implement Active Directory in your environment, my Synology Directory Server guide is a good next step.