AD DNS Server - use multiple servers?

[sonynair]

Hi,

My Syno is joined to my domain with no issues.

However, in my AD setup I have a primary and secondary DNS Sever.

The Syno control panel only allows to enter a single IP address under "DNS Server" in the Domain/Workgroup tab within Control Panel.

This means when my primary DNS Server is down, authentication to AD from the Syno fail. It does not fail over to secondary.

How can I configure primary & secondary DNS servers in that text box?

Many thanks

[Fit]

I would post a feature request/suggestion for this on the forum since it is a very basic functionality that should be present in the DSM.

[sonynair]

Is there a configuration file I can edit to add a secondary DNS server, instead of relying on the GUI?

Thanks

[crisvG]

I would love to add a 2nd DNS too.

I noticed when the primary DNS is down (for example, the DC01) the Synology starts to respond extremly slow. A 2nd DNS for fallback (to a DC02) most probably will solve this issue.

I think its a must for business purposes to add at least 1 fallback DNS.

Could this (i think relative simple) change be implanted ?

[myCloud]

Just curious if adding the secondary after the primary, separated by a comma and space, would work in the configuration?

[sonynair]

Just curious if adding the secondary after the primary, separated by a comma and space, would work in the configuration?

I'm willing to give this a try if you can tell me what the configuration file that needs editing is?

Cheers

[myCloud]

I'm not sure where that would be. I tried doing it in the DNS field of the Network Control Panel and it wouldn't let me type anything past the first IP address.

[sonynair]

So I've been doing some digging and found that in linux dns lookup is performed by resolv.conf


cat /etc/resolv.conf

Code: Select all

nameserver 10.0.187.110
nameserver 10.0.187.110
search mydomain.com

Notice my primary and secondary are set to the same ip for some stupid reason - no wonder the NAS failed when primary server went down! Must be bug in DSM - I have logged a support ticket.

I used vi to update it to:

cat /etc/resolv.conf

Code: Select all

nameserver 10.0.187.110
nameserver 10.0.187.112
search mydomain.com
options timeout:1

I added "options timeout:1" because otherwise it was taking 10 seconds to failover to the secondary server for lookups.

This has fixed my issue and remains intact even after reboot.

Hope this helps you guys out.

[myCloud]

Thank you for sharing this!

[gurufarmer]

How do you get the file so its not in read only so you can edit it?