I have an application on a Linux box that uses reverse lookup to resolve hostnames. The problem is, I have two sets of DNS servers in my resolve.conf (4 servers total), with each set corresponding to a different range of IP's. It works fine for one range of IP's, whichever one happens to be in the first server listed, but if I try to nslookup the other range, it reports not found: 3(NXDOMAIN). If it would just try the next server in the list, it would succeed....is there a way to make it do this? The DNS servers are only authoritative for their respective ranges.
I would install dnsmasq, make it (127.0.0.1) the only nameserver, and configure it to query this or that server for this or that domain using the "server" dnsmasq.conf directive.
If there's a way to try a different server upon a NXDOMAIN from a DNS server, that would be using a local DNS server with that functionality. The Linux resolver doesn't allow it. PowerDNS can be configured to run commands for every query, so as a last resort, you could always do that.
You tell little information so it is hard to begin, but I will try...
First of all the servers you are talking about are authoritative dns servers (that provides information about zones you set up), right? If so you should set up a server in your resolv.conf that is recursive only (only resolving dns name for you, not providing information). You can install it to listen on localhost as sch said.
On the other hand if a server returns an nxdomain that means: "I know this name, I am an authoritative server for it and this name does not exists." The standard dns resolving algorithm stops here. So that is it, there is no way around this. You should set your authoritative dns servers to not to be authoritative for that name.
A response to @cstamas, just to clarify how to address the VPN issue with dnsmasq.
Let's say, your machine is on the homenetwork.test domain with IP addresses 10.1.0.0/16 and the DNS server is 10.1.0.1. That DNS server can only query the "external" domain names for the worknetwork.test domain. It is authoritative (internally) for homenetwork.test and 1.10.in-addr.arp.
Now, you connect a VPN to join the worknetwork, and you now have a new route to 10.2.0.0/16 via that interface and a new DNS server 10.2.0.1 which is authoritative for worknetwork.test and 2.10.in-addr.arpa. If you use one or the other of those name servers, you'll only be able to resolve one or the other of the worknetwork.test and homenetwork.test domains.
If you use both dns servers (and RES_ROTATE), it's not better as you'll be able sometimes to resolve one or the other.
Now, if you use
And have "nameserver 127.0.0.1" in resolv.conf, you'll use 10.2.0.1 to resolve the worknetwork.test and the 10.2.x.x IP addresses and your home DNS server for the rest.