On 21/12/13 01:15, Mark Andrews wrote:
I think this has got to the point of running named in the
foreground with debugging on the master.
named -g -d 100 usual arguments
This will log everything to stderr.
I have pasted the output from running named as above here:
On 21.12.13 14:00, Daniel Lintott wrote:
I have pasted the output from running named as above here:
http://pastebin.com/FprFEkyb
I had changed the zone on the master and reloaded named a couple of
times on the slave.
Interestingly even when I've stopped named and I attempt a transfer it
On 21/12/13 14:10, Matus UHLAR - fantomas wrote:
On 21.12.13 14:00, Daniel Lintott wrote:
I have pasted the output from running named as above here:
http://pastebin.com/FprFEkyb
I had changed the zone on the master and reloaded named a couple of
times on the slave.
Interestingly even when
In article mailman.1893.1387635053.20661.bind-us...@lists.isc.org,
Matus UHLAR - fantomas uh...@fantomas.sk wrote:
On 21.12.13 14:00, Daniel Lintott wrote:
I have pasted the output from running named as above here:
http://pastebin.com/FprFEkyb
I had changed the zone on the master and
On 19/12/2013 23:32, Daniel Lintott wrote:
I have now tried recreating the zone file on the master, removed and
re-added the configuration for the zone on both master and slave, yet
still I am unable to transfer the zone.
I have also added the following logging to the master server:
On 20/12/13 09:16, Cathy Almond wrote:
Noting this in the master zone:
allow-transfer {
192.168.5.2;
};
Check that the slave actually is using that source address for the TCP
transfer (which I grant would be odd to be different, if your other
zones
On 19.12.13 19:27, Daniel Lintott wrote:
The following is logged on the slave:
Dec 19 17:51:48 server2 named[7866]: transfer of
'5.168.192.in-addr.arpa/IN' from 192.168.5.1#53: connected using
192.168.5.2#47108
Dec 19 17:51:48 server2 named[7866]: transfer of
'5.168.192.in-addr.arpa/IN' from
On 20/12/13 11:12, Matus UHLAR - fantomas wrote:
On 19.12.13 19:27, Daniel Lintott wrote:
The following is logged on the slave:
Dec 19 17:51:48 server2 named[7866]: transfer of
'5.168.192.in-addr.arpa/IN' from 192.168.5.1#53: connected using
192.168.5.2#47108
Dec 19 17:51:48 server2
what's in logs on master?
On 20.12.13 11:21, Daniel Lintott wrote:
Nothing seems to be logged for any transfers on the master... even with
the following logging statement added
logging {
channel xfer {
file /var/log/named/xfer.log;
print-category yes;
On 20/12/13 11:40, Matus UHLAR - fantomas wrote:
what's in logs on master?
On 20.12.13 11:21, Daniel Lintott wrote:
Nothing seems to be logged for any transfers on the master... even with
the following logging statement added
logging {
channel xfer {
file
It might be a silly question - but have you checked how many instances
of named you have running on the master (thinking that you might not be
'talking to' the one you think you are)?
Cathy
___
Please visit
On 20/12/13 21:59, Cathy Almond wrote:
It might be a silly question - but have you checked how many instances
of named you have running on the master (thinking that you might not be
'talking to' the one you think you are)?
There appears to only be one instance, from what I can see
I think this has got to the point of running named in the
foreground with debugging on the master.
named -g -d 100 usual arguments
This will log everything to stderr.
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742
Hi,
I have two BIND DNS servers both running 9.9.4-P1.
I have configured them as master and slave, but have a strange issue.
The IPv4 reverse zone, fails to transfer to the slave.
I have tested the AXFR from the command line and this also fails with
SERVFAIL.
Out of 5 zones (3 forward, 1 IPv6
I doubt you'll get help without providing configuration data for master
and slaves and exact log and error messages.
But I'll take one blind guess. DNSSEC validation enabled and your
in-addr.arpa zones are not delegated and not in DLV?
In my configuration IPv4 Reverse zones (which are
On 19.12.13 18:11, Daniel Lintott wrote:
I have two BIND DNS servers both running 9.9.4-P1.
I have configured them as master and slave, but have a strange issue.
The IPv4 reverse zone, fails to transfer to the slave.
I have tested the AXFR from the command line and this also fails with
On 19/12/13 18:37, Timothe Litt wrote:
I doubt you'll get help without providing configuration data for
master
and slaves and exact log and error messages.
But I'll take one blind guess. DNSSEC validation enabled and your
in-addr.arpa zones are not delegated and not in DLV?
DNSSEC is
On Thu, 19 Dec 2013, Daniel Lintott wrote:
(...)
;; ANSWER SECTION:
5.168.192.in-addr.arpa. 38400 IN SOA server1.internal.serverb.co.uk.
daniel.serverb.co.uk. 1234478001 10800 3600 604800 38400
;; AUTHORITY SECTION:
5.168.192.in-addr.arpa. 38400 IN NS
On 19/12/13 19:37, /dev/rob0 wrote:
How about when the zone loaded initially? I suspect a problem in the
master zone file itself. Try named-checkzone(8) on it.
named-checkzone seems to be happy:
zone 5.168.192.in-addr.arpa/IN: loaded serial 1234478001
OK
Can you query SOA and PTR records
19 matches
Mail list logo
