Ancient history - using a port other than 53 for DNS

Barry Margolin barmar at genuity.net
Thu Mar 21 18:31:15 UTC 2002


In article <a7d1a4$447 at pub3.rc.vix.com>,
Dennis Kelly  <kellyrd at nauticom.net> wrote:
>A problem I'm having would be solved more easily if I could run 2
>instances of named on one server - one at the 53 port, and one at
>another. Clearly, this can be done, and I'm ready to set it up, but the
>reason I want to do it involves zone transfers to some old
>implementations (4.x), and I can't find out how to change the port in
>secondary lines in the named.boot file.

I don't think there's any way to specify the port number in named.boot.  I
think if you use the -p<port#> option to named, it uses that port as a
replacement for port 53 throughout its operation, although I'm not sure if
it uses it when pulling zone transfers -- that requires passing a -p option
to named-xfer, and I don't remember if it does that.  But you could give it
a try and see if it works.

But since this also changes the port that the server listens for queries
on, I suspect it's not a useful solution for you.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Woburn, 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 mailing list