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
