[Kea-users] DDNS update for win10 clients
Dominik Epple
dominik.epple at gmail.com
Sat Oct 21 20:22:24 UTC 2017
Hi list,
I am running a test installation of Kea 1.2.0 on FreeBSD 11.1 built from
ports (1.2.0_3) with MySQL support (for leases and reservations). IPv4
only. DDNS integration with PowerDNS (powerdns-4.0.4_5, also built from
ports with MySQL support).
So far I got it like 90% working. In particular I can see some clients
(Linux, Android) getting their IPs and DDNS update is working as well.
However I got an issue with Windows10 clients: DDNS updates seem to happen
only for the reverse DNS entry, not for the foward entry. That is what I
can see in the PowerDNS maps and my Kea logs show:
1. kea-dhcp4.log
2017-10-21 21:49:08.610 INFO [kea-dhcp4.dhcp4/29343] DHCP4_STARTED Kea
DHCPv4 server version 1.2.0 started
2017-10-21 21:49:23.394 INFO [kea-dhcp4.leases/29343] DHCP4_RELEASE
[hwtype=1 bc:83:85:25:f6:6a], cid=[01:bc:83:85:25:f6:6a], tid=0xc6d9b97e:
address 192.168.1.104 was released properly.
2017-10-21 21:49:35.364 INFO [kea-dhcp4.leases/29343] DHCP4_LEASE_ADVERT
[hwtype=1 bc:83:85:25:f6:6a], cid=[01:bc:83:85:25:f6:6a], tid=0x344af947:
lease 192.168.1.104 will be advertised
2017-10-21 21:49:35.369 INFO [kea-dhcp4.leases/29343] DHCP4_LEASE_ALLOC
[hwtype=1 bc:83:85:25:f6:6a], cid=[01:bc:83:85:25:f6:6a], tid=0x344af947:
lease 192.168.1.104 has been allocated
2. kea-ddns.log
2017-10-21 21:49:08.608 DEBUG [kea-dhcp-ddns.dctl/29350] DCTL_RUN_PROCESS
DhcpDdns starting application event loop
2017-10-21 21:49:08.608 INFO [kea-dhcp-ddns.dhcpddns/29350]
DHCP_DDNS_STARTED Kea DHCP-DDNS server version 1.2.0 started
2017-10-21 21:49:08.608 DEBUG [kea-dhcp-ddns.dhcpddns/29350]
DHCP_DDNS_QUEUE_MGR_STARTED application's queue manager has begun listening
for requests.
2017-10-21 21:49:23.401 INFO [kea-dhcp-ddns.d2-to-dns/29350]
DHCP_DDNS_REMOVE_SUCCEEDED DHCP_DDNS Request ID
0001015DEBCEB134F279474D91EFAC78C1B7BD25006A8C3BC36295F2AC60DA6258A9F0:
successfully removed the DNS mapping addition for this request: Type: 1
(CHG_REMOVE)
Forward Change: no
Reverse Change: yes
FQDN: [APFEL.lan.]
IP Address: [192.168.1.104]
DHCID:
[0001015DEBCEB134F279474D91EFAC78C1B7BD25006A8C3BC36295F2AC60DA6258A9F0]
Lease Expires On: 20171021204627
Lease Length: 3600
2017-10-21 21:49:35.374 INFO [kea-dhcp-ddns.d2-to-dns/29350]
DHCP_DDNS_ADD_SUCCEEDED DHCP_DDNS Request ID
0001015DEBCEB134F279474D91EFAC78C1B7BD25006A8C3BC36295F2AC60DA6258A9F0:
successfully added the DNS mapping addition for this request: Type: 0
(CHG_ADD)
Forward Change: no
Reverse Change: yes
FQDN: [APFEL.lan.]
IP Address: [192.168.1.104]
DHCID:
[0001015DEBCEB134F279474D91EFAC78C1B7BD25006A8C3BC36295F2AC60DA6258A9F0]
Lease Expires On: 20171021204935
Lease Length: 3600
This is from a "ipconfig /release", "ipconfig /renew" cycle on the Windows
box. I can see equivalent logs from other test cases (rebooting the device,
etc).
So I can not see any errors related to this event, but for whatever reasons
Kea thinks it is only necessary to manage the reverse map and does nothing
with the forward map. Of course, however, we'd like to see the windows
client also show up in the forward map.
A different Windows 10 test client shows the same behavior. (I don't have
other Windows versions available for cross-testing Windows versions; Linux
and Android however don't show this behavior).
kea.conf pasted below.
Regards
Dominik
{
"Dhcp4": {
"interfaces-config": {
"interfaces": [ "igb0" ]
},
"control-socket": {
"socket-type": "unix",
"socket-name": "/tmp/kea-dhcp4-ctrl.sock"
},
"dhcp-ddns": {
"enable-updates": true,
"qualifying-suffix": "lan",
"generated-prefix": "kea"
},
"lease-database": {
"type": "mysql",
"name": "kea",
"host": "localhost",
"user": "kea",
"password": "..."
},
"hosts-database": {
"type": "mysql",
"name": "kea",
"host": "localhost",
"user": "kea",
"password": "..."
},
"expired-leases-processing": {
"reclaim-timer-wait-time": 10,
"flush-reclaimed-timer-wait-time": 25,
"hold-reclaimed-time": 3600,
"max-reclaim-leases": 100,
"max-reclaim-time": 250,
"unwarned-reclaim-cycles": 5
},
"renew-timer": 900,
"rebind-timer": 1800,
"valid-lifetime": 3600,
"option-data": [
{
"name": "domain-name-servers",
"data": "192.168.1.10"
},
{
// "code": 15,
"name": "domain-name",
"data": "lan"
},
{
"name": "domain-search",
"data": "lan"
},
{
"name": "default-ip-ttl",
"data": "0xf0"
}
],
"subnet4": [
{
"subnet": "192.168.1.0/24",
"id": 1024,
"pools": [ { "pool": "192.168.1.101 - 192.168.1.254" } ],
"option-data": [ { "name": "routers", "data": "192.168.1.1" } ]
}
]
},
"DhcpDdns":
{
"ip-address": "127.0.0.1",
"port": 53001,
"tsig-keys": [],
"forward-ddns" : {
"ddns-domains": [
{
"name": "lan.",
"key-name": "",
"dns-servers": [
{
"hostname": "",
"ip-address": "127.0.0.1",
"port": 53
}
]
}
]
},
"reverse-ddns" : {
"ddns-domains": [
{
"name": "1.168.192.in-addr.arpa.",
"key-name": "",
"dns-servers": [
{
"hostname": "",
"ip-address": "127.0.0.1",
"port": 53
}
]
}
]
}
},
"Logging":
{
"loggers": [
{
"name": "kea-dhcp4",
"output_options": [
{
"output": "/var/log/kea-dhcp4.log"
}
],
"severity": "DEBUG",
"debuglevel": 10
},
{
"name": "kea-dhcp-ddns",
"output_options": [
{
"output": "/var/log/kea-ddns.log"
}
],
"severity": "DEBUG",
"debuglevel": 10
}
]
}
}
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/kea-users/attachments/20171021/3d439a31/attachment.htm>
More information about the Kea-users
mailing list