Skip to content

Add Lighthouse lookup issue to DNS limitations #232

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

Merged
merged 1 commit into from
Apr 7, 2025
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions docs/guides/using-lighthouse-dns/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -86,12 +86,14 @@ curl --dns-servers "100.100.0.1" http://alice-laptop:3000

## Limitations

- The built-in DNS server will only respond to queries for known Nebula hosts and will not make upstream queries to a
secondary DNS server (e.g. for supporting both internal DNS and public DNS.)
- The built-in DNS server will only respond to queries for known Nebula hosts (i.e. hosts which have handshaked with the
lighthouse - this means lighthouses themselves are not included.)
- A host's hostname is restricted to the name in its certificate.
- There is no way to register additional hostnames (e.g. additional CNAMEs for a given Nebula host, or additional A
records for managing non-Nebula hosts.)
- Duplicate names in certificates will result in non-stable answers from the DNS server.
- There is no way to make upstream requests to a secondary DNS server (e.g. for supporting both internal DNS and public
DNS.)
- Duplicate names (i.e. the same name in multiple certificates) will result in non-stable answers from the DNS server.
- If the name in the Nebula certificate is not a [valid hostname](https://www.rfc-editor.org/rfc/rfc1035#section-2.3.1),
Lighthouse DNS will return an empty result.

Expand Down