| Table of Contents |
|---|
Disable
...
and stop firewall
...
| Code Block |
|---|
$ sudo ufw status $ sudo ufw stop $ sudo ufw disable |
Disable and
...
stop AppArmor
| Code Block |
|---|
$ sudo systemctl status apparmor
$ sudo systemctl stop apparmor
$ sudo systemctl disable apparmor |
Disable systemd-resolved
systemd-resolved is a system service in Linux that serves as a network name resolution manager. Its primary function is to provide network name resolution services to local applications running on the system. It offers several features, including caching and validating DNS/DNSSEC (Domain Name System/Domain Name System Security Extensions) stub resolution, as well as LLMNR (Link-Local Multicast Name Resolution) and MulticastDNS (mDNS) resolution and response.
When enabled in k3s installations systemd-resolved will cause issues with communication between the pods, therefore it needs to be disabled.
...
| Code Block |
|---|
sudo su -
systemctl disable systemd-resolved.service
systemctl stop systemd-resolved
reboot
sudo su -
|
Then put the following line in the [main] section of your /etc/NetworkManager/NetworkManager.confto allow a static resolver entry:
| Code Block |
|---|
dns=none |
Delete symlink /etc/resolv.conf
| Code Block |
|---|
rm /etc/resolv.conf |
Use one of these to restart networking:
| Code Block |
|---|
service network-manager restart systemctl restart NetworkManager.service |
And finally:
| Code Block |
|---|
echo "nameserver 8.8.8.8" >> /etc/resolv.conf |
Note, that using sudo will not work here, you need to switch user to root to complete.
| Infonote |
|---|
Customers should use their internal dns name server (DNS) instead of google’s 8.8.8.8, please confirm DNS IP address with customer. |
Fix for EC2 instances (mostly affects just support labs)
...
Using public server may have compliance implications and will not allow to resolve internal host names. |
“Unable to resolve host […]” after every command
If get errors like
| Code Block |
|---|
unable to resolve host adam-enterprise: Temporary failure in name resolution |
You can fix this by setting your hostname in hostnamectl if it isn’t already:
Example:
| Code Block |
|---|
hostnamectl set-hostname adam-enterprise |
...
Then adding a line with hostname pointing to your localhost IP, into your /etc/hosts file:
| Code Block |
|---|
127.0.0.1 adam-enterprise |
...
(The original line with localhost doesn’t need to be removed.)
...