We have two issues using "net ads dns register". For both i have made minor changes to net_ads.c.
1. not responding DNS-Server
When the first nameserver returned is not responding "net ads dns register" fails.
Solution: go through all servers until update works or no more nameserver in the list.
2. machine fqdn differs from ad fqdn
When the domainname can not be fetched from hosts file (e.g. unix fqdn not equal to windows fqdn) "net ads dns register" fails with "No DNS domain...".
Solution: Try the REALM as DNS domain.
Not quite shure, but i thing the REALM is always the better choice. In our setup the unix/windows domains are seperated. In the domain_realm section of krb5.conf we map the unix to the windows-domain, so Kerberos works with this setup.
Created attachment 2770 [details]
patch meantioned in bug