search for: short_hostnam

...> nameserver 10.0.0.1 > search HOME.ROB-CAMPBELL.LAN The order doesn't matter, just so long as the first nameserver (10.0.0.10) is a DC. > > > > > While you are checking, does /etc/hosts contain a line like this: > > > > computers_ip computers FQDN computers short_hostname > > > > Yes > > root at D01:~/.bin# realm leave I suggest you stop using realmd, it isn't a Samba product and you do not need it, the same goes for sssd if it is also installed. > root at D01:~/.bin# net ads join -U administrator > Password for [HOME\administrator]:...

...bell.lan > nameserver A.DC.IPADDRESS > This is what it looks like in this order (if that matters) nameserver 10.0.0.10 nameserver 10.0.0.1 search HOME.ROB-CAMPBELL.LAN > > While you are checking, does /etc/hosts contain a line like this: > > computers_ip computers FQDN computers short_hostname > Yes root at D01:~/.bin# realm leave root at D01:~/.bin# realm list root at D01:~/.bin# cp /etc/samba/smb.conf.converted /etc/samba/smb.conf root at D01:~/.bin# realm list home.rob-campbell.lan type: kerberos realm-name: HOME.ROB-CAMPBELL.LAN domain-name: home.rob-campbell.lan config...

...name, > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ It looks like DNS is failing, does /etc/resolv.conf look like this: search home.rob-campbell.lan nameserver A.DC.IPADDRESS While you are checking, does /etc/hosts contain a line like this: computers_ip computers FQDN computers short_hostname Rowland

...t; saying the A record already exists and it can't "update" the DNS. If > so, a less scarey message would be nice. Please advise. > This is probably down to a dns problem, I usually give my servers a fixed IP and then add the machines dns info to /etc/hosts: IPADDRESS FQDN SHORT_HOSTNAME I never have the problem you are having. If you do not want to set a fixed ip, then ensure that your dhcp server is supplying all the required dns data and that your server knows it. I also hope that '.local' is a placeholder for the real TLD. > > Issue #3: getent not working &g...

....ROB-CAMPBELL.LAN > > The order doesn't matter, just so long as the first nameserver > (10.0.0.10) is a DC. > > > > > > > > > While you are checking, does /etc/hosts contain a line like this: > > > > > > computers_ip computers FQDN computers short_hostname > > > > > > > Yes > > > > root at D01:~/.bin# realm leave > > I suggest you stop using realmd, it isn't a Samba product and you do > not need it, the same goes for sssd if it is also installed. > > > root at D01:~/.bin# net ads join -U adminis...

...ists and it can't "update" the DNS. If > > so, a less scarey message would be nice. Please advise. > > > > This is probably down to a dns problem, I usually give my servers a > fixed IP and then add the machines dns info to /etc/hosts: > > IPADDRESS FQDN SHORT_HOSTNAME > > I never have the problem you are having. > > If you do not want to set a fixed ip, then ensure that your dhcp server > is supplying all the required dns data and that your server knows it. I've never had this problem either. I've joined Linux members in the past to both...

I've successfully joined two Linux Domain Members to two different Domains. Now, I'm joining a second Linux host as a Domain Member to a Samba4 (4.18.9) Domain. I'm having some possible issues this time. Issue #1 Reverse Zone On the SambaWiki: https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member, under 2.5 Forward Lookup, no problem: # host mail mail.hprs.local has

Getting this error when trying to join computer to the domain. I just built a new debian computer for gaming and photo and video editing. I went through the same process as I did before (I created a script to do all of the things I did in the past) net ads join -U administrator Password for [HOME\administrator]: Failed to join domain: failed to find DC for domain HOME - The object was not found.