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.

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 Rowland, [Quote Bouke Henstra] 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' () [..] [Quote Rowland Penny Are you using flat files with Samba and Bind ?? If so, what you are trying to do, will not work. Rowland [..] Thank you very much for your reply. I

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

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

>>> The other option is to remove 'DC=DomainDnsZones,DC=domain,DC=com' and >>> 'DC=ForestDnsZones,DC=domain,DC=com' after the join and then run >>> 'samba_upgradedns', would this work ? >> While it seems to be safe to delete DomainDnsZones context, the ForestDnsZones >> context seems to contain the real DNS zone info: > First and

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

On 18/12/2019 11:56, shacky wrote: > Hi Rowland, > > I have been doing a bit of investigation and I 'think' we do have > a tool ;-) > If you examine 'samba_upgradedns', at the top it says this: > # Upgrade DNS provision from BIND9_FLATFILE to BIND9_DLZ or > SAMBA_INTERNAL > I think if you use it to upgrade to either BIND_DLZ or >

On 10/02/2020 16:46, Alex wrote: >>>> Could not find machine account in secrets database: Failed to fetch >>>> machine account password for DOM from both secrets.ldb (Could not find >>>> entry to match filter: '(&(flatname=DOM)(objectclass=primaryDomain))' >>>> base: 'cn=Primary Domains': No such object: dsdb_search at

Hi, This is just a report I wanted to share. Maybe someone can put it on the wiki. I created a new DC for a new site using the samba internal dns option. Later, I decided to go with bind. So I ran the command, and got this error: [root at theoden ~]# samba_upgradedns --dns-backend=BIND9_DLZ --verbose Reading domain information DNS accounts already exist No zone 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 >>>

On 2 September 2016 at 14:51, Rowland Penny via samba <samba at lists.samba.org > wrote: > > > As I said, I know very little about freebsd, but you should be aware > that Samba only supports the last three major versions i.e. at the > moment 4.2.X, 4.3.x and 4.4.x > They are supported in three ways, the oldest version (now 4.2.x) only > gets security fixes, the middle

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

Hi Rowland and al. > 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

Hi all, We've recently migrated from a separate DNS server that was dynamically updated with BIND's update-policy, using a manually generated tkey-gssapi-keytab (plus a second server functioning as an ordinary slave to the first), to BIND9_DLZ. The setup predated Samba's AD DC support and BIND's DLZ support, and was originally established because even though we needed AD, we were

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)

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, > > > > > >

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