Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • Kea Kea
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 554
    • Issues 554
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 66
    • Merge requests 66
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ISC Open Source ProjectsISC Open Source Projects
  • KeaKea
  • Issues
  • #557
Closed
Open
Issue created Apr 02, 2019 by Ghost User@ghost

ddns in combination with dhcpv6 did not work as expected

Describe the bug setup Kea 1.5 for IPv4 and IPv6 and ddns. Works without any problem in with the IPv4 part. DNS Server is PowerDNS 4.1.8

To Reproduce Steps to reproduce the behavior:

  1. Run Kea dhcpv6 and ddns

Part of kea-dhcp6.conf

    "dhcp-ddns": {                                            
        "enable-updates": true,                               
        "generated-prefix": "host",                           
        "qualifying-suffix": "xxxxx.local",               
        "replace-client-name": "when-not-present",            
        "override-no-update": true,                           
        "override-client-update": true                        
    },                                                                         
         
  1. Client get IPv6 addresses from the dhcp-server, and now i would expect, it see the relevant records in the DNS-Server, but except one record for the AAAA and the PTR record in addition to the DHCID Record nothing appears. Even there are 10 to 15 other devices get an ip from the dhcp-server.

Expected behavior See the generated records in the DNS-Server

Environment:

  • Kea version: 1.5
  • OS: Alpine-Linux 3.9
  • /usr/bin/kea-dhcp-ddns -V 1.5.0 tarball linked with: log4cplus 2.0.3 OpenSSL 1.1.1b 26 Feb 2019

Additional Information What i see in the logfile is only remove messages, but no create messages.

com-b-alpine kea-dhcp-ddns: INFO [kea-dhcp-ddns.d2-to-dns] DHCP_DDNS_REMOVE_SUCCEEDED DHCP_DDNS Request ID 000201F095FB83A15F88F0A7259900830C3C8137668532382B0CC1A159474D19CDE1AC: successfully removed the DNS mapping addition for this request: Type: 1 (CHG_REMOVE)#012Forward Change: yes#012Reverse Change: yes#012FQDN: [host-2003-xxxx-xxxx-xxxxx--185.ghostdive.local.]#012IP Address: [2003:xxxx:xxxx:xxxx::185]#012DHCID: [000201F095FB83A15F88F0A7259900830C3C8137668532382B0CC1A159474D19CDE1AC]#012Lease Expires On: 20190402151730#012Lease Length: 4000#012
com-b-alpine kea-dhcp-ddns: DEBUG [kea-dhcp-ddns.asiodns] ASIODNS_FETCH_COMPLETED upstream fetch to 10.1.0.10(10053) has now completed
com-b-alpine kea-dhcp-ddns: DEBUG [kea-dhcp-ddns.d2-to-dns] DHCP_DDNS_UPDATE_RESPONSE_RECEIVED Request ID 000201F095FB83A15F88F0A7259900830C3C8137668532382B0CC1A159474D19CDE1AC: to server: 10.1.0.10 port:10053 status: SUCCESS, rcode: NXRRSET
com-b-alpine kea-dhcp-ddns: DEBUG [kea-dhcp-ddns.d2-to-dns] DHCP_DDNS_UPDATE_REQUEST_SENT Request ID 000201F095FB83A15F88F0A7259900830C3C8137668532382B0CC1A159474D19CDE1AC: Reverse Remove to server: 10.1.0.10 port:10053
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking