Slave server error

Danny Mayer mayer at
Wed Feb 6 00:09:14 UTC 2002

At 10:05 AM 2/5/02, Rasmus Aaen wrote:

>No, that's not it. The master server is running fine. All zones are loaded
>and it answers queries for those zones. The path mentioned in the directory
>clause exist both on the master and slave server.
>In the mean time I think I have found the answer. Our slave server is
>located in a hosting center behind a firewall which we don't manage. They
>told me that port 53 was open, but it seems that it's only allowing udp
>traffic through. I can't axfr zones using Dig, and I can't telnet to port 53
>from the slave to the master.
>Funny error message though.....

TCP is required for a zone transfer. The message looks funny because
Unix doesn't distinguish between files and sockets.  In this case the
connect request failed, hence the message.

Have the firewall people allow TCP between the two specific IP addresses of
the machines so that a zone transfer can take place.


More information about the bind-users mailing list