[Bug 1351237] [NEW] MAAS install breaks resolvconf
Hag K
1351237 at bugs.launchpad.net
Fri Aug 1 09:23:39 UTC 2014
Public bug reported:
Version:
Ubuntu Server 14.04 with current packages
Problem:
After installing the "maas" package, the "resolveconf" functionality stops working.
Use Case:
The MAAS machine and all other commissioned machines are virtual machines running on KVM. In order to be able to resolve the commissioned machines by their machine names from the MAAS machine itself, the MAAS machine needs to look up 127.0.0.1 (i.e. its own MAAS DNS). In addition, it also needs to look up a second DNS server for the Intranet (i.e. so it can find my internal apt-get proxy).
Workaround:
Edit the "/etc/hosts" file and add all required machine references. A bit cumbersome but it works around the problem.
Steps to reproduce:
1. Create a default Ubuntu Server 14.04 machine with one NIC, which has
a static IP address. Make sure that you specify two DNS servers of which
127.0.0.1 is the first in order. Below is an example
/etc/network/interfaces file. Note: Adjust accordingly to suit your
network.
--------------------------------
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 10.100.10.150
netmask 255.255.255.0
network 10.100.10.0
broadcast 10.100.10.255
gateway 10.100.10.1
dns-nameservers 127.0.0.1 10.2.2.1
dns-search your.company.com
--------------------------------
3. Restart the machine
4. Run "cat /etc/resolv.conf" and verify that it only shows 127.0.0.1 but not 10.2.2.1
Note: I guess this is working as designed?
5. Add the following line to the "/etc/resolvconf/resolv.conf.d/tail"
file. Note: Adjust IP accordingly to suit your network.
nameserver 10.2.2.1
6. Run "sudo resolvconf -u"
7. Run "cat /etc/resolv.conf" and verify that both DNS servers are listed
8. Ping a machine which gets resolved via the DNS server 10.2.2.1 to
verify that resolvconf works.
9. Install MAAS "sudo apt-get install maas"
10. After the MAAS installation has finished, run "cat /etc/resolv.conf"
and verify that it still shows both DNS server entries!
11. However, try to ping a machine which gets resolved via the second
DNS server (i.e. 10.2.2.1). Note that the machine does not get resolved
any more and as a result you get "ping: unknown host".
Attempted fix:
I tried to fix this problem by re-installing "resolvconf" but this didn't make any difference. Attempted steps are outlined below.
A1: Edited the /etc/hosts file and added a reference to my "apt-get" proxy server so that "apt-get" works
A2. Run
sudo apt-get remove --purge resolvconf && sudo apt-get install resolvconf
A3. Removed the previously added entry from the /etc/hosts file
A4. Added the entry to the "/etc/resolvconf/resolv.conf.d/tail" file again
A5. Restarted the machine
A6. Tried to ping a machine, which gets resolved via DNS 10.2.2.1 but it was still not resolving the machine name.
** Affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Tags: maas resolvconf
** Description changed:
Version:
Ubuntu 14.04
Problem:
After installing the "maas" package, the "resolveconf" functionality stops working.
Use Case:
The MAAS machine and all other commissioned machines are virtual machines running on KVM. In order to be able to resolve the commissioned machines by their machine names from the MAAS machine itself, the MAAS machine needs to look up 127.0.0.1 (i.e. its own MAAS DNS). In addition, it also needs to look up a second DNS server for the Intranet (i.e. so it can find my internal apt-get proxy).
Workaround:
Edit the "/etc/hosts" file and add all required machine references. A bit cumbersome but it works around the problem.
Steps to reproduce:
1. Create a default Ubuntu 14.04 machine with one NIC, which has a
static IP address. Make sure that you specify two DNS servers of which
127.0.0.1 is the first in order. Below is an example
/etc/network/interfaces file. Note: Adjust accordingly to suit your
network.
--------------------------------
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
- address 10.100.10.150
- netmask 255.255.255.0
- network 10.100.10.0
- broadcast 10.100.10.255
- gateway 10.100.10.1
- dns-nameservers 127.0.0.1 10.2.2.1
- dns-search your.company.com
+ address 10.100.10.150
+ netmask 255.255.255.0
+ network 10.100.10.0
+ broadcast 10.100.10.255
+ gateway 10.100.10.1
+ dns-nameservers 127.0.0.1 10.2.2.1
+ dns-search your.company.com
--------------------------------
3. Restart the machine
- 4. Run "cat /etc/resolv.conf" and verify that it only shows 127.0.0.1 but not 10.145.24.1
+ 4. Run "cat /etc/resolv.conf" and verify that it only shows 127.0.0.1 but not 10.2.2.1
Note: I guess this is working as designed?
5. Add the following line to the "/etc/resolvconf/resolv.conf.d/tail"
file. Note: Adjust IP accordingly to suit your network.
nameserver 10.2.2.1
6. Run "sudo resolvconf -u"
7. Run "cat /etc/resolv.conf" and verify that both DNS servers listed
8. Install MAAS "sudo apt-get install maas"
9. After the MAAS installation has finished, run "cat /etc/resolv.conf"
and verify that it still shows both entries!
10. However, try to ping a machine which gets resolved via the second
DNS server. Note that the machine does not get resolved any more and as
a result get "ping: unknown host".
Attempted fix:
I tried to fix this problem by re-installing "resolvconf" but this didn't make any difference.
A1: Edited the /etc/hosts file and added a reference to the DNS server sot that "apt-get" works since my "apt-get" is a local proxy
- A2. Run
+ A2. Run
sudo apt-get remove --purge resolvconf && sudo apt-get install resolvconf
A3. Removed the previously added entry from the /etc/hosts file
A. Tried to ping a machine which gets resolved via DNS 10.2.2.1 but it could still not resolve the machine name.
** Description changed:
Version:
Ubuntu 14.04
Problem:
After installing the "maas" package, the "resolveconf" functionality stops working.
Use Case:
The MAAS machine and all other commissioned machines are virtual machines running on KVM. In order to be able to resolve the commissioned machines by their machine names from the MAAS machine itself, the MAAS machine needs to look up 127.0.0.1 (i.e. its own MAAS DNS). In addition, it also needs to look up a second DNS server for the Intranet (i.e. so it can find my internal apt-get proxy).
Workaround:
Edit the "/etc/hosts" file and add all required machine references. A bit cumbersome but it works around the problem.
Steps to reproduce:
1. Create a default Ubuntu 14.04 machine with one NIC, which has a
static IP address. Make sure that you specify two DNS servers of which
127.0.0.1 is the first in order. Below is an example
/etc/network/interfaces file. Note: Adjust accordingly to suit your
network.
--------------------------------
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 10.100.10.150
netmask 255.255.255.0
network 10.100.10.0
broadcast 10.100.10.255
gateway 10.100.10.1
dns-nameservers 127.0.0.1 10.2.2.1
dns-search your.company.com
--------------------------------
3. Restart the machine
4. Run "cat /etc/resolv.conf" and verify that it only shows 127.0.0.1 but not 10.2.2.1
Note: I guess this is working as designed?
5. Add the following line to the "/etc/resolvconf/resolv.conf.d/tail"
file. Note: Adjust IP accordingly to suit your network.
nameserver 10.2.2.1
6. Run "sudo resolvconf -u"
- 7. Run "cat /etc/resolv.conf" and verify that both DNS servers listed
+ 7. Run "cat /etc/resolv.conf" and verify that both DNS servers are listed
8. Install MAAS "sudo apt-get install maas"
9. After the MAAS installation has finished, run "cat /etc/resolv.conf"
- and verify that it still shows both entries!
+ and verify that it still shows both DNS server entries!
10. However, try to ping a machine which gets resolved via the second
DNS server. Note that the machine does not get resolved any more and as
- a result get "ping: unknown host".
+ a result you get "ping: unknown host".
Attempted fix:
- I tried to fix this problem by re-installing "resolvconf" but this didn't make any difference.
+ I tried to fix this problem by re-installing "resolvconf" but this didn't make any difference. Attempted steps are outlined below.
A1: Edited the /etc/hosts file and added a reference to the DNS server sot that "apt-get" works since my "apt-get" is a local proxy
A2. Run
sudo apt-get remove --purge resolvconf && sudo apt-get install resolvconf
A3. Removed the previously added entry from the /etc/hosts file
A. Tried to ping a machine which gets resolved via DNS 10.2.2.1 but it could still not resolve the machine name.
** Description changed:
Version:
- Ubuntu 14.04
+ Ubuntu 14.04 with current packages
Problem:
After installing the "maas" package, the "resolveconf" functionality stops working.
Use Case:
The MAAS machine and all other commissioned machines are virtual machines running on KVM. In order to be able to resolve the commissioned machines by their machine names from the MAAS machine itself, the MAAS machine needs to look up 127.0.0.1 (i.e. its own MAAS DNS). In addition, it also needs to look up a second DNS server for the Intranet (i.e. so it can find my internal apt-get proxy).
Workaround:
Edit the "/etc/hosts" file and add all required machine references. A bit cumbersome but it works around the problem.
Steps to reproduce:
1. Create a default Ubuntu 14.04 machine with one NIC, which has a
static IP address. Make sure that you specify two DNS servers of which
127.0.0.1 is the first in order. Below is an example
/etc/network/interfaces file. Note: Adjust accordingly to suit your
network.
--------------------------------
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 10.100.10.150
netmask 255.255.255.0
network 10.100.10.0
broadcast 10.100.10.255
gateway 10.100.10.1
dns-nameservers 127.0.0.1 10.2.2.1
dns-search your.company.com
--------------------------------
3. Restart the machine
4. Run "cat /etc/resolv.conf" and verify that it only shows 127.0.0.1 but not 10.2.2.1
Note: I guess this is working as designed?
5. Add the following line to the "/etc/resolvconf/resolv.conf.d/tail"
file. Note: Adjust IP accordingly to suit your network.
nameserver 10.2.2.1
6. Run "sudo resolvconf -u"
7. Run "cat /etc/resolv.conf" and verify that both DNS servers are listed
8. Install MAAS "sudo apt-get install maas"
9. After the MAAS installation has finished, run "cat /etc/resolv.conf"
and verify that it still shows both DNS server entries!
10. However, try to ping a machine which gets resolved via the second
DNS server. Note that the machine does not get resolved any more and as
a result you get "ping: unknown host".
Attempted fix:
I tried to fix this problem by re-installing "resolvconf" but this didn't make any difference. Attempted steps are outlined below.
A1: Edited the /etc/hosts file and added a reference to the DNS server sot that "apt-get" works since my "apt-get" is a local proxy
A2. Run
sudo apt-get remove --purge resolvconf && sudo apt-get install resolvconf
A3. Removed the previously added entry from the /etc/hosts file
A. Tried to ping a machine which gets resolved via DNS 10.2.2.1 but it could still not resolve the machine name.
** Description changed:
Version:
Ubuntu 14.04 with current packages
Problem:
After installing the "maas" package, the "resolveconf" functionality stops working.
Use Case:
The MAAS machine and all other commissioned machines are virtual machines running on KVM. In order to be able to resolve the commissioned machines by their machine names from the MAAS machine itself, the MAAS machine needs to look up 127.0.0.1 (i.e. its own MAAS DNS). In addition, it also needs to look up a second DNS server for the Intranet (i.e. so it can find my internal apt-get proxy).
Workaround:
Edit the "/etc/hosts" file and add all required machine references. A bit cumbersome but it works around the problem.
Steps to reproduce:
1. Create a default Ubuntu 14.04 machine with one NIC, which has a
static IP address. Make sure that you specify two DNS servers of which
127.0.0.1 is the first in order. Below is an example
/etc/network/interfaces file. Note: Adjust accordingly to suit your
network.
--------------------------------
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 10.100.10.150
netmask 255.255.255.0
network 10.100.10.0
broadcast 10.100.10.255
gateway 10.100.10.1
dns-nameservers 127.0.0.1 10.2.2.1
dns-search your.company.com
--------------------------------
3. Restart the machine
4. Run "cat /etc/resolv.conf" and verify that it only shows 127.0.0.1 but not 10.2.2.1
Note: I guess this is working as designed?
5. Add the following line to the "/etc/resolvconf/resolv.conf.d/tail"
file. Note: Adjust IP accordingly to suit your network.
nameserver 10.2.2.1
6. Run "sudo resolvconf -u"
7. Run "cat /etc/resolv.conf" and verify that both DNS servers are listed
8. Install MAAS "sudo apt-get install maas"
9. After the MAAS installation has finished, run "cat /etc/resolv.conf"
and verify that it still shows both DNS server entries!
10. However, try to ping a machine which gets resolved via the second
DNS server. Note that the machine does not get resolved any more and as
a result you get "ping: unknown host".
Attempted fix:
I tried to fix this problem by re-installing "resolvconf" but this didn't make any difference. Attempted steps are outlined below.
A1: Edited the /etc/hosts file and added a reference to the DNS server sot that "apt-get" works since my "apt-get" is a local proxy
A2. Run
sudo apt-get remove --purge resolvconf && sudo apt-get install resolvconf
A3. Removed the previously added entry from the /etc/hosts file
- A. Tried to ping a machine which gets resolved via DNS 10.2.2.1 but it could still not resolve the machine name.
+ A4. Added the entry to the "/etc/resolvconf/resolv.conf.d/tail" file again
+ A5. Restarted the machine
+ A6. Tried to ping a machine which gets resolved via DNS 10.2.2.1 but it could still not resolve the machine name.
** Description changed:
Version:
Ubuntu 14.04 with current packages
Problem:
After installing the "maas" package, the "resolveconf" functionality stops working.
Use Case:
The MAAS machine and all other commissioned machines are virtual machines running on KVM. In order to be able to resolve the commissioned machines by their machine names from the MAAS machine itself, the MAAS machine needs to look up 127.0.0.1 (i.e. its own MAAS DNS). In addition, it also needs to look up a second DNS server for the Intranet (i.e. so it can find my internal apt-get proxy).
Workaround:
Edit the "/etc/hosts" file and add all required machine references. A bit cumbersome but it works around the problem.
Steps to reproduce:
1. Create a default Ubuntu 14.04 machine with one NIC, which has a
static IP address. Make sure that you specify two DNS servers of which
127.0.0.1 is the first in order. Below is an example
/etc/network/interfaces file. Note: Adjust accordingly to suit your
network.
--------------------------------
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 10.100.10.150
netmask 255.255.255.0
network 10.100.10.0
broadcast 10.100.10.255
gateway 10.100.10.1
dns-nameservers 127.0.0.1 10.2.2.1
dns-search your.company.com
--------------------------------
3. Restart the machine
4. Run "cat /etc/resolv.conf" and verify that it only shows 127.0.0.1 but not 10.2.2.1
Note: I guess this is working as designed?
5. Add the following line to the "/etc/resolvconf/resolv.conf.d/tail"
file. Note: Adjust IP accordingly to suit your network.
nameserver 10.2.2.1
6. Run "sudo resolvconf -u"
7. Run "cat /etc/resolv.conf" and verify that both DNS servers are listed
- 8. Install MAAS "sudo apt-get install maas"
+ 8. Ping a machine which gets resolved via the DNS server 10.2.2.1 to
+ verify that resolvconf works.
- 9. After the MAAS installation has finished, run "cat /etc/resolv.conf"
+ 9. Install MAAS "sudo apt-get install maas"
+
+ 10. After the MAAS installation has finished, run "cat /etc/resolv.conf"
and verify that it still shows both DNS server entries!
- 10. However, try to ping a machine which gets resolved via the second
+ 11. However, try to ping a machine which gets resolved via the second
DNS server. Note that the machine does not get resolved any more and as
a result you get "ping: unknown host".
Attempted fix:
I tried to fix this problem by re-installing "resolvconf" but this didn't make any difference. Attempted steps are outlined below.
A1: Edited the /etc/hosts file and added a reference to the DNS server sot that "apt-get" works since my "apt-get" is a local proxy
A2. Run
sudo apt-get remove --purge resolvconf && sudo apt-get install resolvconf
A3. Removed the previously added entry from the /etc/hosts file
A4. Added the entry to the "/etc/resolvconf/resolv.conf.d/tail" file again
A5. Restarted the machine
A6. Tried to ping a machine which gets resolved via DNS 10.2.2.1 but it could still not resolve the machine name.
** Description changed:
Version:
Ubuntu 14.04 with current packages
Problem:
After installing the "maas" package, the "resolveconf" functionality stops working.
Use Case:
The MAAS machine and all other commissioned machines are virtual machines running on KVM. In order to be able to resolve the commissioned machines by their machine names from the MAAS machine itself, the MAAS machine needs to look up 127.0.0.1 (i.e. its own MAAS DNS). In addition, it also needs to look up a second DNS server for the Intranet (i.e. so it can find my internal apt-get proxy).
Workaround:
Edit the "/etc/hosts" file and add all required machine references. A bit cumbersome but it works around the problem.
Steps to reproduce:
1. Create a default Ubuntu 14.04 machine with one NIC, which has a
static IP address. Make sure that you specify two DNS servers of which
127.0.0.1 is the first in order. Below is an example
/etc/network/interfaces file. Note: Adjust accordingly to suit your
network.
--------------------------------
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 10.100.10.150
netmask 255.255.255.0
network 10.100.10.0
broadcast 10.100.10.255
gateway 10.100.10.1
dns-nameservers 127.0.0.1 10.2.2.1
dns-search your.company.com
--------------------------------
3. Restart the machine
4. Run "cat /etc/resolv.conf" and verify that it only shows 127.0.0.1 but not 10.2.2.1
Note: I guess this is working as designed?
5. Add the following line to the "/etc/resolvconf/resolv.conf.d/tail"
file. Note: Adjust IP accordingly to suit your network.
nameserver 10.2.2.1
6. Run "sudo resolvconf -u"
7. Run "cat /etc/resolv.conf" and verify that both DNS servers are listed
8. Ping a machine which gets resolved via the DNS server 10.2.2.1 to
verify that resolvconf works.
9. Install MAAS "sudo apt-get install maas"
10. After the MAAS installation has finished, run "cat /etc/resolv.conf"
and verify that it still shows both DNS server entries!
11. However, try to ping a machine which gets resolved via the second
DNS server. Note that the machine does not get resolved any more and as
a result you get "ping: unknown host".
Attempted fix:
I tried to fix this problem by re-installing "resolvconf" but this didn't make any difference. Attempted steps are outlined below.
- A1: Edited the /etc/hosts file and added a reference to the DNS server sot that "apt-get" works since my "apt-get" is a local proxy
+ A1: Edited the /etc/hosts file and added a reference to my "apt-get" proxy server sot that "apt-get" works
A2. Run
sudo apt-get remove --purge resolvconf && sudo apt-get install resolvconf
A3. Removed the previously added entry from the /etc/hosts file
A4. Added the entry to the "/etc/resolvconf/resolv.conf.d/tail" file again
A5. Restarted the machine
A6. Tried to ping a machine which gets resolved via DNS 10.2.2.1 but it could still not resolve the machine name.
** Description changed:
Version:
- Ubuntu 14.04 with current packages
+ Ubuntu Server 14.04 with current packages
Problem:
After installing the "maas" package, the "resolveconf" functionality stops working.
Use Case:
The MAAS machine and all other commissioned machines are virtual machines running on KVM. In order to be able to resolve the commissioned machines by their machine names from the MAAS machine itself, the MAAS machine needs to look up 127.0.0.1 (i.e. its own MAAS DNS). In addition, it also needs to look up a second DNS server for the Intranet (i.e. so it can find my internal apt-get proxy).
Workaround:
Edit the "/etc/hosts" file and add all required machine references. A bit cumbersome but it works around the problem.
Steps to reproduce:
- 1. Create a default Ubuntu 14.04 machine with one NIC, which has a
- static IP address. Make sure that you specify two DNS servers of which
+ 1. Create a default Ubuntu Server 14.04 machine with one NIC, which has
+ a static IP address. Make sure that you specify two DNS servers of which
127.0.0.1 is the first in order. Below is an example
/etc/network/interfaces file. Note: Adjust accordingly to suit your
network.
--------------------------------
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 10.100.10.150
netmask 255.255.255.0
network 10.100.10.0
broadcast 10.100.10.255
gateway 10.100.10.1
dns-nameservers 127.0.0.1 10.2.2.1
dns-search your.company.com
--------------------------------
3. Restart the machine
4. Run "cat /etc/resolv.conf" and verify that it only shows 127.0.0.1 but not 10.2.2.1
Note: I guess this is working as designed?
5. Add the following line to the "/etc/resolvconf/resolv.conf.d/tail"
file. Note: Adjust IP accordingly to suit your network.
nameserver 10.2.2.1
6. Run "sudo resolvconf -u"
7. Run "cat /etc/resolv.conf" and verify that both DNS servers are listed
8. Ping a machine which gets resolved via the DNS server 10.2.2.1 to
verify that resolvconf works.
9. Install MAAS "sudo apt-get install maas"
10. After the MAAS installation has finished, run "cat /etc/resolv.conf"
and verify that it still shows both DNS server entries!
11. However, try to ping a machine which gets resolved via the second
DNS server. Note that the machine does not get resolved any more and as
a result you get "ping: unknown host".
Attempted fix:
I tried to fix this problem by re-installing "resolvconf" but this didn't make any difference. Attempted steps are outlined below.
A1: Edited the /etc/hosts file and added a reference to my "apt-get" proxy server sot that "apt-get" works
A2. Run
sudo apt-get remove --purge resolvconf && sudo apt-get install resolvconf
A3. Removed the previously added entry from the /etc/hosts file
A4. Added the entry to the "/etc/resolvconf/resolv.conf.d/tail" file again
A5. Restarted the machine
A6. Tried to ping a machine which gets resolved via DNS 10.2.2.1 but it could still not resolve the machine name.
** Description changed:
Version:
Ubuntu Server 14.04 with current packages
Problem:
After installing the "maas" package, the "resolveconf" functionality stops working.
Use Case:
The MAAS machine and all other commissioned machines are virtual machines running on KVM. In order to be able to resolve the commissioned machines by their machine names from the MAAS machine itself, the MAAS machine needs to look up 127.0.0.1 (i.e. its own MAAS DNS). In addition, it also needs to look up a second DNS server for the Intranet (i.e. so it can find my internal apt-get proxy).
Workaround:
Edit the "/etc/hosts" file and add all required machine references. A bit cumbersome but it works around the problem.
Steps to reproduce:
1. Create a default Ubuntu Server 14.04 machine with one NIC, which has
a static IP address. Make sure that you specify two DNS servers of which
127.0.0.1 is the first in order. Below is an example
/etc/network/interfaces file. Note: Adjust accordingly to suit your
network.
--------------------------------
# The loopback network interface
auto lo
iface lo inet loopback
# The primary network interface
auto eth0
iface eth0 inet static
address 10.100.10.150
netmask 255.255.255.0
network 10.100.10.0
broadcast 10.100.10.255
gateway 10.100.10.1
dns-nameservers 127.0.0.1 10.2.2.1
dns-search your.company.com
--------------------------------
3. Restart the machine
4. Run "cat /etc/resolv.conf" and verify that it only shows 127.0.0.1 but not 10.2.2.1
Note: I guess this is working as designed?
5. Add the following line to the "/etc/resolvconf/resolv.conf.d/tail"
file. Note: Adjust IP accordingly to suit your network.
nameserver 10.2.2.1
6. Run "sudo resolvconf -u"
7. Run "cat /etc/resolv.conf" and verify that both DNS servers are listed
8. Ping a machine which gets resolved via the DNS server 10.2.2.1 to
verify that resolvconf works.
9. Install MAAS "sudo apt-get install maas"
10. After the MAAS installation has finished, run "cat /etc/resolv.conf"
and verify that it still shows both DNS server entries!
11. However, try to ping a machine which gets resolved via the second
- DNS server. Note that the machine does not get resolved any more and as
- a result you get "ping: unknown host".
+ DNS server (i.e. 10.2.2.1). Note that the machine does not get resolved
+ any more and as a result you get "ping: unknown host".
Attempted fix:
I tried to fix this problem by re-installing "resolvconf" but this didn't make any difference. Attempted steps are outlined below.
- A1: Edited the /etc/hosts file and added a reference to my "apt-get" proxy server sot that "apt-get" works
+ A1: Edited the /etc/hosts file and added a reference to my "apt-get" proxy server so that "apt-get" works
A2. Run
sudo apt-get remove --purge resolvconf && sudo apt-get install resolvconf
A3. Removed the previously added entry from the /etc/hosts file
A4. Added the entry to the "/etc/resolvconf/resolv.conf.d/tail" file again
A5. Restarted the machine
- A6. Tried to ping a machine which gets resolved via DNS 10.2.2.1 but it could still not resolve the machine name.
+ A6. Tried to ping a machine, which gets resolved via DNS 10.2.2.1 but it was still not resolving the machine name.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1351237
Title:
MAAS install breaks resolvconf
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1351237/+subscriptions
More information about the Ubuntu-server-bugs
mailing list