when using dnsmasq, you may encounter situations where it fails to resolve private names in networks with non-equivalent nameservers. This can happen when the nameservers configured for your network do not have the necessary information to resolve the private names.
To troubleshoot this issue, you can try the following steps: Verify DNS configuration: Double-check your network's DNS configuration settings. Ensure that the nameservers specified in the configuration have the ability to resolve private names. If needed, update the DNS configuration to include appropriate nameservers. Check firewall settings: If you have a firewall in place, ensure that it is not blocking the necessary DNS traffic. Adjust the firewall rules to allow DNS queries and responses to flow smoothly between your network and the nameservers. https://home-decoration-ideas.com/what-forms-do-i-need-to-become-a-licensed-garage-door-repair-in-highland-springs/ Configure dnsmasq options: Review the configuration options for dnsmasq. Ensure that it is properly configured to use the correct nameservers for resolving private names. Check for any specific settings related to resolving private names and adjust them if necessary. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1003842 Title: dnsmasq sometimes fails to resolve private names in networks with non- equivalent nameservers Status in dnsmasq package in Ubuntu: Triaged Status in network-manager package in Ubuntu: Invalid Status in dnsmasq source package in Precise: Won't Fix Status in network-manager source package in Precise: Won't Fix Status in dnsmasq package in Debian: New Bug description: A number of reports already filed against network-manager seem to reflect this problem, but to make things very clear I am opening a new report. Where appropriate I will mark other reports as duplicates of this one. Consider a pre-Precise system with the following /etc/resolv.conf: nameserver 192.168.0.1 nameserver 8.8.8.8 The first address is the address of a nameserver on the LAN that can resolve both private and public domain names. The second address is the address of a nameserver on the Internet that can resolve only public names. This setup works fine because the GNU resolver always tries the first- listed address first. Now the administrator upgrades to Precise and instead of writing the above to resolv.conf, NetworkManager writes server=192.168.0.1 server=8.8.8.8 to /var/run/nm-dns-dnsmasq.conf and "nameserver 127.0.0.1" to resolv.conf. Resolution of private domain names is now broken because dnsmasq treats the two upstream nameservers as equals and uses the faster one, which could be 8.8.8.8. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
