Description

This test case verifies that adcli info works even when the domain topology is complex.

Setup

Setting up the requirements for this test is somewhat complex.
It is necessary to have complete domain DNS resolution working for this test.
Make sure to complete the prerequisites before starting this test.
Test general adcli info functionality before doing this test.
The domain must have multiple sites with one domain controller in each site. You must be able to modify the domain DNS configuration.
The domain controller for the local site should be writable (the default).

Run adcli to get the local computer-site:

$ adcli info domain.example.com | grep computer-site

Use the Active Directory Sites and Services tool on Windows Server to identify which is the domain controller that handles the local site.
Use the Active Directory DNS on Windows server to remove the _ldap._tcp.domain.example.com record for the domain controller that covers the local site. There should be one or more other records for other domain controllers.
Verify that the SRV record change has taken effect:
```
$ host -t SRV _ldap._tcp.domain.example.com
```
The domain controller for the local site should not be listed. There should be a at least one other domain controller listed.
Run adcli to get domain info
adcli info domain.example.com

The output should have the right domain-controller listed for the local site, even though it is missing from the SRV record.

The output domain-controller-site and computer-site should match.

The output should say domain-controller-usable = yes.

Use the --verbose argument to provide output when troubleshooting or reporting bugs.
If you have a caching nameserver between you and Active Directory you may need to restart it or wait until its caches timeout. Alternatively place the Active Directory DNS server directly in /etc/resolv.conf