gjmf / route53d Goto Github PK

The DNS dynamic update mechanism allows deletion of 

1) a specific resource-record, 
2) a resource-record set, or 
3) deletion of all records belonging to a name. 

The Route 53 API, however, implements only specific resource-record deletion. 
At present route53d will reject requests for the other deletion types. Instead 
it should query the Route 53 API to find the data it needs to populate a valid 
API request on foot of all dynamic update deletion variants.

install boto and dnspython

jdyer@retina:~/Downloads/route53d-0.01-alpha » pip list                        
    1 ↵
argparse (1.2.1)
boto (2.9.8)
cli53 (0.3.6)
distribute (0.6.45)
dnspython (1.11.0)
docopt (0.6.1)
pssh (2.3.1)
SpoofMAC (1.2.1)
vboxapi (1.0)
wsgiref (0.1.2)

jdyer@retina:~/Downloads/route53d-0.01-alpha » sudo ./route53d.py --config 
route53d.ini.sample
Traceback (most recent call last):
  File "./route53d.py", line 44, in <module>
    import dns.message
ImportError: No module named dns.message

Not very familiar w/ Python but it looks like it cant load that module...  Not 
sure why

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

Add RR where RRSet already exists:

<ErrorResponse 
xmlns="https://route53.amazonaws.com/doc/2011-05-05/"><Error><Type>Sender</Type>
<Code>InvalidChangeBatch</Code><Message>Tried to create resource record set 
x.foo.com., type A but it already 
exists</Message></Error><RequestId>6d83a7e4-654c-11e1-847f-ddaa49e4c811</Request
Id></ErrorResponse>

Delete one RR from existing RRSet:

<ErrorResponse 
xmlns="https://route53.amazonaws.com/doc/2011-05-05/"><Error><Type>Sender</Type>
<Code>InvalidChangeBatch</Code><Message>Tried to delete resource record set 
x.foo.com., type A but the values provided do not match the current 
values</Message></Error><RequestId>8dc0260b-654e-11e1-ba27-5fc1b60d153b</Request
Id></ErrorResponse>

TSIG authentication is desirable for the following:

 + NOTIFY queries and responses
 + Zone transfers IXFR/AXFR queries
 + nsupdate messages and responses

The daemon should respond to SOA queries for slave zones to allow DNS based 
monitoring of API update progress.

The most recent SOA that has been successfully pushed to the Route 53 API 
(whether the change is PENDING or INSYNC) should be the answer.

The Route 53 ListHostedZones API call can enumerate all zones and their HZ ID. 
route53d should use this instead of users listing these in the config file.

Route 53 require the RRSet TTL to be specified in a Change API request but the 
dynamic update protocol means the TTL arrives from the client set to zero. At 
the moment an override TTL is set in the route53d config file.

Need to query the Route 53 API, or do a DNS query, to learn the true TTL and 
remove the config kludge.

There is a typo in the function get_record_set which causes exceptions in the 
script filling logs and causing process hiccups:

----------------------------------------
Exception happened during processing of request from ('10.228.0.1', 34053)
Traceback (most recent call last):
  File "/usr/lib/python2.7/SocketServer.py", line 284, in _handle_request_noblock
    self.process_request(request, client_address)
  File "/usr/lib/python2.7/SocketServer.py", line 310, in process_request
    self.finish_request(request, client_address)
  File "/usr/lib/python2.7/SocketServer.py", line 323, in finish_request
    self.RequestHandlerClass(request, client_address, self)
  File "/usr/lib/python2.7/SocketServer.py", line 638, in __init__
    self.handle()
  File "./bin/route53d.py", line 265, in handle
    response = self.handle_update(msg)
  File "./bin/route53d.py", line 340, in handle_update
    APIRequest.add(rrset)
  File "./bin/route53d.py", line 95, in add
    current_rrset = self.get_record_set(rrset.name, rrset.rdtype)
  File "./bin/route53d.py", line 171, in get_record_set
    or result.next.record_type != qtype):
AttributeError: 'ResourceRecordSets' object has no attribute 'next'
----------------------------------------


See a fix attached.