Recursive Query.
Kevin Darcy
kcd at chrysler.com
Tue Aug 11 17:00:21 UTC 2009
"#53" designates *port* 53. Nothing unusual about that.
To me, this looks more like a kernel issue-- EDESTADDRREQ is what you
get if you try to send data via a UDP socket that's not connect()ed.
BIND keeps good track of what's connect()ed and what isn't; it's like
the kernel is losing the association somehow.
Without knowing what OS this is running on, or what version of BIND,
it's kind of hard to troubleshoot further than that.
- Kevin
kalpesh varyani wrote:
> thanks for your quick reply
>
> I am seen below error msg " once per 60sec" and no seen any query
> failure.
>
> general: error: internal_send: 192.168.2.222#53: Destination address
> required
> general: error: /lib/isc/unix/errno2result.c:116: unexpected
> error:
> general: error: unable to convert errno to isc_result: 217:
> Destination address required
> general: error: /lib/isc/unix/socket.c:1533: unexpected error
> :
> general: error: internal_send: 192.168.2.222#53: Destination address
> required
> general: error: /isc/unix/errno2result.c:116: unexpected
> error:
> Regards
> Hiro Lalwani
>
>
>
> On Tue, Aug 11, 2009 at 10:14 PM, donovan jeffrey j
> <donovan at beth.k12.pa.us <mailto:donovan at beth.k12.pa.us>> wrote:
>
>
> On Aug 11, 2009, at 12:39 PM, kalpesh varyani wrote:
>
>> Hi,
>>
>> I have below configuration.
>>
>> DNS server1 -- Forwarder
>>
>> DNS server2-- Authoritative
>>
>> I am seeing following errors on server1.
>>
>> ----------------------------
>> general: error: internal_send: 192.168.2.222#53: Destination
>> address required
>> general: error: /lib/isc/unix/errno2result.c:116: unexpected
>> error:
>> general: error: unable to convert errno to isc_result: 217:
>> Destination address required
>> general: error: /lib/isc/unix/socket.c:1533: unexpected error
>> :
>> general: error: internal_send: 192.168.2.222#53: Destination
>> address required
>> general: error: /isc/unix/errno2result.c:116: unexpected
>> error:
>>
>> Could any of help me, to resolve this issue.
>
> sounds like a routing or firewall issue. Although from the limited
> post " #53 " doesn't look right.
>
> -j
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
More information about the bind-users
mailing list