commerce_domains 1.0.3

New features

URL redirects in DNS templates, for any registrar

• New record type: DNS templates have a URL redirect, any registrar type. Applied to a domain, it becomes that registrar's own redirect, each as a 302:
  • a forward on Dynadot
  • a URL record on GNAME and Namecheap
• One template for every registrar: a redirect to https://example.com/domain/{domain} works for domains at different registrars.
• Replaces the host's current redirect: when keeping existing records, the template's redirect takes the place of the CNAME or forward already on that host.
• Registrars without a redirect in their DNS API (GoDaddy, NameBright, NameSilo, Porkbun, Spaceship) leave it out, with a warning.
• Validation: the template form checks that a redirect's value is a web address.

DNS records at NameBright

• DNS tab: domains at NameBright now get a DNS tab, and DNS templates and the Apply a DNS template bulk action work for them.
• Which domains: only those on NameBright's own nameservers (*.namebrightdns.com). Others say their reco
• Record types: A, AAAA, CNAME, MX and TXT can be added and removed, one record at a time, so the records that stay are never touched. Existing SRV records are kept as they are.
• No TTL: NameBright's API has no TTL field, so a record with a TTL is refused before anything is written.
• URL forwarding: NameBright forwards with a CNAME to its own forwarder, and the address is set in the NameBright account, not through the API.

Documentation

• New README section: DNS templates covers the DNS tab, the bulk action, {domain} and how redirli>
• DNS records table: now includes NameBright, with its limits.

Upgrading

• No database updates or configuration changes. NameBright domains get the DNS tab as soon as the code is updated, fons at registrars.
• Templates from 1.0.2 keep working. To use a redirect in one, add a URL redirect, any registrar record.