https://rancher.com/ logo
Join Slack
Powered by
This message was deleted.
# k3s
a
This message was deleted.
c
mdsns does not work in golang
you must use an actual DNS record served by a DNS server, or put it in the hosts file
q
Ah, that's too bad. Was not planning on running a DNS server, and maintaining hosts file when using DHCP isn't really a great option either. Guess I'll have to take a step back and have a think. Thanks for the reply.
c
on home networks there is frequently one built in to your DHCP server, if you’re using dnsmasq or something
when you start exposing services across multiple nodes is usually a good time to start nailing down dns and IP reservations
q
Yeah, there used to be one in my linksys router, but I recently switched to a mesh thingy which doesn't. This is only for a homelab.
Looking at the docs, it says it will use the C library routines if 
cgo
is available under certain conditions. What does "`cgo` is available" mean in this context?
c
if the binary is built with cgo enabled.
q
I'm guessing k3s isn't? 🙂
c
it is, because we build in sqlite (which is c) but because we do a static build (so as to be portable across distros) we use the pure go resolver
q
Ok, thanks. I'll have to consider my options another day, todays homelab sessions can't fit a full makeover of name resolution in the network 😄
3 Views
Open in Slack
PreviousNext
Powered by