[Samba] cant start bind9 after dc upgrade 4.17 > 4.18
Rowland Penny
rpenny at samba.org
Sat Jul 22 05:45:30 UTC 2023
On 21/07/2023 23:24, Fabrizio Rompani via samba wrote:
> hi all
> I have 2 DC joined to the same domain .
> both with ubuntu 20 and samba 4.17 ( MichaelTokarev repos) with Bind9 as dns.
> After Upgraded the first dc to ubuntu 22 and 4.18 I' m not able to start bind9 .
> Also the second DC has been broken DNS , and after a BIND9 restart It wont start anymore.
>
> any help?
> thanks
> rf
>
>
Your DC appears to have two ipaddress's :
Jul 21 23:49:14 dc-cloud named[637]: listening on IPv4 interface eth0,
75.119.155.151#53
Jul 21 23:49:14 dc-cloud named[637]: listening on IPv4 interface eth1,
192.168.8.1#53
Yet the failing reversezone doesn't match either:
Jul 21 23:49:14 dc-cloud named[637]: zone 1.168.192.in-addr.arpa/NONE:
has no NS records
It might be a good idea to post your smb.conf and named conf files.
Rowland
More information about the samba
mailing list