bind 9 dans secondary servers

Kevin Darcy kcd at daimlerchrysler.com
Thu Jul 19 22:55:32 UTC 2001


Usually, "timed out" means a network problem of some sort, or the server is
not listening on TCP port 53. I doubt it has anything to do with
allow-transfer or keys.

What happens if you try a "dig trucmachinbidule.com axfr
@xxx.xxx.xxx.xxx" from the slave?


- Kevin

Francois MARTIN wrote:

> Hi,
>
> I've already read articles on the ISC's maling list but this couldn't solve
> my problem.
>
> I've got a problem with a very simple thing to do with Bind 8 but not with
> Bind 9 : that's to make a slave server to download the zone files from a
> primary server each time a change is made on the primary server.
>
> In the log files of my slave server, I've got this :
>
> named[9980]: refresh_callback: zone trucmachinbidule.com/IN: failure for
> xxx.xxx.xxx.xxx#53: timed out
>
> And I don't know if the problem comes from th keys in the named.conf or if
> it comes from somewhere else.
> I'm running Bind 9.1.2 under a Slackware 7 with kernel 2.2.19 on both
> primary and slave servers.
>
> Everything seems to be okay, the allow-transfer is set up in the named.conf
> of the master, and masters{} is set up in the named.conf on the slaves.
>
> If someone had this problem and succeded in solving it, it'd be very great
> to help me.
>
> Thanks in advance.
> François.





More information about the bind-users mailing list