Re: Occasional errors from res_nsearch
Divakar Pratap Singh P wrote: Thanks for suggestion Stacey, Resolv.conf (I have replaced actual data with a,b,c,x,y,z etc) : / domain // xx // . // yy // .ericsson. // se / / nameserver // a.b.c.d / / nameserver // a.b.c.d // 1 / / nameserver // a2.b2.c2.d2 / / search // xx // . // yy // .ericsson. // zz // // yy // .ericsson. // zz // ericsson. // zz / That appears to be OK... I am aware that leading white space in this file can cause libresolv issues that are not seen by dig or nslookup. Check for those with 'cat -vet /etc/resolv.conf'. But as your sample program works some of the time I don't believe that is your issue. Here is the sample source : Run your example code while setting RES_OPTIONS environment variable, for example: $ RES_OPTIONS=debug ./res_nsearch example.com Does that help you track down your issue? Stace ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Occasional errors from res_nsearch
On 11/25/09 05:44, Divakar Pratap Singh P wrote: Hi, I am using S olaris (5.10 Sparc as well as i386 ) server to run an application (written in C language) which uses B ind library client implementation (available on Solaris box by default, version 4.9.4) . On processing consecutive lookup requests using the function res_nsearch , many of the initial requests fail, and after some time, it starts resolving the requests . Error code returned is either 1 or 2, but after some time it starts working fine with eror code 0. Nslookup command works perfectly fine, resolving all valid domains correctly. We have nis service also configured on the servers. Could that be an issue here ? Because its calling res_nsearch() directly NIS shouldn't be an issue, though the NIS domainname would be used - set by res_ninit() - if one is not provided in resolv.conf(4). You should find setting environment variable RES_OPTIONS=debug useful in seeing what the resolver is doing. For further help please provide resolv.conf, output from command when RES_OPTIONS=debug is set and preferably the C code. Stacey Marshall. Sun Microsystems. Cumulative log of replies from res_nsearch ( for domain “ google.com ” ) : - function ret val: 1 Error Msg DNS lookup failed: Response is 'No address associated with name'. Resolved IP: function ret val: 1 Error Msg DNS lookup failed: Response is 'No address associated with name'. Resolved IP: function ret val: 1 Error Msg DNS lookup failed: Response is 'No address associated with name'. Resolved IP: function ret val: 1 Error Msg DNS lookup failed: Response is 'No address associated with name'. Resolved IP: function ret val: 1 Error Msg DNS lookup failed: Response is 'No address associated with name'. Resolved IP: function ret val: 0 Error Msg Resolved IP: 74.125.67.100 function ret val: 0 Error Msg Resolved IP: 74.125.53.100 function ret val: 0 Error Msg Resolved IP: 74.125.45.100 function ret val: 0 Error Msg Resolved IP: 74.125.67.100 function ret val: 0 Error Msg Resolved IP: 74.125.53.100 function ret val: 0 Error Msg Resolved IP: 74.125.45.100 function ret val: 0 Error Msg Resolved IP: 74.125.67.100 function ret val: 0 Error Msg Resolved IP: 74.125.53.100 - Thanks in anticipation, Divakar. ___ 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
Occasional errors from res_nsearch
Hi, I am using Solaris (5.10 Sparc as well as i386) server to run an application (written in C language) which uses Bind library client implementation (available on Solaris box by default, version 4.9.4). On processing consecutive lookup requests using the function res_nsearch, many of the initial requests fail, and after some time, it starts resolving the requests. Error code returned is either 1 or 2, but after some time it starts working fine with eror code 0. Nslookup command works perfectly fine, resolving all valid domains correctly. We have nis service also configured on the servers. Could that be an issue here? Cumulative log of replies from res_nsearch (for domain google.com): - function ret val: 1 Error Msg DNS lookup failed: Response is 'No address associated with name'. Resolved IP: function ret val: 1 Error Msg DNS lookup failed: Response is 'No address associated with name'. Resolved IP: function ret val: 1 Error Msg DNS lookup failed: Response is 'No address associated with name'. Resolved IP: function ret val: 1 Error Msg DNS lookup failed: Response is 'No address associated with name'. Resolved IP: function ret val: 1 Error Msg DNS lookup failed: Response is 'No address associated with name'. Resolved IP: function ret val: 0 Error Msg Resolved IP: 74.125.67.100 function ret val: 0 Error Msg Resolved IP: 74.125.53.100 function ret val: 0 Error Msg Resolved IP: 74.125.45.100 function ret val: 0 Error Msg Resolved IP: 74.125.67.100 function ret val: 0 Error Msg Resolved IP: 74.125.53.100 function ret val: 0 Error Msg Resolved IP: 74.125.45.100 function ret val: 0 Error Msg Resolved IP: 74.125.67.100 function ret val: 0 Error Msg Resolved IP: 74.125.53.100 - Thanks in anticipation, Divakar. ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
