similar to: [samba_upgradedns] Error parsing DNS data

Hello, I am trying to change over from bind9 to internal dns. For some reason I keep getting the following error: Error parsing DNS data from '/opt/samba/private/dns/TH01.INET.zone' () I have inspected TH01.INET.ZONE but I could not find an error. I do not understand this error message. I am hoping someone could help me with this issue please. Your help will be very much appreciated.

Hello all, I managed to install an extra DC. The first DC is comsrv01a with ip 192.168.0.200. I run Samba 4.1.9 and BIND 9.8.1-P1. The new DC is srv01ham with ip 172.16.32.222. I use the internal DNS. I run Samba 4.1.9. I use a permanent LAN-2-LAN VPN via my Draytek routers. The first DC (comsrv01a, 192.168.0.200) is my primary DNS server. This is configured in all my routers and DHCP servers.

Hello, First of all I would like to thank the Samba Project Group for this state of the art software. I would like to thank every body for helping each other out. Please ignore my poor English writing. It is not my native language. Although: I do the best I can. We use Samba for a while now. We started with version 4.0.6 and updated each time. Now we are at version 4.0.9 and we are planning to

​Hello Andrew, Thank you for your reply (very much appreciated). > I take it you are trying to move from the flatfile based bind to internal. That is correct > The samba_upgradedns script is pretty simple, and uses the > dnspython library to read zone files. It certainly could be > the case that it just can't read the zone file after bind9 > has been doing dynamic updates

Hi all, I got some issues with adding DNS records. I still use BIND9_FLATFILE on my first DC. Maybe this is the problem? What I would like to try is to change from BIND9_FLATFILE to BIND9_DLZ. I change the backend from BIND9_FLATFILE to BIND9_DLZ twice (in the past or other servers) but I don't remember how I did this anymore! What I did try is the following... and that didn't work. I

Hello, I have a question regarding to access permissions. Recently I have upgraded my DC from version 41.12 to 4.1.21. This weekend I have decided to upgrade to 4.3.3. I have noticed that my users weren't able to access the sysvol share after the upgraded to 4.3.3. As a test I have created a new user "test" and I was able to open the sysvol share without any issues. Next I have

Dear all, I have a few question regarding to DNS and upgrading from Samba 4.1.17 to 4.4.2. After reading about the Badlock Bug, I feel the urge to upgrade my Samba installation and to move from BIND9_FLATFILE to SAMBA_INTERNAL_DNS. I am using Samba version 4.1.17. During provisioning (some years ago) I have decided to use BIND9_FLATFILE. At this moment I would like to upgrade to Samba 4.4.2 and

Hi, I'm having the following issue when trying to switch from samba_internal to bind9_dlz. I have been following the procedure here: https://wiki.samba.org/index.php/Changing_the_DNS_backend#Changing_from_Samba_Internal_DNS_to_BIND_DLZ I get the following: [root at dc2 ~]# /usr/local/sbin/samba_upgradedns --dns-backend=BIND9_DLZ Reading domain information Segmentation fault (core dumped)

When I run: # samba_upgradedns --dns-backend=BIND9_DLZ I get the following: lpcfg_load: refreshing parameters from /etc/samba/smb.conf params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf" Reading domain information lpcfg_load: refreshing parameters from /etc/samba/smb.conf params.c:pm_process() - Processing configuration file "/etc/samba/smb.conf" DNS

Thanks a lot for your help so far. The main reason I do not use vms is that the server is pretty limited in RAM so this would only be my last resort. To prevent confusion: srv.wie (192.168.1.50) is the same machine as smb.wie (192.168.1.55), I seperated them just now to debug the problem. > These look like they are being run on the DC, what about from the > windows clients ? > I did

> > You are using Bind9 with flatfiles, this is NOT recommended. > If you are using the standard Ubuntu Bind9 package, you should be using > BIND9_DLZ and this stores the dns info in AD. > How did you provision the DC, was it with 'BIND9_FLATFILE' or > 'BIND9_DLZ' ? > If it was the later, just remove the 'wie' zone and its reverse zone > from the

On 05/08/2019 10:14, Patrik wrote: > I am not using flatfiles and i using BIND_DLZ it shows in my log and i > do not use flatfiles. BIND_DLZ only. Oh yes you are, you have this in your /etc/bind/named.conf.local : ??? zone "patrikx3.com" { ??????? type master; ??????? file "/etc/bind/zones/enp1s0f3/patrikx3.com"; ??????? include

Hello, I'm moving my mail server from Exchange to an opensource one. After a bunch of reading, I decided on building a Dovecot2 + Postfix server in a VirtualUsers-only + Multiple-domains configuration. Since my messages will be stored by Dovecot, and the documentation is really good, I figured that it's smartest to configure Dovecot, then make Postfix 'fit' to it, sharing the

Hi at all, i´am using samba 4.3.4 as "ad", "migrated by classicupgrade" some time ago from an nt4-domain. By trying samba_upgradedns --dns-backend=BIND9_DLZ i get the following error: Traceback (most recent call last): File "/usr/sbin/samba_upgradedns", line 262, in <module> paths, lp.configfile, lp) File

Hai Cameron, If you run: named -V Does that version match with the setting in : For example "/var/lib/samba/private/named.conf"; I'm running debian so change the path above to your file. # # This configures dynamically loadable zones (DLZ) from AD schema # Uncomment only single database line, depending on your BIND version # dlz "AD DNS Zone" { # For BIND

On 02/02/16 11:26, Markus Dellermann wrote: > Am Dienstag, 2. Februar 2016, 09:51:03 CET schrieb Rowland penny: >> On 01/02/16 22:24, Markus Dellermann wrote: >>> Hi at all, >>> >>> i´am using samba 4.3.4 as "ad", "migrated by classicupgrade" some time ago >>> from an nt4-domain. >>> >>> By trying >>>

Hello Together Please i have here a little company with any exisiting internal DNS Server "BIND 9.11.5-P4-5.1-Debian (Extended Support Version) <id:998753c>" Today i compilled the release Samba 4.10.7 successfully on any new machine here..... i read on Samba org the following News. - Do not use the BIND9_FLATFILE DNS back end. It is not supported and will be removed

On Thu, 1 Sep 2016 13:31:57 +0100 Cameron Murdoch via samba <samba at lists.samba.org> wrote: > On 1 September 2016 at 13:15, Rowland Penny via samba > <samba at lists.samba.org > > wrote: > > > On Thu, 1 Sep 2016 12:24:38 +0100 > > Cameron Murdoch via samba <samba at lists.samba.org> wrote: > > > > > Hi, > > > > > >

On 2 September 2016 at 09:53, Rowland Penny via samba <samba at lists.samba.org > wrote: > On Thu, 1 Sep 2016 14:12:21 +0100 > Rowland Penny via samba <samba at lists.samba.org> wrote: > > > > > Trying to understand why you are getting the segfault, I set up freebsd > 11.0rc2 in a VM and then installed samba44, I now know where Gentoo > gets its ideas from

On Fri, 2016-09-02 at 13:19 +0100, Rowland Penny via samba wrote: >  > > I have now found out why you had to provision with samba43, > the '--use-ntvfs' option is gone from Samba 4.4.x. I never noticed > because, as I said, I never used it. > This does of course mean that you cannot use the latest versions of > Samba as an AD DC with freebsd unless somehow either