similar to: [samba_upgradedns] Error parsing DNS data

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

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

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

Hello! I've got this error dns_tkey_negotiategss: TKEY is unacceptable when running samba_dnsupdate --verbose With this error dynamic entries stopped working as Type A machines that entered in the field or entry to a new DC. Already tried the step described here https://wiki.samba.org/index.php/Dns_tkey_negotiategss:_TKEY_is_unacceptable But when trying to delete the account used the

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

Il giorno mar 17 dic 2019 alle ore 17:49 Rowland penny via samba < samba at lists.samba.org> ha scritto: In the last year this has come up a few times, try reading this > > https://support.microsoft.com/en-gb/help/817470/how-to-reconfigure-an-msdcs-subdomain-to-a-forest-wide-dns-application > It looks like we need a tool to correct AD :-( > Thanks! I will read that article. Do

Hello! Output of command # 1 record dn: CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=MYDOMAIN cn: {31B2F340-016D-11D2-945F-00C04FB984F9} name: {31B2F340-016D-11D2-945F-00C04FB984F9} Referral # ref: ldap: //interno.mastersonda.com.br/CN=Configuration,DC=MYDOMAIN Referral # ref: ldap: //interno.mastersonda.com.br/DC=DomainDnsZones,DC=MYDOMAIN Referral # ref: ldap:

On 30/12/15 18:19, Carlos A. P. Cunha wrote: > Hello! > I've got this error > dns_tkey_negotiategss: TKEY is unacceptable > > when running samba_dnsupdate --verbose > > With this error dynamic entries stopped working as Type A machines > that entered in the field or entry to a new DC. > > Already tried the step described here > >

On 30/12/15 18:19, Carlos A. P. Cunha wrote: > Hello! > I've got this error > dns_tkey_negotiategss: TKEY is unacceptable > > when running samba_dnsupdate --verbose > > With this error dynamic entries stopped working as Type A machines > that entered in the field or entry to a new DC. > > Already tried the step described here > >

Hai, Ok. I did more digging, this is a link Dennis showed which might help.. https://www.itprotoday.com/windows-78/q-how-can-i-create-domaindnszones-directory-partition Now, if i go throught the mailing list and lookup everything abotu this part. > Could not find machine account in secrets database: Failed to fetch > machine account password for DOM from both secrets.ldb (Could not

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 >

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

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, Samba team! I am trying to install samba4 on FreeBSD 9.2 as a domain DC to join an existing samba4 domain controller on FreeBSD 9.2. I followed the instruction of: Samba4/HOWTO/Join a domain as a DC Everything is OK until I run the following command: root at mtm:/var/named/etc/namedb # samba-tool drs showrepl Default-First-Site-Name\MTM DSA Options: 0x00000001 DSA object GUID:

On 18.07.2016 22:48, Achim Gottinger wrote: > > > Am 18.07.2016 um 11:45 schrieb Norbert Hanke: >> On 18.07.2016 01:52, Achim Gottinger wrote: >>> >>> >>> Am 18.07.2016 um 01:02 schrieb Norbert Hanke: >>>> Hello, >>>> >>>> I'm trying to join a samba 4 DC to an already existing samba 4 DC, >>>> both with

On 18.07.2016 01:52, Achim Gottinger wrote: > > > Am 18.07.2016 um 01:02 schrieb Norbert Hanke: >> Hello, >> >> I'm trying to join a samba 4 DC to an already existing samba 4 DC, >> both with BIND9_DLZ. Samba is at version 4.4.5, bind is version >> 9.10.4-P1, all brand new. >> >> The existing DC runs fine, but the added DC refuses to update

On 15/09/2019 16:44, Bart?omiej Solarz-Nies?uchowski wrote: > >> Done with some problems: > > 1. bugs reported here: > > https://bugzilla.altlinux.org/show_bug.cgi?id=36496 > > and here > > https://bugzilla.samba.org/show_bug.cgi?id=13060 > > involved me - but and make workarounds and migration was done. > > > Basically AD samba works. > > >