Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Domain Controller without DNS Server

Status
Not open for further replies.

fredmartinmaine

IS-IT--Management
Mar 23, 2015
79
0
0
US
We had a pair of Domain Controllers that offered AD Authentication, DNS and DHCP. Dynamic DNS actually.
A decision has been made to move DHCP and DNS to another device, a firewall. I moved DHCP a while ago, and other than not having Dynamic DNS, it's worked well.

However, when I start up DNS on the firewall, and stop the DNS Server service on the Domain Controller, server shares start asking users to authenticate to browse to a share, and eventually logging in to a domain PC fails because it can't find a domain controller.

I've read in a handful of places that domain controllers don't need to be DNS servers but they don't offer any information on how that's properly set up.

Does anyone know what I'm missing here?
 
Did you integrate the Active Directory namespace into the firewall's DNS service?

You might want to try reading this
 
I did not. I'll read the article, thanks. I didn't see anything in the firewall GUI config that applies, but I know this firewall sometimes needs CLI setup for advanced features. Hopefully it's able to accommodate. It's a Fortigate 60F.
 
What's the reasoning for moving DNS to the fortigate? If its some filtering based on DNS (Cisco Umbrella?) then just use forwarders on the Windows DNS servers and disable root lookups.
I don't think I'd be keen on moving the DNS functionality for a Windows AD setup to a fortigate box.
 
We're retiring the domain. Company made the decision to move everything to the cloud. Data is already there. We've already got some of the workstations authenticating through Google with GCPW, they're not even on the domain. This is a step. In the end, DNS and DHCP will be served from the firewall, authentication through Google, and VPN access to the inside will be no more. I suspect, if we can't get authentication from AD to work in concert with DNS on the firewall, we'll skip that step and just move all the workstations off the domain sooner than planned.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top