25 ms·

> DNS and DHCP (although why you wouldn't just let your router do that even back in 2008 escapes me) Doesn't Active Directory depend on being able to write to

• smackeyacky 5y ago
  That might be the reason it was set up that way, I've never been an AD administrator so I'm not sure. For a small business, it probably was much easier to have the DHCP and DNS stuff under one system rather than also having to learn how the router works.
• jve 5y ago
  AD DNS features security ACLs where you give permissions on records who can write what. Computer accounts make their own DNS records and enables updating them securely to whatever address you got assigned (office 1, office 2, VPN..). AD is certainly dependant on DNS and being able to write it. Adding domain controllers adds some srv and A records so that it is discoverable by services like LDAP, Kerberos. Moreover, Kerberos won't work without a proper DNS name as SPNs must match, even if you RDP into a client workstation. Connecting by IP fallbacks to NTLM. AD, according to wiki, was previewed in 1999. I don't know if there are standards that would enable secure DNS update at that time or not and the prevelance of routers that supported DNS client registrations.