I just don't know where to go from here - from everything I've read they should be happy.So how exactly did Russia hack the election? Well, it didn’t. Performing 'ping -a dc2.ip.address' from DC1 comes back fine - it knows what it is in both directions (name and IP) but nslookup and nameserver resolution is still failing. Reverse DNS zones are setup for all the subnets used, there are A records and PTR's for both DC's. Restarting DNS Server, NETLOGON and registering in DNS from DC2 had DC1 talking to it fine for a few minutes, but then it went back how it is (and I haven't been able to replicate this fix since).
When trying to resolve name servers from DC1, DC2 sits at 'validating' for a while and then comes back with 'a timeout occurred during validation'. I get this timeout error for internal and external names, but both DC's are able to ping and access internet with no issues. DC2 is at another site, on another subnet and replicates to and from DC1 only.ĭC2 appears to have no issues, it can resolve any address, nslookup either using itself or DC1 is fine and name servers resolve fine.ĭC1 has massive issues with DC2 - using it for nslookup gives me the following: Within our domain there are two domain controllers for the child domain we manage.ĭC1 has connection back to the parent DC's (managed by our clients parent company), and also replicates both ways with DC2. This issue was discovered when searching for why users at our second site were experiencing slow logons every morning (5-10minutes to login). I've been trying to trudge my way through an issue our client is having but I'm getting nowhere fast.
0 kommentar(er)
