Hot answers tagged

5

There is a wealth of public information on how the DC Locator process works. Essentially it performs a series of DNS lookups and LDAP pings, and also attempts to stratify the results by selecting the closest domain controller. It's unusual for Windows DC Locator to continue to use a failed domain controller, unless the domain controller is passing the ...


2

The answer to your question is not related to DNS. When you create an Active Directory domain, amongst other things, you need to specify the domain name and the domain NetBIOS name. The domain name is the FQDN of your domain (acme.local). The domain NetBIOS name is by default (and usually never changed) the first part of your FQDN (acme) and also referred ...


2

We typically use Exchange HUB as a File Share Witness server. Here are MS's recommendations The witness server can't be a member of the DAG. The witness server must be in the same Active Directory forest as the DAG. The witness server must be running Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003 R2, or Windows Server ...


1

There is no immediate impact if your PDC DC goes down. You can plan to manually seize the PDC role from one of the remaining domain controllers. The process is descrbed well here https://www.petri.com/seizing_fsmo_roles


1

Ok I can now, after the testlab, answer this myself. The initial request for a TGT from the system being logged into to the domain controller contains the username in clear text in the kerberos payload of the network packet(s) (that much was already known). But: When logging in with domainname\username, this will be the username. When logging in with the ...


1

You should disable recursive queries on any Internet facing DNS servers. It is likely not a good idea to allow incoming Internet access to your domain-controller. Blocking recursion will break DNS for any host using your domain-controller as their DNS servers. Configuring firewall rules allowing only outgoing access (and replies) on port 53 would be ...


1

Your problem is you are trying to join a computer to a Windows domain without the client knowing where the DNS server is. In a Windows domain DNS is typically AD-integrated. What that results in is when you join a computer to a Windows domain, some information is created in both AD and DNS. In order for a computer to find the domain controller during the ...



Only top voted, non community-wiki answers of a minimum length are eligible