I was managing my DNS today and getting rid of an A record. When I click Delete, I get this confirmation:

===

DNS Manager

Edit Domain - "xxxxx.com" - Edit Resource Record
Are you sure you want to delete this A record?

====

It would be very helpful for the confirmation page to include the name of the A record that is going to be deleted -- as a way to help the end-user really know that he's doing the right thing. As it is, I could be confirming the deletion of the A record above or below the one I really want -- if I had clicked the wrong one, that is.

_________________
http://ultramookie.com/

I was managing my DNS today (like ultramonkey), adding a bunch of MX Records (google's)
Adding 7 MX records for each domain with Linode DNS Manager is really painful That'll be good if you people add an add more action using ajax for each "Add a new X record" pages

Thanks
K.

A vote for both of those!

Although adding the 7 MX records for Google at Linode is still better than GoDaddy, Pair, PairNIC and zoneedit.

Very cool! Thanks for sharing. I'll be using this for the 4 domains I'll ultimately be bringing over to Linode.

Still wish the interface would get a bit more ajaxified

For example if you want to delete 2 records, it's 4 page reloads. It would be nice if you clicked remove, then a dialog box just popped up to confirm, then that entry just goes away if you click Yes. No full page reload.

Perl & Phyton examples are great!
Thanks mwalling.

Maybe i'll write some code with php using Linode API.
When i get over my laziness!

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.

-- David

David, thanks for the info. Thats another good idea.

Totally agree. Usually I am managing my domains with care, but it improves usability a bit.

Try it again. Is that better?

_________________
Disclaimer: I am no longer employed by Linode; opinions are my own alone.

Absolutely, thanks!

++

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.

This works well, with one caveat; your Linode is still the single point of failure for updating the zone. If, for example, you have two linodes (or a virtual server elsewhere... blasphemy!) with the second one acting as a warm standby then if your linode dies you won't be able to do the DNS changes required to send people to the standby.

If this doesn't concern you then what David described is a good configuration.

_________________
Rgds
Stephen
(Linux user since kernel version 0.11)

How I get around that is I make both of my nodes be masters. You can set many masters in the DNS manager. This way, it will fetch the zone from either.

Dynamic, you say?