Steven Monai
2023-May-19 02:57 UTC
[Samba] On Debian 12: nsupdate (as called from samba_dnsupdate) crashes named/bind9_dlz
Thanks for your reply. On 2023-05-18 12:29 a.m., Rowland Penny via samba wrote:> On 18/05/2023 04:31, Steven Monai via samba wrote:>> Successfully obtained Kerberos ticket to DNS/dc33.ttwo.ad.example.org >> as DC34$ > > That's one misconfiguration you probably have there, it looks like your > second DC isn't using itself as its nameserver, it appears to be still > using the first DC.To be concrete: What do you recommend should be the contents of the respective /etc/resolv.conf files in my test? Here is what I currently have: * On dc33 (IP: 10.150.10.33), /etc/resolv.conf: domain ttwo.ad.example.org search ttwo.ad.example.org nameserver 10.150.10.34 nameserver 10.150.10.33 * On dc34 (IP: 10.150.10.34), /etc/resolv.conf: domain ttwo.ad.example.org search ttwo.ad.example.org nameserver 10.150.10.33 nameserver 10.150.10.34 -- -S.M.
Rowland Penny
2023-May-19 06:24 UTC
[Samba] On Debian 12: nsupdate (as called from samba_dnsupdate) crashes named/bind9_dlz
On 19/05/2023 03:57, Steven Monai via samba wrote:> Thanks for your reply. > > On 2023-05-18 12:29 a.m., Rowland Penny via samba wrote: > >> On 18/05/2023 04:31, Steven Monai via samba wrote: > >>> Successfully obtained Kerberos ticket to DNS/dc33.ttwo.ad.example.org >>> as DC34$ >> >> That's one misconfiguration you probably have there, it looks like >> your second DC isn't using itself as its nameserver, it appears to be >> still using the first DC. > > To be concrete: What do you recommend should be the contents of the > respective /etc/resolv.conf files in my test? > > Here is what I currently have: > > * On dc33 (IP: 10.150.10.33), /etc/resolv.conf: > > domain ttwo.ad.example.org > search ttwo.ad.example.org > nameserver 10.150.10.34 > nameserver 10.150.10.33 > > > * On dc34 (IP: 10.150.10.34), /etc/resolv.conf: > > domain ttwo.ad.example.org > search ttwo.ad.example.org > nameserver 10.150.10.33 > nameserver 10.150.10.34 > > > -- > -S.M. > >In resolv.conf, 'domain' and 'search' are mutually exclusive and the last one wins, as you need 'search', I would remove the 'domain' line. As for the nameservers, I would switch them around on each DC, so that the DC used itself for the nameserver. This means: On DC33 search ttwo.ad.example.org nameserver 10.150.10.33 nameserver 10.150.10.34 ON DC34 search ttwo.ad.examole.org nameserver 10.150.10.34 nameserver 10.150.10.33 Rowland
Reasonably Related Threads
- On Debian 12: nsupdate (as called from samba_dnsupdate) crashes named/bind9_dlz
- On Debian 12: nsupdate (as called from samba_dnsupdate) crashes named/bind9_dlz
- On Debian 12: nsupdate (as called from samba_dnsupdate) crashes named/bind9_dlz
- On Debian 12: nsupdate (as called from samba_dnsupdate) crashes named/bind9_dlz
- On Debian 12: nsupdate (as called from samba_dnsupdate) crashes named/bind9_dlz