system resolver uses only three DNS-servers max, although it is possible to specify more DNS-servers in /etc/resolv.conf it is possible to fix this behaviour very fast. due to documentation man resolv.conf (quote): > .................. > > Up to MAXNS (currently 3, see <resolv.h>) name > servers may be listed, one per keyword. > .................. > we should just change the value in the line # define MAXNS 3 /* max # name servers we'll track */ in /usr/include/resolv.h file I suggest to set up seven at least. Because right now I have the situation, when I need to specify five DNS-servers on my customers' machines.
Alternatively you could run a simple DNS server on the loopback device, or on a nearby system, one that supports as many servers as you like, and simply point your resolv.conf there. Otherwise, you should probably direct your request upstream.
> Alternatively you could run a simple DNS server on > the loopback device, or on a nearby system, one that > supports as many servers as you like, and simply > point your resolv.conf there. > well, I am not always the real administrator of the customer machine. Sometimes all I can do - give some settings to my customer's machine through my DHCP-server. > Otherwise, you should probably direct your request upstream. > OK, next week I'll recompile glibc with maxns=9, check, if there are some unknown issues, and after that, if everything is OK, I'll try to post a message to the official glibc bugzilla. As I see, MS Windows can easily use up to 32 (according to documentation) DNS-servers.
(In reply to comment #2) if you aren't the admin on the system, then it's not like you can install an updated glibc which can support more servers either. on your router, you can install something like dnsmasq which (afaik) can handle many more servers. then point all your clients to that machine. it'll prob be better anyways as it'll act as a local cache for all the systems. if you really want to update MAXNS, then you can use /etc/portage/patches/ to locally increase it.
