Skip to content
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

Extra Records configuration changed in alpha5 to require subnet? #1837

Closed
Nickiel12 opened this issue Mar 19, 2024 · 2 comments
Closed

Extra Records configuration changed in alpha5 to require subnet? #1837

Nickiel12 opened this issue Mar 19, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@Nickiel12
Copy link

Nickiel12 commented Mar 19, 2024

Bug description

I had been having issues with the latest stable, so I've been running on the alpha versions. I updated from alpha4 to alpha5, and I started getting this error:
cmd/headscale/cli/root.go:54 > Failed to get headscale configuration error="netip.ParsePrefix(\"\"): no '/'"

I researched on the discord, and found this was related to changes made to ACL and ipv6. So I added a subnet mask to my DNS record:

dns_config:
    domains:
    extra_records:
    - name: git.nickiel.net
      type: A
      value: 100.64.0.1/31

And it builds and runs, but none of the added DNS records are resolving on any of my tailscale devices.

Environment

  • Headscale v0.23.0-alpha5

  • Several, but my main testing rig was running tailscale 1.62.0

  • NixOS 24.05 unstable

  • 6.1.77

  • [X ] Headscale is behind a (reverse) proxy, but I have not had any issues with it before upgrading to alpha5

To Reproduce

Use an existing configuration that adds extra records from alpha4 or earlier, then try the same configuration on alpha5, and the ip value will cause an error if a subnet mask is not defined.

I'm not entirely sure if it is intended behavior for DNS records to require a subnet mask now, or if it was a bug caused by the new IP validation, so I figured I would open a ticket about it.

@Nickiel12 Nickiel12 added the bug Something isn't working label Mar 19, 2024
@ohdearaugustin
Copy link
Collaborator

Please test with the newest version again.

@Nickiel12
Copy link
Author

It does not give that error anymore when excluding subnet masks from DNS entries. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants