Hostname resolution on nginx/ubuntu container (excerise 7.2, step#11)
Hi Guys,
While doing exercise 7.2, step#11, i am getting following error while updating apt repositories:
root@thirdpage:/# apt-get update Err:1 http://deb.debian.org/debian stretch InRelease Temporary failure resolving 'deb.debian.org' Err:2 http://security.debian.org/debian-security stretch/updates InRelease Temporary failure resolving 'security.debian.org'
My container's resolv.conf have following content:
root@thirdpage:/# cat /etc/resolv.conf nameserver 10.96.0.10 search default.svc.cluster.local svc.cluster.local cluster.local localdomain options ndots:5
NOTE My Host OS /etc/network/interfaces file is configured as:
baqai@lfdtru1804n01:/etc/init.d$ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto ens32 iface ens32 inet dhcp
NOTE: I am doing all these exercises on local VMs created on VMWare Workstation.
Appreciate your help..
Thanks.
Furqan Baqai
Answers
-
Hello Furqan,
Definitely a DNS issue. We do not test using VMWare though.
Having said that, you did test and found that 10.96.0.10 was the listed DNS server inside the container as I see in the /etc/resolv.conf file. This is most likely the IP address of the kubernetes service, found with kubectl get svc -o wide.
Do apt-get commands work inside the master VM? Same for the worker node? What IP address do they use for DNS?
You may want to use kubectl get pods -o wide and kubectl get svc to find that IP address. Also ensure that the coredns and calico-node pods are properly running.
Regards,
0 -
Hi Serewicz,
Thank you for your response.
Responding to your questions inline:
1. Does apt-get commands on the host work ?
Yes apt-get is working and ping to a DNS is working as well
2. Output ofkubectl get pods -o wide
:baqai@lfdtru1804n01:~$ kubectl get svc -o wide NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE SELECTOR kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 21d <none> nginx ClusterIP 10.100.147.5 <none> 443/TCP 16d io.kompose.service=nginx registry ClusterIP 10.102.89.186 <none> 5000/TCP 16d io.kompose.service=registry secondapp LoadBalancer 10.102.242.149 <pending> 80:32000/TCP 34h example=second thirdpage NodePort 10.107.220.47 <none> 80:31325/TCP 24h example=third
- Output of
kubectl get svc
:
baqai@lfdtru1804n01:~$ kubectl get svc NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE kubernetes ClusterIP 10.96.0.1 <none> 443/TCP 21d nginx ClusterIP 10.100.147.5 <none> 443/TCP 16d registry ClusterIP 10.102.89.186 <none> 5000/TCP 16d secondapp LoadBalancer 10.102.242.149 <pending> 80:32000/TCP 34h thirdpage NodePort 10.107.220.47 <none> 80:31325/TCP 24h
- Also ensure that the coredns and calico-node pods are properly running.
I checked if the pods are running by issuing commandkubectl get -n kube-system pods
and found out that the pods are seeemd to be working. Not sure if it is something to do with their configuration. Please find the relevant output
baqai@lfdtru1804n01:~$ kubectl get -n kube-system pods NAME READY STATUS RESTARTS AGE calico-node-k5tv2 2/2 Running 48 21d calico-node-zwm9z 2/2 Running 56 21d coredns-86c58d9df4-62h6j 1/1 Running 28 21d coredns-86c58d9df4-fzhk6 1/1 Running 28 21d etcd-lfdtru1804n01 1/1 Running 29 21d kube-apiserver-lfdtru1804n01 1/1 Running 31 21d kube-controller-manager-lfdtru1804n01 1/1 Running 29 21d kube-proxy-8cs5r 1/1 Running 25 21d kube-proxy-qfkcc 1/1 Running 28 21d kube-scheduler-lfdtru1804n01 1/1 Running 29 21d traefik-ingress-controller-qhv4s 1/1 Running 1 24h traefik-ingress-controller-vv8nh 1/1 Running 1 24h
Thanks in advance for your help...
Regards,
Furqan Baqai0 - Output of
-
Hi Guys,
I think i found out the issue. As i am running all labs on VMWare workstation, kubernetes core DNS services are pointing to my vmware gateway for DNS resolution which is evidently failing. Please check below logs:
baqai@lfdtru1804n01:~$ kubectl logs --namespace=kube-system coredns-86c58d9df4-62h6j .:53 2019-05-20T17:54:20.286Z [INFO] CoreDNS-1.2.6 2019-05-20T17:54:20.286Z [INFO] linux/amd64, go1.11.2, 756749c CoreDNS-1.2.6 linux/amd64, go1.11.2, 756749c [INFO] plugin/reload: Running configuration MD5 = f65c4821c8a9b7b5eb30fa4fbc167769 [ERROR] plugin/errors: 2 325794039783830212.4647384507963668824. HINFO: unreachable backend: read udp 192.168.0.163:47806->192.168.159.2:53: i/o timeout [ERROR] plugin/errors: 2 325794039783830212.4647384507963668824. HINFO: unreachable backend: read udp 192.168.0.163:49965->192.168.159.2:53: i/o timeout [ERROR] plugin/errors: 2 325794039783830212.4647384507963668824. HINFO: unreachable backend: read udp 192.168.0.163:58770->192.168.159.2:53: i/o timeout [ERROR] plugin/errors: 2 325794039783830212.4647384507963668824. HINFO: unreachable backend: read udp 192.168.0.163:37151->192.168.159.2:53: i/o timeout [ERROR] plugin/errors: 2 325794039783830212.4647384507963668824. HINFO: unreachable backend: read udp 192.168.0.163:42153->192.168.159.2:53: i/o timeout [ERROR] plugin/errors: 2 325794039783830212.4647384507963668824. HINFO: unreachable backend: read udp 192.168.0.163:46402->192.168.159.2:53: i/o timeout [ERROR] plugin/errors: 2 325794039783830212.4647384507963668824. HINFO: unreachable backend: read udp 192.168.0.163:35809->192.168.159.2:53: i/o timeout [ERROR] plugin/errors: 2 325794039783830212.4647384507963668824. HINFO: unreachable backend: read udp 192.168.0.163:40866->192.168.159.2:53: i/o timeout [ERROR] plugin/errors: 2 325794039783830212.4647384507963668824. HINFO: unreachable backend: read udp 192.168.0.163:33442->192.168.159.2:53: i/o timeout [ERROR] plugin/errors: 2 325794039783830212.4647384507963668824. HINFO: unreachable backend: read udp 192.168.0.163:54784->192.168.159.2:53: i/o timeout [ERROR] plugin/errors: 2 www.linuxfoundation.org. AAAA: unreachable backend: read udp 192.168.0.163:47129->192.168.159.2:53: i/o timeout [ERROR] plugin/errors: 2 www.linuxfoundation.org. A: unreachable backend: read udp 192.168.0.163:47656->192.168.159.2:53: i/o timeout [ERROR] plugin/errors: 2 www.linuxfoundation.org. A: unreachable backend: read udp 192.168.0.163:56256->192.168.159.2:53: i/o timeout [ERROR] plugin/errors: 2 www.linuxfoundation.org. AAAA: unreachable backend: read udp 192.168.0.163:42880->192.168.159.2:53: i/o timeout [ERROR] plugin/errors: 2 www.linuxfoundation.org. A: unreachable backend: read udp 192.168.0.163:60223->192.168.159.2:53: i/o timeout [ERROR] plugin/errors: 2 www.linuxfoundation.org. AAAA: unreachable backend: read udp 192.168.0.163:57832->192.168.159.2:53: i/o timeout [ERROR] plugin/errors: 2 www.linuxfoundation.org. A: unreachable backend: read udp 192.168.0.163:56050->192.168.159.2:53: i/o timeout [ERROR] plugin/errors: 2 www.linuxfoundation.org. AAAA: unreachable backend: read udp 192.168.0.163:33869->192.168.159.2:53: i/o timeout
Appreciate if somebody help us out to resolve this.
0 -
Hello,
Debugging DNS can definitely be a task. There are several configurations which can effect resolution, some like routing, may not actually be a DNS issue as much as an overall network issue.
I'm glad you looked at the logs, I tried to post here suggesting that but the message was blocked for some reason. From the output it looks like the UDP requests are going from 192.168.0.163:47806 to 192.168.159.2:53 with a timeout. Either the forwarding in VMWare is not properly configured, it is a routing issue, or perhaps a firewall issue.
I don't know much of anything about how VMWare sets up the network between VMs by default. In the systems we support and use like GCE and AWS this problem is typically a firewall issue. That either we have to open all ports, or as in the case with VirtualBox we need to activate every interface to use promiscuous mode so as to not drop some packets.
Regards,
0
Categories
- All Categories
- 207 LFX Mentorship
- 207 LFX Mentorship: Linux Kernel
- 735 Linux Foundation IT Professional Programs
- 339 Cloud Engineer IT Professional Program
- 167 Advanced Cloud Engineer IT Professional Program
- 66 DevOps Engineer IT Professional Program
- 132 Cloud Native Developer IT Professional Program
- 122 Express Training Courses
- 122 Express Courses - Discussion Forum
- 5.9K Training Courses
- 40 LFC110 Class Forum - Discontinued
- 66 LFC131 Class Forum
- 39 LFD102 Class Forum
- 221 LFD103 Class Forum
- 17 LFD110 Class Forum
- 33 LFD121 Class Forum
- 17 LFD133 Class Forum
- 6 LFD134 Class Forum
- 17 LFD137 Class Forum
- 70 LFD201 Class Forum
- 3 LFD210 Class Forum
- 2 LFD210-CN Class Forum
- 2 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum - Discontinued
- 1 LFD233 Class Forum
- 3 LFD237 Class Forum
- 23 LFD254 Class Forum
- 689 LFD259 Class Forum
- 109 LFD272 Class Forum
- 3 LFD272-JP クラス フォーラム
- 10 LFD273 Class Forum
- 109 LFS101 Class Forum
- LFS111 Class Forum
- 2 LFS112 Class Forum
- 1 LFS116 Class Forum
- 3 LFS118 Class Forum
- 3 LFS142 Class Forum
- 3 LFS144 Class Forum
- 3 LFS145 Class Forum
- 1 LFS146 Class Forum
- 2 LFS147 Class Forum
- 8 LFS151 Class Forum
- 1 LFS157 Class Forum
- 14 LFS158 Class Forum
- 5 LFS162 Class Forum
- 1 LFS166 Class Forum
- 3 LFS167 Class Forum
- 1 LFS170 Class Forum
- 1 LFS171 Class Forum
- 2 LFS178 Class Forum
- 2 LFS180 Class Forum
- 1 LFS182 Class Forum
- 4 LFS183 Class Forum
- 30 LFS200 Class Forum
- 737 LFS201 Class Forum - Discontinued
- 2 LFS201-JP クラス フォーラム
- 17 LFS203 Class Forum
- 117 LFS207 Class Forum
- 1 LFS207-DE-Klassenforum
- LFS207-JP クラス フォーラム
- 301 LFS211 Class Forum
- 55 LFS216 Class Forum
- 50 LFS241 Class Forum
- 43 LFS242 Class Forum
- 37 LFS243 Class Forum
- 13 LFS244 Class Forum
- 1 LFS245 Class Forum
- 45 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 145 LFS253 Class Forum
- LFS254 Class Forum
- LFS255 Class Forum
- 6 LFS256 Class Forum
- LFS257 Class Forum
- 1.2K LFS258 Class Forum
- 9 LFS258-JP クラス フォーラム
- 116 LFS260 Class Forum
- 155 LFS261 Class Forum
- 41 LFS262 Class Forum
- 82 LFS263 Class Forum - Discontinued
- 15 LFS264 Class Forum - Discontinued
- 11 LFS266 Class Forum - Discontinued
- 23 LFS267 Class Forum
- 18 LFS268 Class Forum
- 29 LFS269 Class Forum
- 200 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- 3 LFS281 Class Forum
- 7 LFW111 Class Forum
- 257 LFW211 Class Forum
- 178 LFW212 Class Forum
- 12 SKF100 Class Forum
- SKF200 Class Forum
- 791 Hardware
- 199 Drivers
- 68 I/O Devices
- 37 Monitors
- 98 Multimedia
- 174 Networking
- 91 Printers & Scanners
- 85 Storage
- 754 Linux Distributions
- 82 Debian
- 67 Fedora
- 16 Linux Mint
- 13 Mageia
- 23 openSUSE
- 147 Red Hat Enterprise
- 31 Slackware
- 13 SUSE Enterprise
- 351 Ubuntu
- 465 Linux System Administration
- 39 Cloud Computing
- 71 Command Line/Scripting
- Github systems admin projects
- 91 Linux Security
- 78 Network Management
- 101 System Management
- 47 Web Management
- 56 Mobile Computing
- 17 Android
- 28 Development
- 1.2K New to Linux
- 1K Getting Started with Linux
- 366 Off Topic
- 114 Introductions
- 171 Small Talk
- 20 Study Material
- 534 Programming and Development
- 293 Kernel Development
- 223 Software Development
- 1.1K Software
- 212 Applications
- 182 Command Line
- 3 Compiling/Installing
- 405 Games
- 311 Installation
- 79 All In Program
- 79 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)