Send kea-dev mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.isc.org/mailman/listinfo/kea-dev
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of kea-dev digest..."


Today's Topics:

   1.  Reverse DNS update (tach yon)


----------------------------------------------------------------------

Message: 1
Date: Thu, 26 May 2016 11:22:15 +0100
From: tach yon <[email protected]>
To: "[email protected]" <[email protected]>
Subject: [kea-dev] Reverse DNS update
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"

Hi,
I've set up Kea 1.0.0 to serve DHCP requests and store lease information in a 
PgSQL database. There's also a separate bind 9.10 server that I'm trying to 
push dynamic DNS updates to, but unfortunately this isn't working. I'm trying 
to find out why, but I've come across something I don't quite understand.
This suggests to me that the entry has been successfully added to the database 
with the fqdn_rev boolean marked as true:

  address  |     hwaddr     |    client_id     | valid_lifetime |         
expire         | subnet_id | fqdn_fwd | fqdn_rev |         hostname          | 
state-----------+----------------+------------------+----------------+------------------------+-----------+----------+----------+---------------------------+-------
 168566422 | \x0050569d0f1f | \x010050569d0f1f |           4000 | 2016-05-26 
11:04:35+01 |         1 | f        | t        | windhcp.example.net. |     0

Showing fqdn_rev marked as true seems strange because in kea.conf I have it set 
to update forward DNS, not reverse DNS.
"DhcpDdns": {        "tsig-keys": [                {                        
"name": "dynkey",                        "algorithm": "HMAC-MD5",               
         "secret": "xxx"                },        ],        "forward-ddns": {   
             "ddns-domains": [                        {                        
"name": "dynamic.example.net.",                        "key-name": "dynkey",    
                    "dns-servers": [ { "ip-address": "10.12.30.7" } ]           
             },                ]        },        "reverse-ddns": {             
   "ddns-domains": [ ]        }},

I also see this in the ddns log:
2016-05-26 09:57:55.347 DEBUG [kea-dhcp-ddns.dhcp-to-d2/94515] 
DHCP_DDNS_REV_REQUEST_IGNORED Request ID: Reverse updates are disabled, the 
reverse portion of request will be ignored: Type: 0 (CHG_ADD)Forward Change: 
noReverse Change: noFQDN: [windhcp.dynamic.example.net.]IP Address: 
[10.12.30.150]Lease Expires On: 20160526100435Lease Length: 4000
2016-05-26 09:57:55.348 DEBUG [kea-dhcp-ddns.dhcp-to-d2/94515] 
DHCP_DDNS_REQUEST_DROPPED Request ID : Request contains no enabled update 
requests and will be dropped: Type: 0 (CHG_ADD)Forward Change: noReverse 
Change: noFQDN: [windhcp.dynamic.example.net.]IP Address: [10.12.30.150]Lease 
Expires On: 20160526100435Lease Length: 4000

This feels like it's trying to update a reverse request despite having 
configured it to create forward entries, unless I configured it wrong :\
If someone could please help make sense of this it would be very much 
appreciated. Thank you in advance for your time and consideration.
Kind regards,Lewis                                        
-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<https://lists.isc.org/pipermail/kea-dev/attachments/20160526/9e12739e/attachment-0001.html>

------------------------------

_______________________________________________
kea-dev mailing list
[email protected]
https://lists.isc.org/mailman/listinfo/kea-dev

End of kea-dev Digest, Vol 26, Issue 5
**************************************

Reply via email to