https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3s
a
This message was deleted.
b
ndots:5
is a Kubernetes default parameter, i.e. it is not set by k3s. You can change it though https://kubernetes.io/docs/concepts/services-networking/dns-pod-service/#pod-dns-config
However, it should work with 
ndots:5
Can you check that github.com+your_search_domains does not exist? Check: • github.com.default.svc.cluster.local • github.com.svc.cluster.local • etc When you try 
<http://github.com|github.com>.
you are telling your OS that the string is already a FQDN and thus it does not need to add any search domain
I suspect 
<http://github.com|github.com>.$OneOfYourSearchDomains[[home search domains redacted]
returns an IP from a server which does not reply to pings
Something similar happened to this user https://github.com/k3s-io/k3s/issues/5045
k
I cannot explain that behaviour, but I have had a somewhat similar example, where pings would most of the time simply fail, and some times it would succeed, albeit with a massive latency on the line. Turns out that my dns pod wasn't running properly, and along side many other system pods that were in a malfunctioning state, so I deleted them all and let k3s recreate them to resolve the issue.
b
ok so I get this:
Copy code
bash-5.1# nslookup <http://github.com|github.com>
Server:         10.43.0.10
Address:        10.43.0.10#53

*** Can't find <http://github.com.private.home.jtcressy.net|github.com.private.home.jtcressy.net>: No answer
but this makes no sense, except that there are exactly 5 dots in that FQDN it stopped with. and this is the first search domain after cluster.local
Hmm, I think the problem is that some DNS somewhere up my chain is returning with a NOERROR for 
<http://github.com.private.home.jtcressy.net|github.com.private.home.jtcressy.net>
instead of NXDOMAIN since when I dig 
<http://github.com|github.com>.svc.cluster.local
it will give me NXDOMAIN, and this must be the response needed for the resolver to query the next search domain
LOL so the problem is that I had CAA records with wildcards e.g. 
*.<http://home.jtcressy.net|home.jtcressy.net> in CAA
As soon as I deleted them I get NXDOMAIN instead of NOERROR I hate DNS!
🤣 1
my base domain, jtcressy.net is hosted in clouddns
and instead of CNAME records shadowing things, it was CAA records
k
Nice, good to hear you managed to resolve it 😄
b
Yes! Good work @bright-jordan-61721, DNS can be complex
140 Views
Open in Slack
PreviousNext
Powered by