I ran in to a problem where the VPN between two of my offices went down due to a hardware failure and when we got it back up, the mapped drives between the two domains didn't re-establish. I checked the trusts and relationships, but they all looked good.
After trying everything else, I went ahead and tried to refresh the trust, but it errored out saying that it couldn't find a DC. My next thought was DNS, but it looked fine as well. I refreshed the zone, though, and it didn't come back up correctly. Using nslookup, I was able to see that while the domain name would resolve to the VPN IP address, the name of the domain controller was resolving to something external (as an alias of droub.parking.net, or something like that).
Flushing my DNS cache and setting up the forward look-up zone again allowed me to reconnect and re-establish the trust. My question, though, is why did this happen in the first place. Was this DNS poisoning or just an error that my DNS server incorrectly tried to fix on its own?
After trying everything else, I went ahead and tried to refresh the trust, but it errored out saying that it couldn't find a DC. My next thought was DNS, but it looked fine as well. I refreshed the zone, though, and it didn't come back up correctly. Using nslookup, I was able to see that while the domain name would resolve to the VPN IP address, the name of the domain controller was resolving to something external (as an alias of droub.parking.net, or something like that).
Flushing my DNS cache and setting up the forward look-up zone again allowed me to reconnect and re-establish the trust. My question, though, is why did this happen in the first place. Was this DNS poisoning or just an error that my DNS server incorrectly tried to fix on its own?