Another alternative would be to set up your Linode as the authoritative for the relevant zone(s), and set the Linode DNS as slaves. They could still be the NS machines for the zone(s), to avoid your Linode being a single point of failure, but it would let you administer the DNS zone however you might like, and with whatever tools or custom code, locally on your Linode.
When Linode first set this up, the zone transfers could lag a fair amount and AXFR was open to everyone. Now you'll typically be updated within a few seconds of sending out the notifies and AXFR can be closed. I'm even doing reverse DNS for my IPv6 /48 with this. It works quite well.
The web interface is probably easier for simple or infrequently updated zones, my main reason for doing zone transfers is a dynamic zone.