CuDDNS

Shitty Dynamic DNS, optimised for Shitty Cisco boxes

Why?

Old Cisco hardware supports rudimentary "Dynamic DNS", which is helpful. They don't support modern TLS implementations however, which is less helpful as most providers offering dynamic DNS expect updates to be sent over HTTPS.

CuDDNS accepts updates over good old fashioned HTTP which solves the problem, but introduces new and exciting problems such as sending credentials over plaintext - you might be able to work around this by running a HTTP to HTTPS proxy locally.

We've previously operated an internal DDNS system using noip-rfc2136 and Bind, but maintaining servers is dull so we've gone "Serverless" thanks to Jeff Bezos.

Supported Features

• DNS can be updated with a GET request over HTTP or HTTPS
• No pesky HTTPS redirect
• If the myip parameter isn't provided, the record will be updated to the source of the request - useful behind NAT

Unsupported Features

• Currently only *.dns.c29.uk domains are supported. If you want to use your own domain you can CNAME them, or we might add BringYourOwnDomain support in future.
• There's currently no way to delete, or list created domains.

How can I use it?

If you're mad enough to use it, get in touch to get a username and password

Can I see the source?

Maybe. We're too busy to sanitise it for public consumption right now but if you're desperate we might get round to it.

Disclaimer

This is a terrible idea and there's no guarantees of uptime.

Configuration

Cisco

Here's how you can configure a Cisco box to use the CuDDNS service

ip ddns update method ddns
 HTTP
   add http://user:password@dns.c29.uk/update?hostname=<h>&myip=<a>
 interval maximum 0 1 0 0
 interval minimum 0 0 10 0

interface FastEthernet0/0
 ip ddns update hostname vgw-201.foocom.dns.c29.uk
 ip ddns update ddns

Curl

You could also use Curl, or modify the request for another device

curl "https://user:password@dns.29.uk/update?hostname=vgw-201.foocom.dns.c29.uk&myip=198.51.100.23"