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
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 di
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
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
e master's log.
The other two slaves are running perfectly, no errors or delays what so
ever.
Bind version 9.9.2-P2 (recently upgraded to).
Any hints would be appreciated, as I feel like I've exhausted most
options.
Thank you.
--
Tom Sommer
5 matches
Mail list logo
