Bold indicates a button clicked or key pressed.
“quotes” indicates a value which has been entered.
Grey block quote is a command typed directly into the console.
If you happen to come across the following error:
Joined ‘LOCALHOST’ to realm ‘test.lcl’
[2010/03/04 14:39:39, 0] utils/net_ads.c:1080(net_update_dns_internal) net_update_dns_internal: Failed to connect to our DC!
DNS update failed!
This simply means that your FQDN entry for the Linux system you are trying to join is incorrect as far as AD is concerned. In this case the box LOCALHOST.LOCAL.LCL was trying to join the domain TEST.LCL and there was an obvious mismatch. However not quite as obvious of an error message. Update this information in your /etc/hosts file and you should be set!

miro | 09-Mar-10 at 9:56 am | Permalink
Hallo,
I’ve same problem. How I can update hosts file to fix it?
Andrew | 09-Mar-10 at 10:06 am | Permalink
To edit your /etc/hosts file, open it up in your editor of choice (vi, nano, ee, etc…) and replace the information about localhost.localdomain with your actual hostname and domain suffix. So for instance if you had.
127.0.0.1 localhost, localhost.localdomain
Change this to
127.0.0.1 servername, servername.yourdomain
And of course replace those with your actual names, whatever they may be. Save the /etc/hosts file and then retry joining the domain. Hope that helps!
Frans | 24-Mar-10 at 9:10 am | Permalink
Hello
I still get this error after checking my /etc/hosts file.
host file looks like this:
127.0.0.1 debian-proxy debian-proxy.lln.local
192.168.0.1 llnserver llnserver.lln.local
192.168.0.2 debian-proxy debian-proxy.lln.local
when typing net ads join -U administrator -S llnserver.lln.local i get ‘Joined ‘DEBIAN-PROXY’ to realm ‘LLN.LOCAL” and the error that is standing above.
what am I doing wrong?
n00t | 09-Jun-10 at 1:41 pm | Permalink
Thanks, worked for me
Anne Tuen | 08-Jul-10 at 5:32 am | Permalink
Just a further caveat…
Oddness of oddness, if you have a single space between the name entries, i.e
127.0.0.1 debian-proxy debian-proxy.lln.local
192.168.0.1 llnserver llnserver.lln.local
192.168.0.2 debian-proxy debian-proxy.lln.local
It seems to work, however, on my system, if you attempt to tidy it up so it looks nice, e.g.
127.0.0.1 debian-proxy debian-proxy.lln.local
192.168.0.1 llnserver llnserver.lln.local
192.168.0.2 debian-proxy debian-proxy.lln.local
the update failure returns…
what is that all about?
Anne Tuen | 08-Jul-10 at 5:34 am | Permalink
ooops – multiple space have been mangled by HTML,
but in the example, all the names are lined up nice and pwetty
guess I should have used ‘ ’ or something
Anne Tuen | 08-Jul-10 at 5:35 am | Permalink
should have been
127.0.0.1 debian-proxy debian-proxy.lln.local
192.168.0.1 llnserver llnserver.lln.local
192.168.0.2 debian-proxy debian-proxy.lln.local
It seems to work, however, on my system, if you attempt to tidy it up so it looks nice, e.g.
127.0.0.1 debian-proxy debian-proxy.lln.local
192.168.0.1 llnserver llnserver.lln.local
192.168.0.2 debian-proxy debian-proxy.lln.local