Skip to content

Add SUBSPACE_CLIENT_NAMESERVERS for custom client DNS#3

Merged
33k-org merged 1 commit into
masterfrom
feature/client-nameservers
Jun 10, 2026
Merged

Add SUBSPACE_CLIENT_NAMESERVERS for custom client DNS#3
33k-org merged 1 commit into
masterfrom
feature/client-nameservers

Conversation

@33k-org

@33k-org 33k-org commented Jun 10, 2026

Copy link
Copy Markdown
Owner

Custom client nameservers

Ports upstream subspacecommunity/subspace#223 into the fork so it lives in git rather than as a local container modification.

What it does

Adds a SUBSPACE_CLIENT_NAMESERVERS env var. When set to a comma-separated list (e.g. 8.8.8.8,1.1.1.1), that value is written verbatim as the DNS = line in each newly generated client config.

Precedence (validated by rendering the template across all branches)

Scenario Result
CLIENT_NAMESERVERS set DNS = <list>
set and DISABLE_DNS=1 DNS = <list> (nameservers win)
neither set default gateway DNS (unchanged)
DISABLE_DNS=1, no nameservers no DNS line (unchanged)
empty string falls back to gateway DNS

Notes

  • Behavior is identical to upstream when the variable is unset — no regression to existing configs.
  • Only affects newly generated profiles; existing client .conf files are untouched until regenerated.
  • README default documented as (unset) rather than upstream's false, which was misleading for a list-valued variable.
  • Verified with a full docker build (compiles clean on the current master with the merged build fix).

Port of upstream subspacecommunity#223. When
SUBSPACE_CLIENT_NAMESERVERS is set to a comma-separated list, that list
is written verbatim into the generated client config's DNS line,
overriding the default gateway DNS (and SUBSPACE_DISABLE_DNS) when
present. Behavior is unchanged when the variable is unset.

Co-Authored-By: Daniel Ekman <daniel@33k.org>
@33k-org 33k-org merged commit 4357751 into master Jun 10, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant