Cloud DNS
DNS determines which server, application or email service your domain points to. With Cloud Noce DNS, you can add a domain, change nameservers at your domain registrar and create records such as A, AAAA, CNAME, MX and TXT. Before changing important records, note their current values and set TTL according to the sensitivity of the change. Browser, operating system and ISP caches mean users may not all see the new value at the same time.
Important considerations
DNS is separate from domain registration
Cloud Noce hosts the zone and its records. Domain ownership, renewal and nameserver changes still take place through your domain registrar.
Fast updates in Cloud Noce DNS
After you save a record in the dashboard, the change is applied to Cloud Noce nameservers. Query those nameservers directly to check the new value without interference from local caching.
Internet propagation time
Even when a record changes quickly in Cloud Noce, public resolvers, ISPs and users’ devices may retain the old value until its TTL expires. For sensitive migrations, lower TTL several hours beforehand and increase it again after the service stabilizes.
Common records and settings
A and AAAA records
Connect a domain or subdomain to an IPv4 or IPv6 address. Enter the destination service’s IP address exactly.
CNAME records
Point a subdomain to another domain name. For the root domain, A/AAAA records or provider-specific settings are usually used.
MX and TXT records
Used for email, domain ownership verification, SPF, DKIM and DMARC. Preserve quotes and spaces when entering TXT values.
TTL settings
TTL determines how long a record stays cached. Low TTL suits migrations; a higher TTL reduces query volume once the service is stable.
Connect your domain
Add the domain in the dashboard
Enter the domain without http, https or a path. If it already has active records, export or note those records before moving it.
Change the nameservers
Replace the nameservers at your domain registrar with those displayed in the Cloud Noce dashboard. This can take time depending on the registrar and internet caches.
Create the required records
Create the A, CNAME, MX and TXT records needed by your web and email services. Check each record’s name, type, value and TTL individually.
Check propagation
Use dig or similar tools to query the Cloud Noce nameserver directly, then public resolvers, to distinguish cached responses from the authoritative value.
Useful commands
Check the server IP address (A record)
These commands use dig and host to query DNS. They show which public IPv4 address your domain currently resolves to and which server users are directed to.
dig A example.com
host example.comCheck the domain’s active nameservers (NS record)
Run this command to check whether your nameserver change was successfully applied at the registrar and whether the domain points correctly to Cloud Noce’s ns1 and ns2 servers.
dig NS example.com +shortQuery the Cloud Noce server directly without local caching
If your ISP has cached old information, this command sends the query directly to the Cloud Noce authoritative server. It shows the latest recorded values without relying on the local cache.
dig A example.com @ns1.gerdoo.cloud