[Kea-users] generated-prefix, qualifying-suffix per subnet?
Jeffery Harrell
sparky at charlietango.com
Wed Jan 18 02:44:13 UTC 2017
Is there any way to have different DDNS options — generated-prefix and
qualifying-suffix — per subnet? I tried the obvious things:
{
"id": 168722944,
"subnet": "10.14.130.0/29",
"dhcp-ddns": {
"enable-updates": true,
"replace-client-name": "when-not-present",
"generated-prefix": "dhcp",
"qualifying-suffix": "dallas.charlietango.com"
},
"valid-lifetime": 300,
"option-data": [
{
"name": "routers",
"data": "10.14.130.1"
},
{
"name": "domain-name",
"data": "dallas.charlietango.com"
}
],
"pools": [
{
"pool": "10.14.130.2 - 10.14.130.6"
}
]
},
and
{
"id": 168722944,
"subnet": "10.14.130.0/29",
"generated-prefix": "dhcp",
"qualifying-suffix": "dallas.charlietango.com",
"valid-lifetime": 300,
"option-data": [
{
"name": "routers",
"data": "10.14.130.1"
},
{
"name": "domain-name",
"data": "dallas.charlietango.com"
}
],
"pools": [
{
"pool": "10.14.130.2 - 10.14.130.6"
}
]
},
and both got kicked out for being unsupported parameters. The documentation
suggests these are global settings only, but I’d really like to have them
differ by subnets without setting up *entirely* different Kea servers to
service the different subnets. Is there a trick for it?
Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20170117/4d854b62/attachment.htm>
More information about the Kea-users
mailing list