-
Notifications
You must be signed in to change notification settings - Fork 330
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
T6773: RFC-2136 support for Kea DHCP4 server #4153
base: current
Are you sure you want to change the base?
Changes from all commits
929a238
14c54ee
3f50c2d
58c0c6f
c994709
248b18c
cfc438e
3a5d9d6
9f76ec0
885427e
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
{ | ||
"DhcpDdns": { | ||
"ip-address": "127.0.0.1", | ||
"port": 53001, | ||
"control-socket": { | ||
"socket-type": "unix", | ||
"socket-name": "/run/kea/kea-ddns-ctrl-socket" | ||
}, | ||
"tsig-keys": {{ dynamic_dns_update | kea_dynamic_dns_update_tsig_key_json }}, | ||
"forward-ddns" : { | ||
"ddns-domains": {{ dynamic_dns_update | kea_dynamic_dns_update_domains('forward_domain') }} | ||
}, | ||
"reverse-ddns" : { | ||
"ddns-domains": {{ dynamic_dns_update | kea_dynamic_dns_update_domains('reverse_domain') }} | ||
}, | ||
"loggers": [ | ||
{ | ||
"name": "kea-dhcp-ddns", | ||
"output_options": [ | ||
{ | ||
"output": "stdout", | ||
"pattern": "%-5p %m\n" | ||
} | ||
], | ||
"severity": "INFO", | ||
"debuglevel": 0 | ||
} | ||
] | ||
} | ||
} |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,19 @@ | ||
<!-- include start from dhcp/ddns-dns-server.xml.i --> | ||
<tagNode name="dns-server"> | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. In Kea's config, the My feeling is that the server number here is just extra information — as far as I can see from the docs, the order of servers in the list has no special meaning to Kea. Unless I'm missing anything here, I would make it |
||
<properties> | ||
<help>DNS server specification</help> | ||
<valueHelp> | ||
<format>u32:1-999999</format> | ||
<description>Number for this DNS server</description> | ||
</valueHelp> | ||
<constraint> | ||
<validator name="numeric" argument="--range 1-999999"/> | ||
</constraint> | ||
<constraintErrorMessage>DNS server number must be between 1 and 999999</constraintErrorMessage> | ||
</properties> | ||
<children> | ||
#include <include/address-ipv4-ipv6-single.xml.i> | ||
#include <include/port-number.xml.i> | ||
</children> | ||
</tagNode> | ||
<!-- include end --> |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,103 @@ | ||
<!-- include start from dhcp/ddns-settings.xml.i --> | ||
<leafNode name="force-updates"> | ||
<properties> | ||
<help>Send updates for this scope</help> | ||
<valueless /> | ||
</properties> | ||
</leafNode> | ||
<leafNode name="force-client-update"> | ||
<properties> | ||
<help>Always update both forward and reverse DNS data, regardless of the client's request</help> | ||
<valueless /> | ||
</properties> | ||
</leafNode> | ||
<leafNode name="force-no-update"> | ||
<properties> | ||
<help>Perform a DDNS update, even if the client instructs the server not to</help> | ||
<valueless /> | ||
</properties> | ||
</leafNode> | ||
<leafNode name="replace-client-name"> | ||
<properties> | ||
<help>Replace client name mode</help> | ||
<completionHelp> | ||
<list>never always when-present when-not-present</list> | ||
</completionHelp> | ||
<valueHelp> | ||
<format>never</format> | ||
<description>Use the name the client sent. If the client sent no name, do not generate | ||
one</description> | ||
</valueHelp> | ||
<valueHelp> | ||
<format>always</format> | ||
<description>Replace the name the client sent. If the client sent no name, generate one | ||
for the client</description> | ||
</valueHelp> | ||
<valueHelp> | ||
<format>when-present</format> | ||
<description>Replace the name the client sent. If the client sent no name, do not | ||
generate one</description> | ||
</valueHelp> | ||
<valueHelp> | ||
<format>when-not-present</format> | ||
<description>Use the name the client sent. If the client sent no name, generate one for | ||
the client</description> | ||
</valueHelp> | ||
<defaultValue>never</defaultValue> | ||
<constraint> | ||
<regex>(never|always|when-present|when-not-present)</regex> | ||
</constraint> | ||
<constraintErrorMessage>Invalid replace client name mode</constraintErrorMessage> | ||
</properties> | ||
</leafNode> | ||
<leafNode name="generated-prefix"> | ||
<properties> | ||
<help>The prefix used in the generation of an FQDN</help> | ||
<constraint> | ||
<validator name="fqdn" /> | ||
</constraint> | ||
<constraintErrorMessage>Invalid generated prefix</constraintErrorMessage> | ||
</properties> | ||
</leafNode> | ||
<leafNode name="qualifying-suffix"> | ||
<properties> | ||
<help>The suffix used when generating an FQDN, or when qualifying a partial name</help> | ||
<constraint> | ||
<validator name="fqdn" /> | ||
</constraint> | ||
<constraintErrorMessage>Invalid qualifying suffix</constraintErrorMessage> | ||
</properties> | ||
</leafNode> | ||
<leafNode name="update-on-renew"> | ||
<properties> | ||
<help>Update DNS record on lease renew</help> | ||
<valueless /> | ||
</properties> | ||
</leafNode> | ||
<leafNode name="use-conflict-resolution"> | ||
<properties> | ||
<help>Defines DNS conflict resolution behavior</help> | ||
<valueless /> | ||
</properties> | ||
</leafNode> | ||
<leafNode name="ttl-percent"> | ||
<properties> | ||
<help>Calculate TTL of the DNS record as a percentage of the lease lifetime</help> | ||
<constraint> | ||
<validator name="numeric" argument="--range 1-100" /> | ||
</constraint> | ||
<constraintErrorMessage>Invalid qualifying suffix</constraintErrorMessage> | ||
</properties> | ||
</leafNode> | ||
<leafNode name="hostname-char-set"> | ||
<properties> | ||
<help>A regular expression describing the invalid character set in the host name</help> | ||
</properties> | ||
</leafNode> | ||
<leafNode name="hostname-char-replacement"> | ||
<properties> | ||
<help>A string of zero or more characters with which to replace each invalid character in | ||
the host name</help> | ||
</properties> | ||
</leafNode> | ||
<!-- include end --> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if these ports should be configurable, in case someone is already running something on 53001.