samba - May 2024 - named wont start

>>>> In an ideal world, the Samba dns server (be it the internal or
>>>> Bind9) should just be responsible for the AD domain and forward
>>>> anything unknown to another dns server (which is how dns
servers
>>>> generally work).
ok, so I spun up another server and split dns out. I ran:

    systemctl stop named

    systemctl disable named

    samba_upgradedns --dns-backend=SAMBA_INTERNAL

    systemctl restart samba-ad-dc.service

nothing responds on port 53 for dns :(

Peter

On 5/1/24 17:32, Peter Carlson via samba wrote:
>
>>>>> In an ideal world, the Samba dns server (be it the internal
or
>>>>> Bind9) should just be responsible for the AD domain and
forward
>>>>> anything unknown to another dns server (which is how dns
servers
>>>>> generally work).
>
> ok, so I spun up another server and split dns out. I ran:
>
> ?? systemctl stop named
>
> ?? systemctl disable named
>
> ?? samba_upgradedns --dns-backend=SAMBA_INTERNAL
>
> ?? systemctl restart samba-ad-dc.service
>
> nothing responds on port 53 for dns :(
>
> Peter
oops I forgot to add "dns" to server services in smb.conf