similar to: Samba AD DC DNS issue after upgrade

Displaying 20 results from an estimated 600 matches similar to: "Samba AD DC DNS issue after upgrade"

2023 Aug 02
1
Joining a new Samba AD DC
On 01/08/2023 22:40, Mark Foley via samba wrote: > Is not being able to run 'host -t A' a show stopper here? The wiki 'host -t CNAME' > gave, as expected: > > # host -t CNAME 0d2a3ba9-4ade-45de-85c7-321ba69caee0._msdcs.hprs.local. > Host 0d2a3ba9-4ade-45de-85c7-321ba69caee0._msdcs.hprs.local. not found: 3(NXDOMAIN) > > and when trying to add with
2019 Jan 07
2
dns_tkey_gssnegotiate: TKEY is unacceptable
Call me dense, but now I am more confused. I have tried with and without quotes ... all over the place (i.e. in the smb.config and on the command line) and everything still results in errors, although not always exactly the same. Messing with the command line results in things like this: ERROR(runtime): uncaught exception - (9711, 'WERR_DNS_ERROR_RECORD_ALREADY_EXISTS')   File
2020 Jun 10
2
getting no SRV record
I am setting up a newly reloaded Ubuntu 18.04.4LTS Samba 4.12.3 domain controller with BIND9_DLZ. All has gone well until I run: root@[dchost]:~# host -t SRV _ldap._tcp.[domain].work. _ldap._tcp.[domain].work has no SRV record Then I run: root@[dchost]:~# samba-tool dns add [dchost] [domain].work _ldap._tcp SRV '[dchost].[domain].work 8080 0 100' -Uadministrator Password for
2020 Aug 25
2
problem whith samba and dnsupdate command
Hello Rowland we have a dnsmasq as a dns server and we want to use this service a dns server, now on the status of samba we see the next errors: root at domain-server2:~# /etc/init.d/samba-ad-dc status ? samba-ad-dc.service - Samba AD Daemon Loaded: loaded (/lib/systemd/system/samba-ad-dc.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2020-08-24 11:23:53 -03;
2019 Jan 02
2
AD bind DNS broken after 4.7.3 -> 4.9.2 upgrade
On Wed, 02 Jan 2019 20:09:44 +0100 Král Gergely via samba <samba at lists.samba.org> wrote: > 2018-12-31 20:50 időpontban L.P.H. van Belle via samba ezt írta: > > Can you try to upgrade to any 4.8 version then to 4.9.4? > > might work, atleast my guess this will have a better chance get > > passed this bug. > > > > I can confirm that an upgrade to 4.7.3 to
2023 Aug 01
1
Joining a new Samba AD DC
On Mon Jul 31 11:17:57 2023 Mark Foley via samba <samba at lists.samba.org> wrote: > On Jul 31 03:00:37 2023 Rowland Penny via samba <samba at lists.samba.org> wrote: > > > On 30/07/2023 22:24, Mark Foley via samba wrote: > > > That gave me: > > > > > > # host -t A 0d2a3ba9-4ade-45de-85c7-321ba69caee0._msdcs.hprs.local > > > host:
2020 Feb 27
4
New PTR records not visible
Ok, new test. Besides that i dont like the python errors shown, this still looks good. So i dont know.. See below, i can not make it error. for x in 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 ; do samba-tool dns add dc1.internal.dom.tld $x.249.10.in-addr.arpa 158 PTR host-test.extrazone.dom.tld ; done Record added successfully Record added successfully Record added successfully Record added
2018 Aug 22
1
Samba 4.8.4 + BIND 9.9.4 - possibility of nonsecure DNS updates
Hello, guys. First of all, I would like to thank you all for the time you spend with solving my problem. I appreciate that very much. Especially Rowland. You make great job every day here on lists. Louis: > ; TSIG error with server: tsig verify failure > > Mayabe update/setup your TSIG key. >
2020 Aug 24
2
problem whith samba and dnsupdate command
Problem whith dnsupdate --> /etc/samba# samba_dnsupdate --all-names --fail-immediately Failed to get Kerberos credentials, falling back to samba-tool: kinit for DOMAIN-SERVER2$@POLICIA2.RIONEGRO.GOV.AR failed (Cannot contact any KDC for requested realm) ERROR(runtime): uncaught exception - (9711, 'WERR_DNS_ERROR_RECORD_ALREADY_EXISTS') File
2015 Jan 11
2
Ghost DNS Entry (WERR_DNS_ERROR_RECORD_ALREADY_EXISTS)
Hallo, I'm using Samba 4 AD in production now for more than a half year. All works great since today. Today I was unable to access my network printer by its hostname. So I looked up his DNS Entry using the Windows DNS-Manager and recognized that the DNS entry for the printer is missing. I tried to readd it, but got the error message that the entry already exists. Next I tried to remove an
2020 Mar 22
2
new installation Samba AD - dnsupdate fail
Hello together Installing a new Samba AD on me new installed Debian 10. root at AD:/home/maurizio# /usr/sbin/smbd -V Version 4.9.5-Debian But DNS_Update will by fail: [2020/03/22 13:26:02.266719, 0] ../lib/util/util_runcmd.c:327(samba_runcmd_io_handler) /usr/sbin/samba_dnsupdate: ERROR(runtime): uncaught exception - (9711, 'WERR_DNS_ERROR_RECORD_ALREADY_EXISTS') [2020/03/22
2018 May 02
4
samba_dnsupdate --all-names -> dns_tkey_negotiategss: TKEY is unacceptable
Hi Rowland, Am 02.05.2018 um 14:27 schrieb Rowland Penny via samba: > Try adding 'dns update command = /usr/sbin/samba_dnsupdate > --use-samba-tool' to smb.conf > > and run 'samba_dnsupdate --all-names --use-samba-tool' we did this and we now getting the following error-message: ----------- . . ERROR(runtime): uncaught exception - (9711,
2019 Jan 07
1
dns_tkey_gssnegotiate: TKEY is unacceptable
Okay, because you are not wrong ... One more time before I move forward with this. The smb.conf is now: # Global parameters [global]         bind interfaces only = Yes         interfaces = lo eno1         netbios name = DC01         realm = CORP.<DOMAIN>.COM         server role = active directory domain controller         server services = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl,
2019 Jan 02
2
AD bind DNS broken after 4.7.3 -> 4.9.2 upgrade
> On 2 Jan 2019, at 22:43, Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Wed, 2 Jan 2019 19:35:04 +0000 > Rowland Penny via samba <samba at lists.samba.org> wrote: > >> On Wed, 02 Jan 2019 20:09:44 +0100 >> Král Gergely via samba <samba at lists.samba.org> wrote: >> >>> 2018-12-31 20:50 időpontban L.P.H. van Belle
2023 Jul 30
1
Joining a new Samba AD DC
On 30/07/2023 17:17, Mark Foley via samba wrote: > ERROR(runtime): uncaught exception - (9711, 'WERR_DNS_ERROR_RECORD_ALREADY_EXISTS') > File "/usr/lib64/python2.7/site-packages/samba/netcmd/__init__.py", line 176, in _run > return self.run(*args, **kwargs) > File "/usr/lib64/python2.7/site-packages/samba/netcmd/dns.py", line 940, in run >
2020 Apr 06
1
errors during samba_dnsupdate
I joined a Samba server to a Windows 2003 server. As far as I can see, replication works, but sometimes there are errors like this: ; TSIG error with server: tsig verify failure Failed nsupdate: 2 update (nsupdate): SRV _ldap._tcp.Default-First-Site- Name._sites.ForestDnsZones.domain.local server03.domain.local 389 Calling nsupdate for SRV _ldap._tcp.Default-First-Site-
2013 Sep 04
1
"Empty" DNS entry, no A record, can't delete or update
Hi, I am running Samba 4.1.0 with Bind 9.8.4 and I am struggling with an "empty" DNS entry. I used Microsofts DNS MMC to add an A record to one of my zones, later deleted this entry because I wanted to move the record to another zone. After I moved it backed the A record (and the PTR) was invisible in the MMC. nslookup still works for the IP and hostname from the PDC and other hosts
2020 Jun 03
1
Samba-4.11 AD DC dnsupdate fails
FreeBSd-12.1p5 Samab-4.11 py37-dnspython-1.16.0 python37-3.7.7 I am seeing a recurring error relating to dns updates. I ran: samba_dnsupdate --verbose I see this result: Calling samba-tool dns add -k no -P ['192.168.216.166', 'brockley.harte-lyne.ca', '_ldap._tcp.Default-First-Site-Name._sites.ForestDnsZones', 'SRV',
2020 Jun 10
2
getting no SRV record
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
2020 Feb 27
5
New PTR records not visible
Ok, we might have found something here. I created a small script, see below, easy to adapt. So, after running this i see the same problem as in : https://bugzilla.samba.org/show_bug.cgi?id=14268 If i do it manualy everything works fine. But if i "past the commands or run the script" Then i see this problem.. So im thinking here, the speed of adding is creating somekind or