named can certainly listen on ports other than 53, but your resolver
library probably doesn't have any way to be configured to use a non-53 port.
If you _really_ want to do this, then perhaps you should get the
authoritative nameserver to listen on a port other than 53, and put some
sort of port translator in front of it. Then port 53 would be freed up
on your server for recursive service.
Or, why not just configure a separate virtual interface and have the two
nameserver instances listen on different *addresses* instead of ports? I
realize that may entail modifications of firewall rules, etc. but it
seems cleaner than using a port translator.
- Kevin
bsd wrote:
Hello,
Would It be possible to configure BIND to be only a recursor for local
querries on a different default port than 53?
I have an authoritative server for various zones that I have
configured using PowerDNS which is already listening on 53.
PowerDNS recursor comes as an add-on and seems to be very weak and slow.
Of course he should not try to resolve querries for local zones that
are handled by PowerDNS (ideally he should transmit these querries to
the other DNS server)…
I would like to use regular bind and keep my other server running and
resolving querries from the Internet for the zones that we are handling.
Do you have any suggestions?
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
Gregober ---> PGP ID --> 0x1BA3C2FD
bsd @at@ todoo.biz
¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯¯
P "Please consider your environmental responsibility before printing
this e-mail"
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
