similar to: Logs full of FORMERR errors.

Bind_DLZ is not loaded Which makes sence if we see the errors.. Verify if this is loaded.. I have it in named.conf.local // adding the dlopen ( Bind DLZ ) module for samba, beware, if you using bind9.9 then you need to change this manualy include "/var/lib/samba/bind-dns/named.conf"; > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at

Hi Bob, ? Ok, things are looking ok again? dpkg-reconfiure krb5.conf , doesnt do much expect installing and configuringing krb5.conf which basicly only sets the REALM.? "init administrator" will not connect to kerberos? If the DNS isnt running, its unable to resolv the servernames for the REALM. Resulting in, you not able to kinit. ? Greetz, ? Louis ? ? Van: Robert Wooden

Hi, I recently setup a CentOS 5 file server for a small LAN consisting of 15 Windows XP clients. The LAN is eventually expected to migrate to Linux, at least some of the client machines. The previous setup made by a local Windows-only computer firm was an unhealthy mix of static and dynamic IP addresses with conflicting adresses, etc. First thing I undertook was clean up this mess by setting

Rowland, To answer you first, my "example.com" registered host is a wildcat " *. example.com". Everything example.com returns my external ip address. Both bind9 and samba are running. Might add your "options" but for now, solving my problem, first. Louis, your answer in a few minutes. On Wed, Sep 30, 2020 at 8:09 AM Rowland penny via samba < samba at

Package: logcheck-database Version: 1.3.8 Severity: normal After double checking that I had the most up to date logcheck-database :-) I am seeing these lines reported. May 17 15:29:33 localhost named[1765]: error (network unreachable) resolving 'software.majix.org/A/IN': 2001:503:ba3e::2:30#53 I believe that this line was intended to match it. ^\w{3} [ :[:digit:]]{11}

Hello all, I am trying to configure a subdomain DNS server on a Cent OS 5.1 - for my lab. Brief configuration: Lab machine ---> 192.168.17.2 (should respond to DNS queries from hosts in 192.168.16.0/20 network) 1. I would also like to forward any queries outside the above network to our corporate domain (no firewalls between our 192.168.16.x network and the corporate network. The domain

There seems to be a problem with my local dns server resolving mirror.centos.org. I know something about dns but obviously not enough to figure out what might be wrong here or how to fix this in bind configs. The SERVFAIL errors below seem to be related to AAAA and MX queries for the domain. Please advise. TIA. # host mirror.centos.org 8.8.8.8 Using domain server: Name: 8.8.8.8 Address:

>> However, my 2nd DC is not that new, I restarted it many times, just >> again (samba service). No DNS records are created anywhere. >> >> If I go through the DNS console, in each and every container there is >> some entry for the 1st DC, but none for the 2nd (except on the top >> levels: FQDN and _msdcs.FQDN). >> >> Could this have to do with...

Am 10.12.2015 um 15:49 schrieb Rowland penny: > On 10/12/15 14:40, Ole Traupe wrote: >> >>>> However, my 2nd DC is not that new, I restarted it many times, just >>>> again (samba service). No DNS records are created anywhere. >>>> >>>> If I go through the DNS console, in each and every container there >>>> is some entry for the

1) samba-tool dns add dcmsc.test.inc test.inc test.inc MX 'mail.test.inc 10' 2) samba-tool dns query dcmsc.test.inc test.inc test.inc MX 3) [root at dcmsc caiman]# samba-tool dns query dcmsc.test.inc test.inc test.inc MX Password for [administrator at test.INC]: Name=, Records=1, Children=0 MX: mail.test.inc. (5) (flags=600000f0, serial=10, ttl=0) Name=_msdcs, Records=0,

Hmm.. > >>>> Could this have to do with... > >>>> a) I demoted my initial 1st DC (seized FSMO roles) and got rid of > >>>> DNS entries via this script on the wiki? > >>>> b) set up the *new* 2nd DC on the hardware of the prior 1st DC > >>>> (with the same IP address)? This can be a problem yes, depending on the order of

On 10/12/15 15:13, Ole Traupe wrote: > > > Am 10.12.2015 um 15:49 schrieb Rowland penny: >> On 10/12/15 14:40, Ole Traupe wrote: >>> >>>>> However, my 2nd DC is not that new, I restarted it many times, >>>>> just again (samba service). No DNS records are created anywhere. >>>>> >>>>> If I go through the DNS

Hi Ole, Using internal DNS samba_dnsupdate does not work correctly, at least not every time. Someone modified this samba_dnsupdate tool commenting this line: os.unlink(tmpfile) which should line 413. Doing that he was able to get files generated by samba_dnsupdate to use them as argument of nsupdate command (without -g switch and with "allow dns updates = nonsecure" in smb.conf). I

I FINALLY DID IT!!!!! After following Louis van Belle's walk-through to create a new DC, and having problems at the end, I realized there was nothing in the walk through about modifying /var/lib/samba/bind-dns/named.conf to let Samba know the Bind version so I did that and Voila! We have name resolution, can create kerberos tickets, just successfully connected a windows workstation to the

Hi, I used to upgrade/migrated samba 3.3.10 to samba 3.4.17 with LDAP backend in place, while upgrading the CentOS from 5.5 to 5.9. In place to retain the trust relationship. The users can able to login without re-authentication from existing machines. Tested 3 XPs, and 3 Win7 but it takes 5-8 mins to login compared to 1 win7 that was re-connected (disconnected from domain, restart, then rejoin

On 10/12/15 14:40, Ole Traupe wrote: > >>> However, my 2nd DC is not that new, I restarted it many times, just >>> again (samba service). No DNS records are created anywhere. >>> >>> If I go through the DNS console, in each and every container there >>> is some entry for the 1st DC, but none for the 2nd (except on the >>> top levels: FQDN

Hi, here are the versions: dc01: Raspberry Pi 3 Model B Rev 1.2 root at dc01:~# cat /etc/debian_version 11.8 root at dc01:~# samba -V Version 4.17.12-Debian root at dc01:~# uname -a Linux dc01 6.1.21-v8+ #1642 SMP PREEMPT Mon Apr 3 17:24:16 BST 2023 aarch64 GNU/Linux Dc02: Raspberry Pi 3 Model B Rev 1.2 root at dc02:~# cat /etc/debian_version 11.8 root at dc02:~# samba -V Version

I just found the /etc/hosts thing two seconds before reading your email. A couple of questions: 1) The install also did nothing to krb5.conf - do I need to merge it with the file that the install generated? 2) When adding a DC to this domain, do I follow the same walk-through but just use samba-tool domain join instead of domain provision? 3) What tests should I run? I can join a computer to the

I joined a Fedora Linux box running Samba 4.1.5 to a Windows Server 2000 domain controller as an additional domain controller with the command: samba-tool domain join adi.com DC -Uadministrator --realm=adi.com --dns-backend=BIND9_DLZ The messages indicated that this was mostly sucessfull with the exception of the message: NO DNS zone information found in source domain, not replicating DNS

On Tue, 2 Jan 2018 15:11:59 +0000 Kristján Valur Jónsson <kristjan at rvx.is> wrote: > Here are log files from my two DCs that are set up in redundant DHCP > mode. One of them is running with the -v flag in dhcp-dyndns, hence > is much more verbose. > dc02 is the primary, dc03 is secondary > log_dc02, log_dc03, show a failed dyndns session from Fridriks_iphone. > >