On Wednesday 15 August 2012 02:16 PM, Simon Kelley wrote: > What does dig @192.168.2.1 smtp.corp.corpdomain.com return? >
Nothing. Because that is my ISP's nameserver which has no information about my workplace's hosts. > Assuming it's NXDOMAIN, that's your problem, and it's not a new one, but > the way dnsmasq has always worked. Dnsmasq is written on the strong > assumption that all the upstream nameservers are equal, and it can > forward a query to any of them. An NXDOMAIN answer is as good as any > other, and will be returned to the original requestor: it explicitly > doesn't trigger an attempt to send the query to another nameserver, and > the order of the nameservers is not significant. > > If your 192.168.2.1 is local nameserver only handling certain domains, > you can configure dnsmasq to use it as such with the > > server=/example.com/192.168.2.1 > > style configuration on /etc/dnsmasq.conf. That's what I had been using earlier and wanted to avoid. resolvconf does have a /etc/resolvconf/interface-order file. But that won't help since I am using dnsmasq. For now I will revert back to the old method of categorizing domains (and sub-domains) to specific name servers. If the resolvconf's interface-order feature matters, you might want to look. Otherwise please close this bug report. And thank you for explaining. Ritesh -- Ritesh Raj Sarraf | http://people.debian.org/~rrs Debian - The Universal Operating System
signature.asc
Description: OpenPGP digital signature
