Post ASfqgQdnoxF2buP0SW by selea@social.linux.pizza
(DIR) More posts by selea@social.linux.pizza
(DIR) Post #ASflOx0oEBMa1Z0gPw by selea@social.linux.pizza
2023-02-14T14:15:46Z
0 likes, 0 repeats
Apparently, I have to write absolute hostnames (example.com.) in order to make DNS resolution work in my kluster..... wat
(DIR) Post #ASfltZJuMcOnWQXjhA by joacim@mastodon.melin.org
2023-02-14T14:21:14Z
0 likes, 0 repeats
@selea in /etc/resolv.conf: search domain.tld
(DIR) Post #ASfp44bBE28lHzK3Xc by selea@social.linux.pizza
2023-02-14T14:56:51Z
0 likes, 0 repeats
@joacim yeah, it is already there. And everything has worked nicely up until recently without modifications there.
(DIR) Post #ASfp8OUNDRw88UCP8i by AIaYYAle4i1uKmKpqy.gme@bofh.social
2023-02-14T14:49:41.410997Z
0 likes, 0 repeats
/etc/resolv.conf.Set the search … list for domains for the resolver to search for.
(DIR) Post #ASfp8OwjW0cbYRT3LM by selea@social.linux.pizza
2023-02-14T14:57:37Z
0 likes, 0 repeats
@gme Already present actually, the thing is that every domain (libre.fm, google.com, selea.se ) suffers from the same problem in my kluster
(DIR) Post #ASfqSQsg8FOHIggd8a by AIaYYAle4i1uKmKpqy.gme@bofh.social
2023-02-14T15:03:24.060693Z
0 likes, 0 repeats
What happens if you do a dig query on your hostname?gme@DESKTOP-R7ILMJV:~$ dig google.com +showsearch; <<>> DiG 9.18.11-2~bpo11+1-Debian <<>> google.com +showsearch;; global options: +cmd;; Got answer:;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52666;; flags: qr rd ad; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL: 0;; WARNING: recursion requested but not available;; QUESTION SECTION:;google.com. IN A;; ANSWER SECTION:google.com. 0 IN A 64.233.177.99google.com. 0 IN A 64.233.177.105google.com. 0 IN A 64.233.177.104google.com. 0 IN A 64.233.177.103google.com. 0 IN A 64.233.177.147google.com. 0 IN A 64.233.177.106;; Query time: 0 msec;; SERVER: 172.28.224.1#53(172.28.224.1) (UDP);; WHEN: Tue Feb 14 15:02:10 UTC 2023;; MSG SIZE rcvd: 142gme@DESKTOP-R7ILMJV:~$
(DIR) Post #ASfqSRTttrAHA86M9g by selea@social.linux.pizza
2023-02-14T15:12:24Z
0 likes, 0 repeats
@gme dig worked fine, since it assumes that the domain is absolute.I did purge my resolv.conf and removed the dns-search entry. And that solved the issue that I had.Another solution I found thanks to the kubernetes chat room on matrix is this:https://pracucci.com/kubernetes-dns-resolution-ndots-options-and-why-it-may-affect-application-performances.html dnsConfig: options: - name: ndots value: "1"That solved my problem too, but then I had to modify all my deployments with that
(DIR) Post #ASfqgQdnoxF2buP0SW by selea@social.linux.pizza
2023-02-14T15:14:57Z
0 likes, 0 repeats
@gme In the end - I have no idea why this suddenly became an issue. Things worked fine for month
(DIR) Post #ASfrEbVDwaS68vgZmK by AIaYYAle4i1uKmKpqy.gme@bofh.social
2023-02-14T15:18:52.330026Z
0 likes, 0 repeats
Software update or configuration change usually.
(DIR) Post #ASfrEc5jkpevyAljgu by selea@social.linux.pizza
2023-02-14T15:21:07Z
0 likes, 0 repeats
@gme I think I know - it must have happened when I changed my router from a pfsense to a EdgeRouter ....
(DIR) Post #ASkJKgzk0mEGGNUW8G by scumola@social.linux.pizza
2023-02-16T18:54:50Z
0 likes, 0 repeats
@selea echo "search example.com" >> /etc/resolv.conf
(DIR) Post #ASkJMSXAkOjjzcyFsG by selea@social.linux.pizza
2023-02-16T18:55:10Z
0 likes, 0 repeats
@scumola removing that solved the issues actually
(DIR) Post #ASkJOfFWRX1O0Ylasq by scumola@social.linux.pizza
2023-02-16T18:55:31Z
0 likes, 0 repeats
@selea lol ha! :)
(DIR) Post #ASkJQwpY32cP77hr72 by selea@social.linux.pizza
2023-02-16T18:55:59Z
0 likes, 0 repeats
@scumola yeah it was strange, no idea why ;)