Re: Stalling slave transfers

2013-05-17 Thread Cathy Almond
On 15/05/13 15:58, Tony Finch wrote: Tom Sommer m...@tomsommer.dk wrote: That works fine, but I think I figured out the problem, it was due to the server having acquired a 2nd (autodiscovered) IPv6 address, and it was using that as transfer source. It would be very helpful if the logfile

Re: Stalling slave transfers

2013-05-15 Thread Tony Finch
Tom Sommer m...@tomsommer.dk wrote: That works fine, but I think I figured out the problem, it was due to the server having acquired a 2nd (autodiscovered) IPv6 address, and it was using that as transfer source. It would be very helpful if the logfile said the actual source IP, and not just

Re: Stalling slave transfers

2013-05-14 Thread Tom Sommer
On 5/9/13 2:19 PM, Luther, Dan wrote: Tom, What happens when you dig +tcp example.com @1.2.3.4? Specifically I'm wondering here if the slave you're having problems with is blocking TCP port 53. Such a configuration would allow you to query the master server, but not transfer to/from

Re: Stalling slave transfers

2013-05-09 Thread Cathy Almond
On 08/05/13 19:15, Tom Sommer wrote: On 5/8/13 12:25 PM, Cathy Almond wrote: On 08/05/13 08:26, Tom Sommer wrote: Hi, I have a problem with one of 3 slave servers, all set up the exact same way, with the exact same bind version and configuration. One slave has a problem transfering zones

Re: Stalling slave transfers

2013-05-09 Thread Tom Sommer
On 5/9/13 11:36 AM, Cathy Almond wrote: I don't think you solved the problem - I think you moved it (or made it happen faster...) The refresh errors indicate that the master isn't responding to your slave for some reason. That's what you'll need to investigate. I would suggest auditing the

RE: Stalling slave transfers

2013-05-09 Thread Luther, Dan
: Wednesday, May 08, 2013 1:16 PM To: Cathy Almond Cc: bind-users@lists.isc.org Subject: Re: Stalling slave transfers On 5/8/13 12:25 PM, Cathy Almond wrote: On 08/05/13 08:26, Tom Sommer wrote: Hi, I have a problem with one of 3 slave servers, all set up the exact same way, with the exact same bind

Stalling slave transfers

2013-05-08 Thread Tom Sommer
Hi, I have a problem with one of 3 slave servers, all set up the exact same way, with the exact same bind version and configuration. One slave has a problem transfering zones from the master. The logfiles are flooded with received notify for zone .. refresh in progress, refresh check queued

Re: Stalling slave transfers

2013-05-08 Thread Tom Sommer
On 5/8/13 12:25 PM, Cathy Almond wrote: On 08/05/13 08:26, Tom Sommer wrote: Hi, I have a problem with one of 3 slave servers, all set up the exact same way, with the exact same bind version and configuration. One slave has a problem transfering zones from the master. The logfiles are

Re: Stalling slave transfers

2013-05-08 Thread Tom Sommer
On 5/8/13 8:15 PM, Tom Sommer wrote: Another issue has arisen now though, the logfile is filled with lots of named[5596]: zone example.com/IN: refresh: failure trying master 1.2.3.4#53 (source 0.0.0.0#0): operation canceled and named[5596]: zone example.com/IN: refresh: retry limit for