5 ms·
What about DNS integration? As far as I know, you can't resolve nodes by name (http://media-server), you have to use node's internal IP.
by blue_pants 8mo ago
What about DNS integration? As far as I know, you can't resolve nodes by name (http://media-server), you have to use node's internal IP.
- bink 8mo agoNebula uses lighthouses instead of DNS for finding other nodes. https://github.com/slackhq/nebula?tab=readme-ov-file#2-optional-but-you-really-should-at-least-one-discovery-node-with-a-routable-ip-address-which-we-call-a-lighthouse https://github.com/slackhq/nebula?tab=readme-ov-file#2-optio...
- blue_pants 8mo agoYes, but when you connect your phone to a Nebula network, and go to http://media-server in your browser, the DNS won't resolve it to your desired node, because the phone client (same on desktop) didn't update DNS of the phone, so you'll have to use node's IP address. That's what I've read (when evaluating Nebula), at least.
- nine_k 8mo agoWhen your nodes are not very numerous, and their IPs are statically assigned, you can just have them in a hosts file, or even served by your normal name server if you're using a split-horizon configuration.
- blue_pants 8mo agoEditing hosts file seems unwieldy, and impossible on a phone without rooting it, AFAIK > split-horizon configuration Is it when your local router redirects media-server.mydomain.com to a local IP, and say Cloudflare DNS redirects it to your Nebula IP?
- bink 8mo agoIt doesn't automatically update, that's true. But I think the typical way to deal with this is to have a nebula subdomain. www.nebula.example.com instead of www.example.com.
- blue_pants 8mo agoI haven't thought about it, thanks