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

[vnet] IPv4 DNS Server #51843

Open
nklaassen opened this issue Feb 4, 2025 · 0 comments
Open

[vnet] IPv4 DNS Server #51843

nklaassen opened this issue Feb 4, 2025 · 0 comments
Labels
feature-request Used for new features in Teleport, improvements to current should be #enhancements vnet

Comments

@nklaassen
Copy link
Contributor

What would you like Teleport to do?

Serve VNet DNS requests on an IPv4 address.

What problem does this solve?

VNet currently only serves DNS requests on a Unique Local IPv6 Unicast Address. Some network policies block all IPv6 traffic, even to local addresses. To address this, VNet could make the local DNS server available on an IPv4 address.

If a workaround exists, please include it.

Allow IPv6 traffic to VNet's current DNS nameserver.

Notes:
The reason VNet currently serves DNS on an IPv6 address only is twofold:

  • VNet always has a unique IPv6 address space and can unconditionally serve DNS over IPv6. IPv4 ranges are configurable and VNet might not even have a usable IPv4 range until the user logs in to a Teleport cluster.
  • On MacOS the process serving DNS requests is different from the process configuring the DNS nameservers, it's slightly more complicated to coordinate between the processes to select a common (set of) addresses on which to serve DNS.

Why not serve DNS on localhost/127.0.0.1?

  • DNS must be served on port 53, there's no way to configure a different port. We currently avoid using 127.0.0.1 to avoid potential conflict with other local nameservers using that port, and select an address from VNet's unique IPv6 range instead.
@nklaassen nklaassen added feature-request Used for new features in Teleport, improvements to current should be #enhancements vnet labels Feb 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request Used for new features in Teleport, improvements to current should be #enhancements vnet
Projects
None yet
Development

No branches or pull requests

1 participant