DO Ideas 2

DNS Templates

Each DNS Template will be created by the user and will have a set of common records for his domains.

We could apply a DNS Template to a domain to save us from having to add each record manually.

  • Anonymous
  • Sep 11 2018
  • Will not implement
  • Attach files
  • Dave Rogers commented
    September 11, 2018 18:13

    Whaaat - this would've been awesome. Examples:

    * Swapping out "ns1.digitalocean.com (etc.)" for vanity nameservers
    * CNAME to redirect www.domain.tld to domain.tld
    * Google MX records
    * Outlook.com Mail (which was a HUGE pain in the butt! MS continues to be awful at everything.)

    I'm appreciative that there is a pretty great API to do these things as well; just would be nice to avoid building-out scripts just for things I think are pretty basic. The Google MX one is something I see on most DNS services.

  • Lewis Goddard commented
    September 11, 2018 18:13

    I have a CName Record set to " * @ " and an A Record set to " @ MY.IP.HE.RE " That way i can redirect invalid sub-domains to the apache default.

  • Matheus commented
    September 11, 2018 18:13

    +1

  • Moisey Uretsky commented
    September 11, 2018 18:13

    We don't have any plans to offer a slave DNS service through our nameservers as it can cause a large number of conflicts with the records that are stored by customers directly.

  • Biji commented
    September 11, 2018 18:13

    I prefer the give slave dns service :)

  • Moisey Uretsky commented
    September 11, 2018 18:13

    Whats the catch all record that you usually setup ?