zone xfers alternate port again
barmar at bbnplanet.com
Thu Nov 4 15:15:48 UTC 1999
In article <Pine.LNX.4.10.9911031448200.3115-100000 at ann.ied.com>,
Jan Vicherek <honza at ied.com> wrote:
> SUGGESTION for solution: This is my suggestion as to how to solve the
>problem using an enhancement to the bind software. It requires that both
>SECONDARY (slave) and PRIMARY (master) have this enhancement installed.
> In short: ``Add a "port" option to the "allow-transfer" statement for
>both "master" and "slave" zone types. Then the master listens on this port
>to allow zone xfer and the slave initiates request for zone xfer to this
You can use the "listen-on" option to specify the port that named listens
on for both queries and zone transfers.
Since you presumably want to listen on the normal port 53 for normal
queries, what you could do is run *two* named processes. Their named.boot
files would be identical except for the "listen-on" option; one would
listen on port 53, while the other would listen on the port that can get
through the firewall; it would exist just to serve these zone transfers.
Barry Margolin, barmar at bbnplanet.com
GTE Internetworking, Powered by BBN, Burlington, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.
More information about the bind-users