Re: Unable to transfer IPv4 reverse zone

2013-12-21 Thread Barry Margolin
In article , 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. > > > >Interesting

Re: Unable to transfer IPv4 reverse zone

2013-12-21 Thread Daniel Lintott
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. >> >> Interestin

Re: Unable to transfer IPv4 reverse zone

2013-12-21 Thread Matus UHLAR - fantomas
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 replies

Re: Unable to transfer IPv4 reverse zone

2013-12-21 Thread Daniel Lintott
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 > > This will log everything to stderr. > I have pasted the output from running named as above here: http://pastebin.com/Fp

Re: Unable to transfer IPv4 reverse zone

2013-12-20 Thread Mark Andrews
I think this has got to the point of running named in the foreground with debugging on the master. named -g -d 100 This will log everything to stderr. -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org

Re: Unable to transfer IPv4 reverse zone

2013-12-20 Thread Daniel Lintott
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 [root@

Re: Unable to transfer IPv4 reverse zone

2013-12-20 Thread Cathy Almond
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 https://lists.isc.org/mailman/listinfo/bind-us

Re: Unable to transfer IPv4 reverse zone

2013-12-20 Thread Daniel Lintott
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 "/va

Re: Unable to transfer IPv4 reverse zone

2013-12-20 Thread Matus UHLAR - fantomas
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;

Re: Unable to transfer IPv4 reverse zone

2013-12-20 Thread Daniel Lintott
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 ser

Re: Unable to transfer IPv4 reverse zone

2013-12-20 Thread Matus UHLAR - fantomas
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 192

Re: Unable to transfer IPv4 reverse zone

2013-12-20 Thread Daniel Lintott
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 othe

Re: Unable to transfer IPv4 reverse zone

2013-12-20 Thread Cathy Almond
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: > >

Re: Unable to transfer IPv4 reverse zone

2013-12-19 Thread Daniel Lintott
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: logging { channel xfer { file "/

Re: Unable to transfer IPv4 reverse zone

2013-12-19 Thread Daniel Lintott
On 19/12/13 19:44, David Forrest wrote: > This is an unrouteable private zone. I slave root as you appear to do > and serve your own 5.168.192.in-addr.arpa. as I do. I don't expect it > to transfer out as it only has meaning in an internal view. > > Dave I'm not expecting the zone to transfer

Re: Unable to transfer IPv4 reverse zone

2013-12-19 Thread Daniel Lintott
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

Re: Unable to transfer IPv4 reverse zone

2013-12-19 Thread David Forrest
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 server1.internal.ser

Re: Unable to transfer IPv4 reverse zone

2013-12-19 Thread /dev/rob0
On Thu, Dec 19, 2013 at 07:27:51PM +, Daniel Lintott wrote: > 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 enabl

Re: Unable to transfer IPv4 reverse zone

2013-12-19 Thread Daniel Lintott
On 19/12/13 18:50, Matus UHLAR - fantomas wrote: > Does the master answer SOA requests for all requests correctly? It would appear so, yes: dig @192.168.5.1 5.168.192.in-addr.arpa SOA ; <<>> DiG 9.9.4-P1 <<>> @192.168.5.1 5.168.192.in-addr.arpa SOA ; (1 server found) ;; global options: +cmd ;; G

Re: Unable to transfer IPv4 reverse zone

2013-12-19 Thread Daniel Lintott
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? > DNSS

Re: Unable to transfer IPv4 reverse zone

2013-12-19 Thread Matus UHLAR - fantomas
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 SERVFAIL

Re: Unable to transfer IPv4 reverse zone

2013-12-19 Thread Timothe Litt
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 DNSSEC

Unable to transfer IPv4 reverse zone

2013-12-19 Thread Daniel Lintott
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 r