Internet connectivity with Domain Controller

Question

We have a Windows 2008 R2 Domain controller and every PC on the network has the IP address of domain controller set under DNS settings. Is it normal to have the Domain controller also be the DNS server and lose all internet connectivity to all of the computers on the network when the domain controller reboots? I understand that DNS is a core part of group policy, but how can I make it so all the machines in my network don't lose connectivity when the Domain Controller goes down? Do people normally have a backup/mirrored DNS or something? Sorry I'm self-taught and this is how the existing network was setup, before my time.

Solution

Two Domain Controllers. both also DNS servers, clients configured to use both for DNS. That is how it's done.

Comments

[Just Lucky Really]

I'm going off the assumption that you still want internet connectivity, without the need of a DNS server online in your LAN. Hence my answer to set the secondary DNS sever for the clients as an external DNS. You could make a second DC, but if they both went offline, you'd be back to square 1.

[MDMarra]

You should never have domain joined clients using a non-AD DNS server, @Stretch. The proper solution is to have more than one DC (it's critical after all) and run DNS on each.

[TheFrack]

Thanks for answering my question. I read all over the place that external DNS should never be used as an alternate, worst case with 1 server, it should be the gateway. Example: firelogic.net/… I will be temporarily using my local network gateway as secondary DNS until I get a second domain controller (if any).

[joeqwerty]

Glad to help...

[Admin]

@joeqwerty I believe they have answered the question. They state that that typical configurations have at least two controllers, and then go above and beyond by showing how to configure them. To be honest, creating an answer and then going on to give negative comments on the others is in poor taste and, frankly, quite rude. Comments are meant to be for building upon answers and providing constructive feedback, not just a "You're wrong" statement and negativity.

[joeqwerty]

1. You edited your answer after my comment. You did not originally have the preceding paragraph. You simply listed the DNS client settings on the Domain Controllers and you didn't have the following section with the Client DNS settings in your answer. 2. If an answer is wrong we have a responsibility to tell the person it's wrong. 3. Manners be darned. I can answer a question or post comments in any way I see fit. I don't see anything particularly offensive in any of my comments.

[MDMarra]

You've got this backwards. 127.0.0.1 should be last on your DCs. A quick run of the AD BPA on your domain controllers will confirm this.