Overview
This guide covers common issues and best practices when using the DNS Zone Editor in our Cloud Control Panel. The domain example.com will be used for examples.
Important Rule
When entering a fully qualified domain name in the DNS Zone Editor, you should always end the domain with a '.' character (e.g., test.example.com.).
Nameservers
Use these nameservers with our cloud DNS Zones:
dns1.ramnode.comdns2.ramnode.comdns3.ramnode.comCreating Records for the Root Domain
Some DNS software allows you to use the @ character as a shortcut to example.com., but for the Cloud DNS Zone Editor, you must specify the entire fully qualified domain name instead.
@example.com.
Creating Records with Spaces
SPF and DMARC records often require spaces to separate entries. For records with spaces, you must enclose the entire record in double quotes.
_dmarc.example.com. 3600 TXT v=DMARC1; rua=mailto:admin@example.com; fo=1; p=none;_dmarc.example.com. 3600 TXT "v=DMARC1; rua=mailto:admin@example.com; fo=1; p=none;"
Creating Multiple MX Records
When creating a second or backup MX record (or other record type with an existing entry), use the correct plus (+) button to avoid overwriting existing records.
Important
Click the plus (+) sign on the right side of the existing record, NOT the plus (+) at the bottom of the page. Using the bottom plus will overwrite existing records with the same root and type.
Pro Tip
Always test your DNS records after making changes. Use tools like dig or nslookup to verify that records are propagating correctly. DNS changes can take up to 48 hours to propagate globally.