Displaying 7 results from an estimated 7 matches for "intranator".
2017 Jan 12
0
Problems with bind9_dlz when rndc is reloaded
I've added logs (dirty and quickly):
logging {
channel "request" {
file "/var/named/named.run" size 10m;
print-time yes;
print-category yes;
severity debug;
};
category default { request; };
category security { request; };
};
Reload DNS service using systemctl once, twice, then restart Bind, reload
it using rndc and no complain about log file and
2017 Jan 12
0
Problems with bind9_dlz when rndc is reloaded
Hum... what are these logs related to GeoIP?
Perhaps this answer will be a bit rough... anyway:
MS AD is complex. Samba team did a great job to reproduce its behaviour but
MS product are not reputed to be too stable, so a work-in-progress
reproduction of such tool has few chances to be too stable.
DNS is complex by itself, especially when using Bind as backend: Bind can
do lot of things related
2017 Jan 27
2
Problems with bind9_dlz when rndc is reloaded
Hello!
After updating (only one dc) for samba 4.5.3 is occurring duplicate zone
errors, when I run rndc reload
Samba_dlz: Ignoring duplicate zone
This replied to all my dcs ...
When I run:
Samba_dnsupdate --verbose --all-names
I get the error
Update failed: NOTAUTH
....
....
Update failed: NOTAUTH
Failed nsupdate: 2
Failed update of 21 entries
Like this topic to have reference to this,
2017 Jan 12
2
Problems with bind9_dlz when rndc is reloaded
Using your log parameters, the shutting down message is not showed, but when I reload rndc a get the same effect. Everything is working fine until bond9_dlz needs to reload (and no restart) rndc. When this happens, I need to restart bind and everything works fine again.
I'm starting named with named -d 3 -u named and using /var/log/messages.
See log using your parameters:
# rndc reload
2017 Jan 12
2
Problems with bind9_dlz when rndc is reloaded
Mathias,
Thanks for your reply.
Please, try to start your bind with some debug level and run commando "rndc reload" and see the end of the log. I saw samba source code and found the destroy dns function in dlz_bind9.c and called by turture blz_bind9.c.
When dlz_bind9.c is shutting down, I get this error when I try to update dns.
update failed: NOTAUTH Failed nsupdate: 2
2003 Dec 01
0
No subject
...online.com
[194.25.134.19]) by lists.samba.org (Postfix) with ESMTP id 08BA34477
for <samba@samba.org>; Wed, 6 Jun 2001 03:29:38 -0700 (PDT)
Received: from fwd00.sul.t-online.de by mailout06.sul.t-online.de with
smtp id 157aZC-0002e1-0D; Wed, 06 Jun 2001 12:29:34 +0200
Received: from intranator.local (320058631742-0001@[62.157.82.135]) by
fmrl00.sul.t-online.com with esmtp id 157aZ1-0aFhlgC; Wed, 6 Jun 2001
12:29:23 +0200
Received: from aqua.local (aqua.local [172.16.1.1]) by intranator.local
(8.11.3/8.11.3) with ESMTP id f56ATM331516 for <samba@samba.org>; Wed,
6 Jun 2001 1...
2003 Dec 01
0
No subject
...online.com
[194.25.134.17]) by lists.samba.org (Postfix) with ESMTP id 3EDFA42FB
for <samba@samba.org>; Sat, 26 May 2001 01:45:59 -0700 (PDT)
Received: from fwd04.sul.t-online.de by mailout02.sul.t-online.de with
smtp id 153ZiW-0004ZN-02; Sat, 26 May 2001 10:46:36 +0200
Received: from intranator.local (320058631742-0001@[217.0.94.130]) by
fmrl04.sul.t-online.com with esmtp id 153ZjF-0Z40f2C; Sat, 26 May 2001
10:47:21 +0200
Received: from aqua.local (aqua.local [172.16.1.1]) by intranator.local
(8.11.3/8.11.3) with ESMTP id f4Q8kTh31286 for <samba@samba.org>; Sat,
26 May 2001...