DDNS Basic Implementation

[BSpendlove]

Daemon/Area

ddns

Feature/Enhancement you are proposing

Effort is yet to be made for DDNS daemon

Basic implementation will provide common API calls first and then more specific ones

Reason for Feature/Enhancement

To encourage people to use API calls instead of directly managing the configuration

[bitcollector1]

I'm Implementing DDNS in the next week or so, more great timing :) Thanks again!

[iqwang]

Hi,
I'm wondering is the ddns daemon fully working now?
Cause I can use dhcp6 without any problems, but got "result=1, text='forwarding socket is not configured for the server type Ddns'" error when trying to get ddns config.
Thanks in advance if you could give more details or help.

[iqwang]

Hi,
I'm wondering is the ddns daemon fully working now?
Cause I can use dhcp6 without any problems, but got "result=1, text='forwarding socket is not configured for the server type Ddns'" error when trying to get ddns config.
Thanks in advance if you could give more details or help.

[BSpendlove]

Hi, I'm wondering is the ddns daemon fully working now? Cause I can use dhcp6 without any problems, but got "result=1, text='forwarding socket is not configured for the server type Ddns'" error when trying to get ddns config. Thanks in advance if you could give more details or help.

Hi, sorry I haven't had enough interest on the DDNS side to work on it fully yet (nor use it at the company I am working for right now which utilize this module heavily).

There is already a basic implementation for some of the API calls for interacting with the configuration (config-get, config-reload, config-set, config-test) and a few other statistics commands but that's it.

The forwarding socket not configured sounds like to me your control agent configuration hasn't defined the ddns socket to interact with the ddns daemon, are you using any sample configurations in this repo? (as I think I may not include a working ddns config)

I am happy to test out and go through some of the kea documentation for the latest version to see which API calls I could implement for the ddns implementation if you would like to be apart of the testing.

Thanks!

[iqwang]

Hi,
I'm using my own configuration files.
I've defined ddns socket in control agent config file as below, as Kea documents suggested:
"control-sockets": {
"dhcp4": {
"socket-type": "unix",
"socket-name": "/tmp/kea4-ctrl-socket"
},
"dhcp6": {
"socket-type": "unix",
"socket-name": "/tmp/kea6-ctrl-socket"
},
"d2": {
"socket-type": "unix",
"socket-name": "/tmp/kea-ddns-ctrl-socket"
}
},
I'm guessing is the issue caused by the socket name, i.e. "ddns" used in your repo but "d2" in original kea?
I did tried to change "d2" to "ddns" and add a new socket for "ddns". Neither of them works.
Appreciated if you could upload a working ddns config example, I'll try to compare my setting with yours to see if any fix.

Thanks a lot.