Thomas,
At 2016-02-25 12:23:36 -0500
Thomas Markwalder <[email protected]> wrote:
> On 2/25/16 11:54 AM, Tobias - wrote:
> > "name": "0.168.192.in-addr-arpa.",
> Hello Tobias:
>
> I believe you have too many hyphens. Try this:
>
>
> "name": "0.168.192.in-addr.arpa.",
That's a good catch!
I have two suggestions about this.
First, perhaps the name searched for could be listed in the error
message saying no match was found. That might make it more obvious?
> feb 25 17:29:12 oink kea-dhcp-ddns[28405]: 2016-02-25 17:29:12.456 ERROR
> [kea-dhcp-ddns.dhcp-to-d2/28405] DHCP_DDNS_NO_REV_MATCH_ERROR Request ID
> 0000012DB9A727C8ADD6899EF59D4F2B6725BD34D18172E972B07ABC235CCAFE188B87: the
> configured list of reverse DDNS domains does not contain a match for: Type: 0
> (CHG_ADD)
It looks like the error message was written to include the domain name,
but that somehow we got "Type: 0 (CHG_ADD)" instead of
"103.0.168.192.in-addr-arpa"?
Second, perhaps one could make "name" optional for DDNS domains, and
just default to the right thing?
If that doesn't make sense, perhaps by default Kea could consider it an
error if you used something other than in-addr.arpa for IPv4 or
ip6.arpa for IPv6 in reverse DNS? Maybe using a special configuration
like "nonstandard-reverse-domain" or something like that could disable
such a check...
"reverse-ddns": {
"ddns-domains": [
{
"name": "0.1.10.routingwhitelist.company.internal.",
"nonstandard-reverse-domain": True,
"key-name": "tsig.example.com.",
"dns-servers": [ { "ip-address": "127.0.1.1" } ]
}
]
}
Honestly while in theory sometimes you might want something other than
the normal reverse DNS, in practice you almost always just want the
normal stuff. Software doesn't make typos. :)
Cheers,
--
Shane
_______________________________________________
Kea-users mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-users
