- Read this and am getting some symptoms. Curious about the answer for this scenario.
- Read this but its for 2012 and talks about having a Windows server. Is this not possible to do in CONJUNCTION with a dedicated Firewall/ Router box.
- This link says its not a good idea, but.. Is there anyway to do a SEPARATION of CONCERNS? Let external requests be routed out and internal requests go to the DC?
- Wondering if there's some part of this we can leverage:
Moving the DHCP/DNS services from a Windows server (Active Directory) to a Linux machine
- Prevent / Throttle LAN clients using domain controller as gateway
SBS 2008/ Server 2008 DC Environment.
Originally DHCP was managed by DC, but now its been disabled.
We figured that if DHCP was handed off from the DC, domain clients could still carry on with their usual Internet/ Email activity via ISP connectivity.
But, for some reason when the DC is down, clients lose Net Access.
A dedicated Router/ Firewall box handles DHCP now. Let's say it uses 2 DNS entries:
ISP DNS 1 or Google DNS 1
ISP DNS 2 or Google DNS 2
Now, these Internet DNS will not understand or handle LAN / Local Domain DNS needs that the DC understands.
How should we configure the DC so that it works well (to service local domain DNSes) in co operation with the ISP / Google DNSes for external.
So, that even if the DCs are shut down clients can still access the Internet.
Could we configure them both such that External Internet requests continue forward via Router/ Firewall and ISP DNS (even if DC is down) while Internal Domain requests go to / via the DC.
Thoughts? Maybe use some kind of DNSMasq/ forward/ redirection from router/ firewall to the DC?