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.

Sign up for GitHub

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

Jump to bottom

Document DNS client use and configuration #798

Open

jovatn opened this issue Nov 4, 2024 · 0 comments

Labels

documentation triage

Contributor

jovatn commented Nov 4, 2024 •

edited

Loading

This issue relates to #782 and should probably be a sub-issue of that.

DNS resolver can be configured statically (ietf-system) or received via DHCP client (infix-dhcp-client). Status can be viewed with "show dns".

Examples should be added to doc/system.md, and
possibly the behavior when receiving dns resolver settings from different sources (static, DHCP) should be explained
(optional) relation to mDNS client (well, see Update discovery.md with infix.local mDNS alias #738)
(optional) ... and possibly IPv6 vs IPv4 lookups.

Use of NTP client/server configuration is useful in example, as this is a case where DNS resolution is clearly needed.

admin@infix-00-00-00:/config/system/> help dns-resolver 
  search                            An ordered list of domains to search when resolving
  server                            List of the DNS servers that the resolver should query.
  options                           Resolver options.  The set of available options has been
admin@infix-00-00-00:/config/system/>

admin@infix-00-00-00:/config/system/> edit ntp server ntpexample
admin@infix-00-00-00:/config/system/ntp/server/ntpexample/> set udp address ntp.pool.org
admin@infix-00-00-00:/config/system/ntp/server/ntpexample/>

The text was updated successfully, but these errors were encountered:

jovatn added documentation triage labels

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment