MAXADDRS problem

[Kevin Darcy]

named doesn't care about MAXADDRS. That's a resolver limitation. If you
used a real lookup tool like "dig", instead of the sucky nslookup, you
wouldn't be getting those messages.

Note, however, that gethostbyname() and friends might also have the
MAXADDRS limitation.


- Kevin

nmaafa wrote:

> Hi all,
>
> My problem comes from a simple query made to a local name server :
>
> nslookup router.dom1.dom2.fr
> which give a mong other answers, the message :
> MAXADDRS exceeds ....
> MAXADDRS exceeds ....
> etc...
> MAXADDRS exceeds ....
> 10.100...., 10.100..., etc (35 IP addresses).
> the element in question is a cisco router which have 47 IP addresses.
>
> So I made a 'grep MAXADDRS /usr/include/*' and i found that this
> variable
> is the max addresses which an element in the network is supposed to have
> (in netdb.h).
>
> My question : is this limitation can overtake with some simple unknown
> option or we are obliged to recompile the named sources with MAXADDRS=50
> or higher ?
>
> thank you