[PATCH] resolver does not try other nameservers on SERVFAIL

[Bernhard Reutner-Fischer]

On 13 March 2014 11:43:05 Michel Stam <michel.uclibc at reverze.net> wrote:

> Dear mailing list,
>
> I have seen very little response on this topic; Would it be possible to 
> apply this patch to trunk?

I'm verifying the patch right now, will apply it afterwards. Will followup 
in the push.

Thanks!
>
> I would like to add that without this patch, the behaviour in uClibc 
> differs from glibc.
>
> Best regads,
>
> Michel Stam
> On 03/03/2014 11:46 AM, Michel Stam wrote:
> > Commit e1420eca7374cd8f583e9d774c890645a205aaee fixed a bug where a
> > response code should mean the next server is tried. However, it tries
> > only the next search domain, and never skips to the next server.
> >
> > In my specific situation, I was using tmdns as a DNS -> mDNS bridge to 
> resolve mDNS names. tmdns returns SERVFAIL on any domain that does not end 
> in .local.
> >
> > uClibc then tries all the search domains in /etc/resolv.conf and gives 
> up, not jumping to the next nameserver in the list (in my case the real 
> nameserver). Thus, any non-.local domain never got resolved.
> >
> > My resolv.conf;
> > domain bla.net
> > search bla.net
> > nameserver 127.0.0.1
> > nameserver 172.16.1.1
> >
> > The patch I have attached basically allows SERVFAIL to go back to the 
> case as it was before 0.9.32, except that search domains are still tried.
> >
> > Best regards,
> >
> > Michel Stam
> >
> >
> >
> >


Sent with AquaMail for Android
http://www.aqua-mail.com