Glauca HexDNS CNAME and A record setup
How to add a CNAME, A or TXT record at Glauca HexDNS: the host for a subdomain and the root domain (@), and how to check it's live.
These are the steps DoDomain's hosted connect flow shows a customer whose domain is managed at Glauca HexDNS, in Glauca HexDNS's own vocabulary. A product using DoDomain never writes them: the connect flow detects the provider, shows these steps beside the exact records to create, and verifies each record against the zone's authoritative nameservers. They are published here for your own support articles, and for anyone who wants to see the steps before they start.
Related definitions: CNAME record, A record, apex domain.
Where the records live
Open Glauca HexDNS's DNS management and pick the domain.
How to add a CNAME or A record in Glauca HexDNS
- Sign in to the HexDNS control panel and open the zone for your domain.
- In the section for the record type (Address records, CNAME records, TXT records), click New.
- Enter Record name and the value field as below (Address for A, Alias for CNAME, Data for TXT), then Save.
- Come back here and click Verify.
What to put in the Glauca HexDNS host field
Enter the subdomain only in Record name (the zone is appended); use @ for the zone root. For a record on the domain itself, enter @.
Whatever the panel calls the field — Name, Host, Hostname — DoDomain's connect flow shows the value to paste into it already in this provider's format, and shows the fully-qualified name it will verify next to it.
Common questions
Where do I add DNS records at Glauca HexDNS?
Open Glauca HexDNS's DNS management and pick the domain.
What goes in the host field at Glauca HexDNS?
Enter the subdomain only in Record name (the zone is appended); use @ for the zone root. For a record on the domain itself, enter @.
How do I check that a record at Glauca HexDNS is live?
Look the name up with the free DNS lookup, which shows the authoritative answer next to what public resolvers return. DoDomain verifies against the authoritative nameservers, so a record can be correct there while resolvers still serve the old answer until its TTL expires.
Check the record is live
A saved record is not yet a live record. DoDomain verifies against the zone's authoritative nameservers, which answer as soon as the provider publishes the change; public resolvers can lag behind for as long as the old answer's TTL. The free DNS lookup shows both answers side by side for any name, and the provider detector tells you which provider serves a domain and whether a one-click path exists for it.
If you are the product asking for this record
You do not have to send customers here. Mint a connect session and the hosted flow shows these steps to your Glauca HexDNS customers on its own, then verifies and keeps monitoring the records — see the connect flow and the framework guides for Next.js, Rails, Laravel and Django. A customer who wants their bare domain rather than a subdomain is the apex question, which no provider panel solves on its own.
Vocabulary checked against Glauca HexDNS's own help page on 2026-10-22: https://github.com/AS207960/hexdns/blob/master/hexdns_django/dns_grpc/templates/dns_grpc/fzone/zone.html.