I have Server Essentials 2016. Each client that I connect gets their DNS set to the SE2016 box during connection. My router has it’s DNS set to the ISP. I have some weird issues with the internet just not working at times, but it seems it might just be DNS issues.
What should the setup be for the router and the clients?
- Should the router have it’s DNS set to the SE2016 box?
- Should I change my clients to use the router for DNS instead?
- Should I add my router as a second DNS to my clients in case the SE2016 box isn’t handling the request?
- Anything else I should know?
I’m sure there is a correct way of setting this up, but I’m not really finding much info on this. I probably just don’t know what to search for to get the answer.
This is a home setup, and the SE2016 box is pretty much only used for backups and a file share.
Answer
Your clients should use the SE2016 box for primary DNS, because it is the only thing able to resolve hostnames on your local network (assuming it is actually configured as a DNS server, that is). Resolution of these names is needed for smooth running of many applications, but they will not be in the public DNS which is what your router forwards or recurses to.
You can add the router as secondary DNS for your client as a last resort for internet access if the server is down, but as above in that scenario you will have trouble with things that require local name resolution, e.g. connecting to other hosts on your network by name.
It would be good to have the background on the “weird issues with the internet” that you are attributing to DNS, in order to provide the most useful response.
Attribution
Source : Link , Question Author : Josh Close , Answer Author : Mintra
