Closed purepani closed 8 months ago
@purepani oh I've not been using the dns so I didn't noticed this. I can reproduce it easily, however I'm not sure how I can fix it. Will give it a shot in next couple of weeks
@purepani I don't think there's anything we can do to allow netclient to write to /etc/hosts
I am pretty sure this can be closed now that Netmaker abandoned the idea of using hosts file: https://github.com/gravitl/netclient/pull/655
I'm just not sure what should be configured instead.
Current documentation suggests pointing your client machine to the CoreDNS' IP address. I have confirmed this with Netmaker developers on Discord.
@nazarewk thanks for finding this.
FYI: solved DNS completely server-side without any client-side config (wired up CoreDNS as NS
record)
https://github.com/NixOS/nixpkgs/pull/283768#issuecomment-1912175838
FYI: solved DNS completely server-side without any client-side config (wired up CoreDNS as
NS
record) #283768 (comment)
Hello there, would you be able to expand how or what did you do specifically?
I did 1, 2 and 3 from this: https://docs.netmaker.io/architecture.html#coredns
but where did you wire the NS record? an actual domain pointing (which one?) to the netmaker server public address or how?
Describe the bug
When using netclient with a netmaker server configured with DNS, the domains are unable to populate the /etc/hosts file, rendering the feature unable to be used. This happens because the hosts file is symlinked into the nix store, and as such cannot be modified.
Steps To Reproduce
Steps to reproduce the behavior:
Expected behavior
Pinging the domain should succeed
Additional context
The service will likely need to be able to modify the hosts file dynamically in order to work correctly. I'm not sure what the solution would be in this case though.
Notify maintainers
@wexder
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"
and paste the result.