| 2012-05-24 09:14:57 |
Thomas Hood |
bug |
|
|
added bug |
| 2012-05-24 09:38:37 |
Launchpad Janitor |
network-manager (Ubuntu): status |
New |
Confirmed |
|
| 2012-05-24 09:38:42 |
pdf |
bug |
|
|
added subscriber pdf |
| 2012-05-24 09:59:49 |
Thomas Hood |
summary |
Enabling dnsmasq by default breaks systems with non-equivalent upstream nameservers |
Upgrading to Precise NM with "dns=dnsmasq" breaks systems with non-equivalent upstream nameservers |
|
| 2012-05-25 12:56:26 |
Thomas Hood |
summary |
Upgrading to Precise NM with "dns=dnsmasq" breaks systems with non-equivalent upstream nameservers |
Precise NM with "dns=dnsmasq" breaks systems with non-equivalent upstream nameservers |
|
| 2012-05-25 14:06:05 |
Scott Moser |
bug |
|
|
added subscriber Scott Moser |
| 2012-05-29 14:37:44 |
Thomas Hood |
bug |
|
|
added subscriber Louis Li |
| 2012-05-29 14:52:10 |
Thomas Hood |
removed subscriber Louis Li |
|
|
|
| 2012-05-31 07:48:34 |
Thomas Hood |
bug task added |
|
dnsmasq (Ubuntu) |
|
| 2012-05-31 07:49:07 |
Thomas Hood |
bug task added |
|
resolvconf (Ubuntu) |
|
| 2012-05-31 08:00:41 |
Thomas Hood |
summary |
Precise NM with "dns=dnsmasq" breaks systems with non-equivalent upstream nameservers |
dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers |
|
| 2012-05-31 08:27:15 |
Thomas Hood |
bug task deleted |
resolvconf (Ubuntu) |
|
|
| 2012-05-31 09:58:15 |
James Page |
dnsmasq (Ubuntu): status |
New |
Confirmed |
|
| 2012-05-31 09:58:19 |
James Page |
dnsmasq (Ubuntu): importance |
Undecided |
Medium |
|
| 2012-05-31 09:58:23 |
James Page |
network-manager (Ubuntu): importance |
Undecided |
Medium |
|
| 2012-05-31 14:18:40 |
Scott Moser |
nominated for series |
|
Ubuntu Precise |
|
| 2012-05-31 14:18:40 |
Scott Moser |
bug task added |
|
dnsmasq (Ubuntu Precise) |
|
| 2012-05-31 14:18:40 |
Scott Moser |
bug task added |
|
network-manager (Ubuntu Precise) |
|
| 2012-05-31 14:18:49 |
Scott Moser |
network-manager (Ubuntu Precise): status |
New |
Confirmed |
|
| 2012-05-31 14:18:52 |
Scott Moser |
network-manager (Ubuntu Precise): importance |
Undecided |
Medium |
|
| 2012-05-31 14:18:58 |
Scott Moser |
network-manager (Ubuntu Precise): milestone |
|
ubuntu-12.04.1 |
|
| 2012-05-31 14:19:04 |
Scott Moser |
dnsmasq (Ubuntu Precise): status |
New |
Confirmed |
|
| 2012-05-31 14:19:07 |
Scott Moser |
dnsmasq (Ubuntu Precise): importance |
Undecided |
Medium |
|
| 2012-05-31 14:19:10 |
Scott Moser |
dnsmasq (Ubuntu Precise): milestone |
|
ubuntu-12.04.1 |
|
| 2012-06-06 15:39:59 |
Mathieu Trudel-Lapierre |
network-manager (Ubuntu): status |
Confirmed |
In Progress |
|
| 2012-06-06 15:40:01 |
Mathieu Trudel-Lapierre |
network-manager (Ubuntu): assignee |
|
Mathieu Trudel-Lapierre (mathieu-tl) |
|
| 2012-06-06 15:40:04 |
Mathieu Trudel-Lapierre |
network-manager (Ubuntu Precise): assignee |
|
Mathieu Trudel-Lapierre (mathieu-tl) |
|
| 2012-06-06 15:40:06 |
Mathieu Trudel-Lapierre |
network-manager (Ubuntu Precise): status |
Confirmed |
Triaged |
|
| 2012-06-12 17:24:22 |
Logan Rosen |
bug watch added |
|
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675319 |
|
| 2012-06-12 17:24:22 |
Logan Rosen |
bug task added |
|
dnsmasq (Debian) |
|
| 2012-06-12 19:09:14 |
Bug Watch Updater |
dnsmasq (Debian): status |
Unknown |
New |
|
| 2012-06-15 15:35:13 |
Damir Butmir |
bug |
|
|
added subscriber Damir Butmir |
| 2012-06-16 22:48:22 |
Jeff Licquia |
bug |
|
|
added subscriber Jeff Licquia |
| 2012-06-18 02:44:13 |
Maarten Jacobs |
bug |
|
|
added subscriber Maarten Jacobs |
| 2012-07-11 11:11:41 |
veitlhuber |
bug |
|
|
added subscriber veitlhuber |
| 2012-07-12 20:55:41 |
Stéphane Graber |
dnsmasq (Ubuntu Precise): milestone |
ubuntu-12.04.1 |
|
|
| 2012-07-15 21:05:48 |
Enrique Hernández Bello |
bug |
|
|
added subscriber Enrique Hernández Bello |
| 2012-08-26 02:06:13 |
Stéphane Graber |
network-manager (Ubuntu Precise): milestone |
ubuntu-12.04.1 |
ubuntu-12.04.2 |
|
| 2012-11-20 13:08:36 |
vloupien |
bug |
|
|
added subscriber vloupien |
| 2013-02-07 17:50:52 |
Steve Langasek |
network-manager (Ubuntu Precise): milestone |
ubuntu-12.04.2 |
ubuntu-12.04.3 |
|
| 2013-04-08 00:51:29 |
Andreas Ntaflos |
bug |
|
|
added subscriber Andreas Ntaflos |
| 2013-04-12 15:54:44 |
Joshua Anhalt |
bug |
|
|
added subscriber Joshua Anhalt |
| 2013-04-16 11:58:55 |
Ben Shum |
bug |
|
|
added subscriber Ben Shum |
| 2013-11-22 09:28:19 |
Alexey Molchanov |
bug |
|
|
added subscriber Alexey Molchanov |
| 2015-02-04 04:55:00 |
thedward |
bug |
|
|
added subscriber thedward |
| 2015-06-05 13:36:30 |
Thomas Hood |
network-manager (Ubuntu): status |
In Progress |
New |
|
| 2015-06-06 15:08:02 |
Launchpad Janitor |
network-manager (Ubuntu): status |
New |
Confirmed |
|
| 2015-07-12 22:46:33 |
Ben Shum |
removed subscriber Ben Shum |
|
|
|
| 2016-04-25 08:38:04 |
Mario Knippfeld |
bug |
|
|
added subscriber Mario Knippfeld |
| 2016-05-09 14:13:12 |
euda |
bug |
|
|
added subscriber euda |
| 2016-07-29 12:05:09 |
Alberto Salvia Novella |
tags |
|
precise xenial |
|
| 2016-07-29 12:05:21 |
Alberto Salvia Novella |
network-manager (Ubuntu): importance |
Medium |
Critical |
|
| 2016-07-29 12:05:25 |
Alberto Salvia Novella |
dnsmasq (Ubuntu Precise): importance |
Medium |
Critical |
|
| 2016-07-29 12:05:27 |
Alberto Salvia Novella |
dnsmasq (Ubuntu): importance |
Medium |
Critical |
|
| 2016-07-29 12:05:29 |
Alberto Salvia Novella |
network-manager (Ubuntu Precise): importance |
Medium |
Critical |
|
| 2016-07-29 12:07:28 |
Alberto Salvia Novella |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-07-29 12:08:44 |
Alberto Salvia Novella |
network-manager (Ubuntu): status |
Confirmed |
Invalid |
|
| 2016-07-29 12:08:49 |
Alberto Salvia Novella |
network-manager (Ubuntu Precise): status |
Triaged |
Invalid |
|
| 2016-07-29 12:08:55 |
Alberto Salvia Novella |
dnsmasq (Ubuntu): status |
Confirmed |
Triaged |
|
| 2016-07-29 12:09:00 |
Alberto Salvia Novella |
dnsmasq (Ubuntu Precise): status |
Confirmed |
Triaged |
|
| 2016-07-29 12:11:27 |
Alberto Salvia Novella |
dnsmasq (Ubuntu): assignee |
|
Mathieu Trudel-Lapierre (cyphermox) |
|
| 2016-07-29 12:11:33 |
Alberto Salvia Novella |
dnsmasq (Ubuntu Precise): assignee |
|
Mathieu Trudel-Lapierre (cyphermox) |
|
| 2016-07-29 12:23:57 |
Amit Bhardwaj |
bug |
|
|
added subscriber Amit Bhardwaj |
| 2016-12-07 00:04:08 |
kristian |
bug |
|
|
added subscriber kristian |
| 2017-02-02 16:55:00 |
Andreas Ntaflos |
removed subscriber Andreas Ntaflos |
|
|
|
| 2017-03-10 22:54:36 |
Darrell Ulm |
bug |
|
|
added subscriber Darrell Ulm |
| 2017-04-26 05:09:05 |
Sachin Bawoor |
dnsmasq (Ubuntu): assignee |
Mathieu Trudel-Lapierre (cyphermox) |
Sachin Bawoor (bawoor) |
|
| 2017-04-26 07:43:19 |
Srushti Patil |
bug |
|
|
added subscriber Srushti Patil |
| 2017-05-02 06:09:12 |
sunil |
dnsmasq (Ubuntu): assignee |
Sachin Bawoor (bawoor) |
sunil (chikkalli) |
|
| 2017-05-02 09:20:25 |
nikhil |
dnsmasq (Ubuntu): assignee |
sunil (chikkalli) |
nikhil (nikhilnikki) |
|
| 2017-05-03 14:57:32 |
Christian Ehrhardt |
bug |
|
|
added subscriber Ubuntu Server Team |
| 2017-12-11 07:05:53 |
Chen-Han Hsiao (Stanley) |
bug |
|
|
added subscriber Chen-Han Hsiao (Stanley) |
| 2019-03-05 10:41:40 |
SHWETA SINGH |
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. |
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. |
|
| 2020-07-06 01:25:52 |
vio0au0d |
dnsmasq (Ubuntu): status |
Triaged |
New |
|
| 2020-07-06 01:25:55 |
vio0au0d |
dnsmasq (Ubuntu Precise): status |
Triaged |
New |
|
| 2020-07-06 01:25:59 |
vio0au0d |
network-manager (Ubuntu): status |
Invalid |
New |
|
| 2020-07-06 01:26:03 |
vio0au0d |
network-manager (Ubuntu Precise): status |
Invalid |
New |
|
| 2020-07-06 01:26:07 |
vio0au0d |
dnsmasq (Ubuntu): assignee |
nikhil (nikhilnikki) |
|
|
| 2020-07-06 01:26:11 |
vio0au0d |
dnsmasq (Ubuntu Precise): assignee |
Mathieu Trudel-Lapierre (cyphermox) |
|
|
| 2020-07-06 01:26:17 |
vio0au0d |
network-manager (Ubuntu Precise): assignee |
Mathieu Trudel-Lapierre (cyphermox) |
|
|
| 2020-07-06 01:26:19 |
vio0au0d |
network-manager (Ubuntu): assignee |
Mathieu Trudel-Lapierre (cyphermox) |
|
|
| 2020-07-06 01:26:30 |
vio0au0d |
summary |
dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers |
SDFEEWRDSsdfdasfsdf |
|
| 2020-07-06 01:26:38 |
vio0au0d |
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. |
dfasfwerwq2323sf |
|
| 2020-07-06 01:26:43 |
vio0au0d |
tags |
precise xenial |
|
|
| 2020-07-06 01:26:52 |
vio0au0d |
information type |
Public |
Private |
|
| 2020-07-06 01:27:04 |
vio0au0d |
removed subscriber vio0au0d |
|
|
|
| 2020-07-06 01:30:55 |
vio0au0d |
removed subscriber vloupien |
|
|
|
| 2020-07-06 01:30:55 |
vio0au0d |
removed subscriber Amit Bhardwaj |
|
|
|
| 2020-07-06 01:30:55 |
vio0au0d |
removed subscriber pdf |
|
|
|
| 2020-07-06 01:30:55 |
vio0au0d |
removed subscriber Scott Moser |
|
|
|
| 2020-07-06 01:30:55 |
vio0au0d |
removed subscriber Damir Butmir |
|
|
|
| 2020-07-06 01:30:55 |
vio0au0d |
removed subscriber Jeff Licquia |
|
|
|
| 2020-07-06 01:30:55 |
vio0au0d |
removed subscriber Maarten Jacobs |
|
|
|
| 2020-07-06 01:30:55 |
vio0au0d |
removed subscriber veitlhuber |
|
|
|
| 2020-07-06 01:30:55 |
vio0au0d |
removed subscriber Enrique Hernández Bello |
|
|
|
| 2020-07-06 01:30:55 |
vio0au0d |
removed subscriber Joshua Anhalt |
|
|
|
| 2020-07-06 01:30:55 |
vio0au0d |
removed subscriber Alexey Molchanov |
|
|
|
| 2020-07-06 01:30:55 |
vio0au0d |
removed subscriber Craig G |
|
|
|
| 2020-07-06 01:30:55 |
vio0au0d |
removed subscriber Sergey Starosek |
|
|
|
| 2020-07-06 01:30:55 |
vio0au0d |
removed subscriber thedward |
|
|
|
| 2020-07-06 01:30:55 |
vio0au0d |
removed subscriber Mario Knippfeld |
|
|
|
| 2020-07-06 01:30:55 |
vio0au0d |
removed subscriber euda |
|
|
|
| 2020-07-06 01:30:55 |
vio0au0d |
removed subscriber kristian |
|
|
|
| 2020-07-06 01:30:55 |
vio0au0d |
removed subscriber Darrell Ulm |
|
|
|
| 2020-07-06 01:30:55 |
vio0au0d |
removed subscriber Srushti Patil |
|
|
|
| 2020-07-06 01:30:55 |
vio0au0d |
removed subscriber nikhil |
|
|
|
| 2020-07-06 01:30:55 |
vio0au0d |
removed subscriber Ubuntu Server |
|
|
|
| 2020-07-06 01:30:55 |
vio0au0d |
removed subscriber Chen-Han Hsiao (Stanley) |
|
|
|
| 2020-07-06 01:30:55 |
vio0au0d |
removed subscriber elad domb |
|
|
|
| 2020-07-06 12:43:00 |
Nick Moffitt |
information type |
Private |
Public |
|
| 2020-07-06 12:53:20 |
Colin Watson |
dnsmasq (Ubuntu): status |
New |
Triaged |
|
| 2020-07-06 12:53:22 |
Colin Watson |
dnsmasq (Ubuntu Precise): status |
New |
Triaged |
|
| 2020-07-06 12:53:24 |
Colin Watson |
network-manager (Ubuntu): status |
New |
Invalid |
|
| 2020-07-06 12:53:27 |
Colin Watson |
network-manager (Ubuntu Precise): status |
New |
Invalid |
|
| 2020-07-06 12:54:06 |
Colin Watson |
summary |
SDFEEWRDSsdfdasfsdf |
dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers |
|
| 2020-07-06 12:54:17 |
Colin Watson |
tags |
|
precise xenial |
|
| 2020-07-06 12:55:06 |
Colin Watson |
description |
dfasfwerwq2323sf |
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. |
|
| 2020-07-06 13:47:35 |
Svin Typorylov |
bug |
|
|
added subscriber Svin Typorylov |
| 2021-03-29 20:24:12 |
a59ff5 |
network-manager (Ubuntu Precise): status |
Invalid |
Fix Released |
|
| 2021-03-29 20:24:24 |
a59ff5 |
network-manager (Ubuntu): status |
Invalid |
Fix Released |
|
| 2021-03-29 20:24:36 |
a59ff5 |
dnsmasq (Ubuntu Precise): status |
Triaged |
Fix Released |
|
| 2021-03-29 20:24:51 |
a59ff5 |
dnsmasq (Ubuntu): status |
Triaged |
Fix Released |
|
| 2021-03-29 20:39:06 |
Colin Watson |
network-manager (Ubuntu): status |
Fix Released |
Invalid |
|
| 2021-03-29 20:39:09 |
Colin Watson |
network-manager (Ubuntu Precise): status |
Fix Released |
Invalid |
|
| 2021-03-29 20:39:11 |
Colin Watson |
dnsmasq (Ubuntu): status |
Fix Released |
Triaged |
|
| 2021-03-29 20:39:13 |
Colin Watson |
dnsmasq (Ubuntu Precise): status |
Fix Released |
Triaged |
|
| 2021-07-06 18:34:10 |
audrey reed |
network-manager (Ubuntu Precise): status |
Invalid |
Incomplete |
|
| 2021-10-14 01:03:47 |
Steve Langasek |
dnsmasq (Ubuntu Precise): status |
Triaged |
Won't Fix |
|
| 2021-10-14 01:03:55 |
Steve Langasek |
network-manager (Ubuntu Precise): status |
Incomplete |
Won't Fix |
|
