Hello,
I've been seeing more and more of the following errors in all of our
name servers running Bind 9.4.3-2 on CentOS 5.3 servers:
May 8 11:00:44 ns3 named[7502]: socket.c:4524: unexpected error:
May 8 11:00:44 ns3 named[7502]: 22/Invalid argument
May 8 11:00:45 ns3 named[7502]: socket.c:452
afaik, yes it's expected - for the reason that we don't yet have a smart
way across all types of database to find the most specific match without
doing multiple queries.
-david
Scott Haneda wrote:
> The DLZ users mailing list is pretty quiet, thought to ask here in
> case someone can elaborate.
>
The DLZ users mailing list is pretty quiet, thought to ask here in
case someone can elaborate.
I have MySql query logging on so I can see the queries as they come in
for testing.
dig example.com @localhost
This yields a hit to the database of
090509 5:50:56 2593 Query SELECT zone
3 matches
Mail list logo