To configure a domain controller as a global catalog server, you need to modify the NTDS Settings object for that domain controller. In Active Directory Sites and Services, you can locate the domain controller and access its NTDS Settings. From there, you can enable the global catalog checkbox, effectively designating the domain controller as a global catalog server.
To meet the requirements of preventing authentication by using NTLM, using Kerberos to verify authentication requests, and preventing users from signing in to a client computer if it is disconnected from the domain, you should add the users to the Protected Users group. Members of this group can only use Kerberos for authentication and are restricted from using NTLM, Digest Authentication, or CredSSP. Additionally, they cannot log on if the computer is disconnected from the domain because user credentials cannot be cached locally.




Running Set-DnsServerCache is the correct approach. When users can access the external website from home but not from within the internal network, it indicates that the issue is likely due to outdated DNS cache entries in the internal DNS server. The Set-DnsServerCache cmdlet can be used to clear the DNS server cache, ensuring that the DNS servers resolve the URL to the updated IP address immediately. This directly addresses the problem of the internal DNS server holding onto stale records. Options involving dnscmd, Set-DnsServerGlobalQueryBlockList, or ipconfig commands do not directly address clearing the DNS cache in this context.