The solution that can be proposed is that we can search in non sequential order. if the first server fails then it should continue until it gets matched to the other nameserver.
Like, if the request needs to resolve private address then ,it first searches non sequentiall order and so it asks 8.8.8.8 nameserver initially. but in the first hit, it can resolve only public addresses. So now it contacts the other nameserver 192.168.0.1, at this time it can clearly resolve the public and private addresses. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
