Here's what happened: root@[dchost]:~# samba_dnsupdate --use-samba-tool Failed to get Kerberos credentials, falling back to samba-tool: kinit for [dchost]$@[domain].WORK failed (Cannot contact any KDC for requested realm) ERROR(runtime): uncaught exception - (9711, 'WERR_DNS_ERROR_RECORD_ALREADY_EXISTS') >>>>>>>> snipped for brevity <<<<<<<<<<<<< >>>>> all "uncaught exceptions" <<<<<<<<<<<< ? File "/usr/local/samba/lib/python3.6/site-packages/samba/netcmd/__init__.py", line 186, in _run ??? return self.run(*args, **kwargs) ? File "/usr/local/samba/lib/python3.6/site-packages/samba/netcmd/dns.py", line 945, in run ??? raise e ? File "/usr/local/samba/lib/python3.6/site-packages/samba/netcmd/dns.py", line 941, in run ??? 0, server, zone, name, add_rec_buf, None) Failed update of 29 entries (It's late where you are. More in the morning?) (Sent from home location.) Bob Wooden On 6/10/20 3:50 PM, Rowland penny via samba wrote:> samba_dnsupdate --use-samba-tool
On 10/06/2020 21:58, Bob Wooden via samba wrote:> Here's what happened: > > root@[dchost]:~# samba_dnsupdate --use-samba-tool > Failed to get Kerberos credentials, falling back to samba-tool: kinit > for [dchost]$@[domain].WORK failed (Cannot contact any KDC for > requested realm) > > ERROR(runtime): uncaught exception - (9711, > 'WERR_DNS_ERROR_RECORD_ALREADY_EXISTS') > >>>>>>>> snipped for brevity <<<<<<<<<<<<< > >>>>> all "uncaught exceptions" <<<<<<<<<<<< > ? File > "/usr/local/samba/lib/python3.6/site-packages/samba/netcmd/__init__.py", > line 186, in _run > ??? return self.run(*args, **kwargs) > ? File > "/usr/local/samba/lib/python3.6/site-packages/samba/netcmd/dns.py", > line 945, in run > ??? raise e > ? File > "/usr/local/samba/lib/python3.6/site-packages/samba/netcmd/dns.py", > line 941, in run > ??? 0, server, zone, name, add_rec_buf, None) > Failed update of 29 entries > > (It's late where you are. More in the morning?)Its not that late that I can't tell you that the record does exist and the python error above has been fixed in a later version. Try checking /etc/resolv.conf, it should be: search [domain].work nameserver <the DC's ipaddress> I seem to remember Bind9 being mentioned, is it running ? Is /etc/hosts set up correctly ? Rowland
(Sent from home location.) Bob Wooden On 6/10/20 4:16 PM, Rowland penny via samba wrote:> Try checking /etc/resolv.conf, it should be: > > search [domain].work > > nameserver <the DC's ipaddress> > > I seem to remember Bind9 being mentioned, is it running ? > > Is /etc/hosts set up correctly ? > > RowlandAnd here ya go. root@[[dchost]:~# cat /etc/hosts 127.0.0.1??? localhost 192.168.16.50??? [dchost].[domain].work??? [dchost] root@[dchost]:~# systemctl status bind9 ? bind9.service - BIND Domain Name Server ?? Loaded: loaded (/lib/systemd/system/bind9.service; enabled; vendor preset: enabled) ?? Active: *active (running)* since Wed 2020-06-10 15:20:55 CDT; 2h 57min ago ???? Docs: man:named(8) ?Main PID: 590 (named) ??? Tasks: 5 (limit: 4531) ?? CGroup: /system.slice/bind9.service ?????????? ??590 /usr/sbin/named -f -u bind root@[dchost]:~# cat /etc/resolv.conf nameserver 192.168.16.50 search [domain].work Scratching my head . . . .