-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Inconsistency ‘givenName’ in node #2177
Comments
hopleus
added a commit
to hopleus/headscale
that referenced
this issue
Oct 9, 2024
… by applying FQDN rules
6 tasks
hopleus
added a commit
to hopleus/headscale
that referenced
this issue
Oct 9, 2024
hopleus
added a commit
to hopleus/headscale
that referenced
this issue
Oct 15, 2024
… by applying FQDN rules
hopleus
added a commit
to hopleus/headscale
that referenced
this issue
Oct 15, 2024
hopleus
added a commit
to hopleus/headscale
that referenced
this issue
Oct 15, 2024
… with FQDN rules applied
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a support request?
Is there an existing issue for this?
Current Behavior
Host name where the error occurs -
MacBook-Pro
(This is the real hostname of my machine)
When registering a node on the network,
hostname
as well asgivenName
is stored in its original form fromtailcfg.Hostname
-MacBook-Pro
, without making it based on FQDN rules.When renaming a node (changing the
givenName
), the logic checks the new name for FQDN compliance (CheckForFQDNRules
) and does not allow theMacBook-Pro
name to be saved, requiring lowercase i.e.macbook-pro
.Expected Behavior
When a node is registered on the network, the givenName is stored subject to FQDN rules.
Steps To Reproduce
Environment
Runtime environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: