[Kea-users] generated-prefix, qualifying-suffix per subnet?

[Jason Guy]

Hi Jeffery,

I actually just got my ddns working today. I am not sure why you would want
different DDNS per subnet. DDNS is just the update mechanism to your DNS
server. I suppose you could allocate a sub-domain per subnet, but im not
sure how you can do that.

I think the best way to proceed is to get the syntax correct. Then test and
see what it is doing. Does the domain-name option govern the FQDN sent in
DDNS? Perhaps try this config and tweak it.


"Dhcp4": {
    "valid-lifetime": 300,
    "subnet4": [
        {
            "subnet": "10.14.130.0/29",
            "id": 168722944,
            "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"
                }
            ],
        }
    ],
    "dhcp-ddns": {
         "enable-updates": true,
         "replace-client-name": "when-not-present",
         "generated-prefix": "dhcp",
         "qualifying-suffix": "charlietango.com"
     },
},
"DhcpDdns": {
    "forward-ddns": {
"ddns-domains": [
   {
"name": "dallas.charlietango.com",
"key-name": "",
"dns-servers": [
   { "ip-address": "172.16.1.5" },
   { "ip-address": "172.16.2.5" }
]
   },
   {
"name": "charlietango.com",
"key-name": "",
"dns-servers": [
   { "ip-address": "172.16.2.5" }
]
   },

]
    }
}

Cheers,
Jason

On Tue, Jan 17, 2017 at 9:44 PM, Jeffery Harrell <sparky at charlietango.com>
wrote:

> 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!
>
>
> _______________________________________________
> Kea-users mailing list
> Kea-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/kea-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20170118/722a8094/attachment.htm>