"recursion no" option problem

[Kevin Darcy]

If your nameserver is *only* serving master and/or slave zones to external
nameservers, then there shouldn't be any problem with "recursion no". But if
it's also being used for lookups by your own clients, for names outside of
your master or slave zones, then you need to allow recursion for those
clients, if you want those lookups to work. On later versions of BIND, you can
use the "allow-recursion" option to control which addresses are allowed to
recurse and which are not.


- Kevin

Nuno Teixeira wrote:

> Hello to all,
>
> I add "recursion no" to the named.conf and when I restart named, my ssh2
> client cannot connect to my server, it gives the error above this message.
> When I remove this option, ssh2 works again.
>
> I read that this option used with "fetch-glue no" prevents the named of
> being spoofing.
>
> How do I resolve this problem between named and ssh2?
>
> "Remote host disconnected: Some authentication methods were successful, but
> all configured authentication methods have been exhausted and the server
> still requires additional authentication."
>
> Thanks very much,
>
> Nuno Teixeira