search

bpbp-boop / route53d

Automatically exported from code.google.com/p/route53d
0 stars 0 forks source link

Updates from ISC DHCP don't work #6

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Set up a zone in your dhcpd.conf that points at the route53d server/instance 
(make sure the route53d server runs on port 53 -- isc dhcp can't specify port 
#):

zone mydomain.com {
   primary myroute53dserver.mydomain.com;
}

2. Add a new lease in this zone with ddns-hostname and ddns-domainname set:

host whatever {
   hardware ethernet ...;
   ddns-hostname "myserver";
   ddns-domainname "mydomain.com";
}

3. renew dhcp lease on myserver.

What is the expected output? What do you see instead?

Expected result: dns is registered.  Actual result is this from the log:

2012-09-18 14:04.41 PDT - 25730 - DEBUG - route53d.py:534 __init__ - no tsig 
config for X.X.4.22
2012-09-18 14:04.41 PDT - 25730 - INFO - route53d.py:294 handle_update - UPDATE 
from X.X.4.22: mydomain.com. IN SOA
2012-09-18 14:04.41 PDT - 25730 - WARNING - route53d.py:302 handle_update - 
UPDATE unsupported prereqs from X.X.4.22

What version of the product are you using? On what operating system?

dhcpd - isc dhcp 3.0.5-23.el5_5.2
route53d - rev 25

Original issue reported on code.google.com by lier...@gmail.com on 18 Sep 2012 at 9:05

GoogleCodeExporter commented 9 years ago 
Here is my work-around.  Basically, I just ignore that it's got pre-reqs, and 
let it add the TXT and A records anyway.  I also handle an interesting thing 
where DHCP is specifying a 15 million second TTL.

Original comment by lier...@gmail.com on 18 Sep 2012 at 11:12

Attachments: