Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
DNS Host Ignored
See original GitHub issueWhen I run microk8s enable dns:172.x.y.z specifying our company’s DNS server it is apparently ignored as is shown by microk8s kubectl -n kube-system edit configmap/coredns:
...
forward . 8.8.8.8 8.8.4.4
...
Nowhere in the config is our 172.x.y.z IP and none of the pods can do any DNS resolution of our LAN hosts inspection-report-20220325_141813.tar.gz .
Issue Analytics
- State:
- Created a year ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
windows - hosts file ignored, how to troubleshoot? - Server Fault
Make sure that it whatever application is ignoring the hosts file is actually using Windows' DNS cache in the first place ...
Read more >DNS entries in hosts file are being ignored by Windows 7
DNS entries in hosts file are being ignored by Windows 7. I have a webserver in my network with the address 192.168.10.110 with...
Read more >Why is my hosts file entry being ignored by the browser? [closed]
Solution (Firefox):. This solution is quite similar to Chrome - just look for "Use secure DNS" and ensure it is unchecked - but...
Read more >Hosts File not working in Windows 11/10
If the Hosts File not working in your Windows 11/10, here are some working solutions that are sure to help you get rid...
Read more >Windows 10 Ignoring the Hosts File for Specific Name ...
To prevent the computer from communicating to any external DNS name, add the relevant name to the HOSTS file and point it to...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@neoaggelos could I suggest an improvement to microk8s due to this issue?
I’ve worked with k3s and this kind of manual DNS configuration was not necessary - it would be great if microk8s “just worked” out of the box.
MicroK8s versions follow upstream Kubernetes, and we support the current and the previous two minor versions.
At the moment, these are 1.23 (upstream), 1.22 and 1.21. All three versions are actively maintained and considered stable.