samba - Sep 2022 - Samba unable to find SRV record during join

I just found out about the --server parameter to `samba-tool domain 
join`. I set it to the DNS name of one of the existing DCs, and the join 
succeeded.

I'd like to make sure that I understand the option description, though, 
which is:

     DC to join

Does this mean the DC to join is hardcoded instead of looked up with 
DNS? That would explain why the join succeeds now, but not why the 
original issue occurred.

William Edwards via samba schreef op 2022-09-07 16:03:
> Rowland Penny via samba schreef op 2022-09-07 12:57:
>> On Wed, 2022-09-07 at 12:16 +0200, William Edwards wrote:
>>> >
>>> >
>>> 
>>> Samba hasn?t logged anything to the journal and to syslog.
>>> 
>> 
>> Not even that samba has started ?
> 
> Sorry, I should've been more specific. Samba does log stuff, but
> nothing related to the join.
> 
>> 
>> I am trying to add a 4.16.4 DC to my test domain and I cannot get it 
>> to
>> stop segfaulting
>> 
>> Sep  7 10:41:10 tempdc samba[11019]: [2022/09/07 10:41:10.179673,  0]
>> ../../lib/util/fault.c:183(smb_panic_log)
>> Sep  7 10:41:10 tempdc samba[11019]:   PANIC (pid 11019): Signal 11:
>> Segmentation fault in 4.16.4-Debian
>> 
>> I need the dbgsym packages to help in debugging this, but they only
>> seem to exist for sid. While it is nice to be able to get the latest
>> Samba from backports, it would be nicer still to get all of the latest
>> Samba from backports :-)
>> 
>> Rowland
> 
> --
> With kind regards,
> 
> William Edwards
-- 
With kind regards,

William Edwards

On Wed, 2022-09-07 at 16:30 +0200, William Edwards via samba
wrote:
> I just found out about the --server parameter to `samba-tool domain 
> join`. I set it to the DNS name of one of the existing DCs, and the
> join 
> succeeded.
I said it was dns.
> 
> I'd like to make sure that I understand the option description,
> though, 
> which is:
> 
>      DC to join
> 
> Does this mean the DC to join is hardcoded instead of looked up with 
> DNS? That would explain why the join succeeds now, but not why the 
> original issue occurred.
The join is supposed to find the best DC to use during the join and it
looks like your new DC couldn't find a DC to join to. Using
'--server'
tells the join to use that DC, so the question has to be, did your
/etc/resolv.conf look like this:

search <YOUR_DNS_DOMAIN>
nameserver <AN_AD_DC_IP>

Does your new DC have a fixed IP ?
Is its IP info in /etc/hosts ?

Have you updated your new DC's /etc/resolv.conf to now use its
ipaddress as its nameserver ?

Rowland