similar to: DNS update when removing interface

Displaying 20 results from an estimated 6000 matches similar to: "DNS update when removing interface"

2018 Aug 22
1
Cannot find KDC for requested realm
Hi folks, this is my first time setting up samba4 as AD. Using the 'samba_dnsupdate' tool, I get the error: Failed to get Kerberos credentials, falling back to samba-tool: kinit for AD$@AD.FIRMA.ANDRICK.DE failed (Cannot find KDC for requested realm) How would I get at this error? I assume 'AD$' is some automatically generated user. I have no idea how to list the users. All I
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. >
2018 Sep 10
2
samba 4.7.6-Ubuntu + ipv6 not work bind9-DLZ
Hi, all I trying setting domain samba with bind9-DLZ. I followed the tutorial https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller, but not work. see the tests bellow ricardobarbosa at isadora:~$ bash tools/testSambaRecords.sh Host _ldap._tcp.freewaynet.corp not found: 3(NXDOMAIN) Host _kerberos._udp.freewaynet.corp not found: 3(NXDOMAIN) Host
2019 Jan 02
0
AD bind DNS broken after 4.7.3 -> 4.9.2 upgrade
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 4.8.5 works. But! After upgrading the dnsupdate did not work, giving these log messages: [2019/01/02 19:18:42.908955, 0]
2019 Jan 02
0
AD bind DNS broken after 4.7.3 -> 4.9.2 upgrade
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 via samba ezt írta: > > > Can you try to upgrade to any 4.8 version then to 4.9.4? > > > might work, atleast my
2019 Jan 02
0
AD bind DNS broken after 4.7.3 -> 4.9.2 upgrade
This bug affects only upgrade via source or via packages (louis's apt) too? On Wed, Jan 2, 2019 at 8:38 PM Viktor Trojanovic via samba < samba at lists.samba.org> wrote: > > > > 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
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
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
2020 Feb 27
0
New PTR records not visible
> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Christian Naumer via samba > Verzonden: donderdag 27 februari 2020 10:33 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] New PTR records not visible > > Hello Louis, > thanks for looking into this. Have you looked at what the original > poster shared in the
2020 Feb 27
0
New PTR records not visible
Hello Lois, thanks for looking into this. Have you looked at what the original poster shared in the bug report? https://bugzilla.samba.org/show_bug.cgi?id=14268 I don't have a big problem with this, just trying to help. Maybe the original poster can say more with regards of the problem he has with this. here are more of my details. Regards #####samba-debug-info.txt##############
2013 Oct 10
1
Question about DNS Ghost Records
I have had an IP Address Record of the name Z37 which was 192.168.2.203. Using nslookup I find it, but samba-tool queries the name and shows 0 Records? $ nslookup Z37 Server: 192.168.2.1 Address: 192.168.2.1#53 Name: Z37.calcdom.local Address: 192.168.2.203 $ samba-tool dns query localhost calcdom.local @ ALL Name=, Records=4, Children=0 SOA: serial=119, refresh=900,
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;
2020 Feb 27
0
New PTR records not visible
Yet that still does not explain why the PTR record I create for that IP does not become visible. I can create other PTR records in the same zone and they do become visible to DNS lookups. I suspect it has something to do with half-dead entries in the database that are blocking it... Thanks for looking into this, Christian On 27/02/2020 11:31, L.P.H. van Belle via samba wrote: > Ok, we might
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
2018 Aug 24
3
Samba fileserver member corrupt smb.ldb after joining 4.8.4 Samba DC
Hello, I'm trying to join a samba-fileserver to a 4.8.4 Domain Controller. Both are installed from the Debian Unstable Sources. I've setup some scripts that allows me to provision the latest samba-version for testing purposes on two VMs. The following configs where working absolutly fine when provisioning a Samba-DC version 4.7.3 and I was able to do profile roaming, but since the DC is
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
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
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 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
2023 Aug 02
1
Joining a new Samba AD DC
On Wed Aug 2 04:15:23 2023 Rowland Penny via samba <samba at lists.samba.org> wrote: > 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