[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2023-05-15 Thread carlostipton1319
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,

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2022-03-29 Thread shamita
Need for dell laptop repairing contact dell service center in thane because we have door step support for dell laptop users thane if you have problem with your laptop like motherboard issue ,screen issue ,battery issue or ram replacement we capable to resolve your issue at your place within

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2021-11-02 Thread Ahmed
ake: Entering directory '/home/Christian/binutils-gdb/cygwin-obj/gdb' CXXLD gdb.exe http://www.compilatori.com/computers/smartphones/ cp-support.o: in function `gdb_demangle(char const*, int)': http://www.acpirateradio.co.uk/services/ios15/

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: network-manager (Ubuntu Precise) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2021-10-13 Thread Steve Langasek
The Precise Pangolin has reached end of life, so this bug will not be fixed for that release ** Changed in: dnsmasq (Ubuntu Precise) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2021-07-06 Thread audrey reed
** Changed in: network-manager (Ubuntu Precise) Status: Invalid => Incomplete -- 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

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2021-03-29 Thread Colin Watson
** Changed in: network-manager (Ubuntu) Status: Fix Released => Invalid ** Changed in: network-manager (Ubuntu Precise) Status: Fix Released => Invalid ** Changed in: dnsmasq (Ubuntu) Status: Fix Released => Triaged ** Changed in: dnsmasq (Ubuntu Precise) Status: Fix

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2021-03-29 Thread a59ff5
** Changed in: network-manager (Ubuntu Precise) Status: Invalid => Fix Released ** Changed in: network-manager (Ubuntu) Status: Invalid => Fix Released ** Changed in: dnsmasq (Ubuntu Precise) Status: Triaged => Fix Released ** Changed in: dnsmasq (Ubuntu) Status:

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2020-07-05 Thread vio0au0d
** Changed in: dnsmasq (Ubuntu) Status: Triaged => New ** Changed in: dnsmasq (Ubuntu Precise) Status: Triaged => New ** Changed in: network-manager (Ubuntu) Status: Invalid => New ** Changed in: network-manager (Ubuntu Precise) Status: Invalid => New ** Changed in:

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2019-12-18 Thread James Smith
Adding the needed domain to the /etc/NetworkManager/system-connections as an argument to : dns-search= see Works for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2019-03-05 Thread SHWETA SINGH
** Description changed: 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

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2017-05-02 Thread nikhil
This breaks domain name resolution in Ubuntu 16.04, as seen in bug #1522057. tags: added: precise xenial Changed in network-manager (Ubuntu): importance: Medium → Critical Changed in dnsmasq (Ubuntu Precise): importance: Medium → Critical Changed in dnsmasq (Ubuntu): importance:

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2017-05-02 Thread sunil
another solution is to resolve 192.168.0.1 code it as server=/sample.com/192.168.0.1 which would send all dns lookups for sample.com to 192.168.0.1. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2017-05-02 Thread sunil
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

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2017-05-02 Thread sunil
** Changed in: dnsmasq (Ubuntu) Assignee: Sachin Bawoor (bawoor) => sunil (chikkalli) -- 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

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2017-05-01 Thread Sachin Bawoor
The solution would be to search non-sequentially. If the first nameserver fails to answer, then it should ask other till it gets correct nameserver. For example if the request needs to resolve private address-it first searches non sequentially and asks 8.8.8.8 nameserver initially but it can

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2017-04-25 Thread Sachin Bawoor
** Changed in: dnsmasq (Ubuntu) Assignee: Mathieu Trudel-Lapierre (cyphermox) => Sachin Bawoor (bawoor) -- 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:

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2017-02-02 Thread Wolf Rogner
Regarding #69: This does not work at all. In resolv.conf there is still nameserver 127.0.1.1 -- 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

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2017-02-02 Thread Wolf Rogner
On Yakkety there is no file /etc/NetworkManager/dnsmasq.d/strict-order. Should a touch do the trick? If so why so? -- 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

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2017-02-02 Thread Benjamin Baumer
On Xenial I've set strict-order in /etc/NetworkManager/dnsmasq.d/strict- order. After a Restart of dnsmasq I have no failed DNS Queries to our internal Domain. For me this is fine, because the first (internal) Nameserver act as forwarder. If this fails the second Nameserver can be used to resolv

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2017-01-17 Thread Mathieu Clabaut
Adding the needed domain to the /etc/NetworkManager/system-connections as an argument to : dns-search=mycorporatedomain.com Works for me. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2016-07-29 Thread Alberto Salvia Novella
This breaks domain name resolution in Ubuntu 16.04, as seen in bug #1522057. ** Tags added: precise xenial ** Changed in: network-manager (Ubuntu) Importance: Medium => Critical ** Changed in: dnsmasq (Ubuntu Precise) Importance: Medium => Critical ** Changed in: dnsmasq (Ubuntu)

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2015-12-09 Thread Seva Gluschenko
Hope, my experience might help somebody affected with this issue. I've just put the needed domain into the "Additional search domains" line of the IPv4 settings of my VPN connection, and it did the trick. -- You received this bug notification because you are a member of Ubuntu Touch seeded

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2015-07-09 Thread Thomas Hood
Christian, the workaround is to comment out the line dns=dnsmasq in /etc/NetworkManager/NetworkManager.conf. -- 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:

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2015-07-09 Thread Christian Frommeyer
I stumbled upon this Problem on 15.04. I cannot resolve company intranet hosts via VPN as my WLANs local DNS server is always faster and only knows about my local machines and internet. From a users perspective I don't care about what might be the correct setup of the DNS-Servers (I cannot

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2015-06-06 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dnsmasq in Ubuntu.

[Touch-packages] [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2015-06-05 Thread Thomas Hood
** Changed in: network-manager (Ubuntu) Status: In Progress = New -- 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