similar to: samba 4.7.6-Ubuntu + ipv6 not work bind9-DLZ

Displaying 20 results from an estimated 6000 matches similar to: "samba 4.7.6-Ubuntu + ipv6 not work bind9-DLZ"

2018 Sep 10
1
samba 4.7.6-Ubuntu + ipv6 not work bind9-DLZ
Em 10-09-2018 10:43, Rowland Penny via samba escreveu: > On Mon, 10 Sep 2018 09:56:46 -0400 > spiderslack via samba <samba at lists.samba.org> wrote: > >> 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
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
0
samba 4.7.6-Ubuntu + ipv6 not work bind9-DLZ
On Mon, 10 Sep 2018 09:56:46 -0400 spiderslack via samba <samba at lists.samba.org> wrote: > 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
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-
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,
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
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
2019 Sep 15
0
Migrating Samba NT4 Domain to Samba AD
W dniu 2019-09-15 o?20:38, Rowland penny via samba pisze: > On 15/09/2019 19:08, Bart?omiej Solarz-Nies?uchowski wrote: >> W dniu 2019-09-15 o?18:32, Rowland penny via samba pisze: >>> On 15/09/2019 16:44, Bart?omiej Solarz-Nies?uchowski wrote: >>>> I have some questions: >>>> >>>> I not currently understood - bind9 connected to AD server must
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 Aug 16
0
Failing to join existing AD as DC
On 16/08/2019 14:14, Alexander Harm via samba wrote: > > > > > > 4. apt update &&?apt -t buster-backports install samba attr winbind libpam-winbind libnss-winbind libpam-krb5 krb5-config krb5-user smbclient You are missing the 'acl' package > > 5.?find /var/run/samba /var/lib/samba /var/cache/samba /var/lib/samba/private -name '*.tdb' -name
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
2017 May 11
2
Upgrading BIND DNS Backend
Hi, After upgrading to BIND9_DLZ, BIND service is properly starting. However, DNS updates are failing. When I try to force the DNS update, I get the following error. Even kinit command returns "kinit: Cannot find KDC for realm "EXZA.LOCAL" while getting initial credentials" --------------------------------------- [root at dc ~]# samba_dnsupdate --verbose --all-names IPs:
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##############
2020 Jun 10
2
getting no SRV record
Same result: root@[dchost]:~# host -t SRV _ldap._tcp.$(hostname -d) _ldap._tcp.[domain].work has no SRV record (Sent from home location.) Bob Wooden Donelson Trophy 615.885.2846 On 6/10/20 2:37 PM, Rowland penny via samba wrote: > On 10/06/2020 20:25, Bob Wooden via samba wrote: >> I am setting up a newly reloaded Ubuntu 18.04.4LTS Samba 4.12.3 >> domain controller with
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
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
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
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,