New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make it easy to add A and PTR records as a pair #51

fastcat opened this Issue Jul 29, 2015 · 2 comments


None yet
2 participants
Copy link

fastcat commented Jul 29, 2015

Since A and PTR records are very often paired, it would be convenient to be able to add them as a pair. Auto-detecting the PTR zone would be nifty, but not absolutely necessary.

Even cooler would be the ability to edit them as a pair, but that's rather more difficult.


This comment has been minimized.

Copy link

tuxis-ie commented Jul 30, 2015

That sounds like a good idea. Do you have any idea how you would like to see that implemented? It's not based on a zone, so it would be an extra option in a tools section in the menu or something like that?


This comment has been minimized.

Copy link

fastcat commented Jul 30, 2015

I see two "natural" ways to do it.

One: Make it an "extension" to the box for adding an A / AAAA record to a zone -- e.g. if you select one of those, have extra fields that appear for adding the PTR record. The zone in which to place the PTR record could be a drop-down, with a little javascript to try to auto-select the correct zone based on the content for the A/AAAA record. I don't think a separate TTL field would be necessary, use the same TTL for both records.

Two: A top level option as you suggest, with similar javascript to try to auto-select both zones.

The UI for option two is probably a bit cleaner, though it does require two variants of the zone auto-selector js.

As far as placement of the link, for option 1 it's embedded into the existing UI. For option 2, I think the most natural placement would be another "tab" button alongside the import and add zone buttons.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment