DNS records: what they are and how they work
DNS (Domain Name System) translates a domain name into the addresses and information that browsers, mail servers and other services need – for example which IP address a website visitor should reach, or which server should deliver an e-mail. A domain does not point anywhere by itself; that is determined by the DNS records in its zone.
Nameservers
A nameserver is a server that answers DNS queries for a domain – it holds its zone with all the records. A domain has, at its registrar, a setting for which nameservers are responsible for it (delegation).
CloudWeb runs its own nameservers:
ns1.cloudweb.skns2.cloudweb.sk
If a domain uses these nameservers, you manage its DNS zone directly in the CloudWeb panel – see Editing DNS records in the panel.
Domain registered elsewhere
If your domain is registered with another registrar, you have two options:
- Point the domain's nameservers at CloudWeb – at your registrar, change the nameservers to
ns1.cloudweb.skandns2.cloudweb.sk. From then on you manage the DNS zone in the CloudWeb panel. - Keep DNS at your current provider – add the domain to your account as "I have the domain elsewhere" and manually copy the records you need (for e-mail or your website, for example) into the zone at your existing provider.
The full walkthrough for both paths is in Domain registered elsewhere.
Main record types
| Type | Purpose |
|---|---|
| A | Points a name (e.g. @ or www) at an IPv4 address of a server |
| AAAA | Same as an A record, but for an IPv6 address |
| CNAME | An alias – redirects one name to another domain name instead of an IP address |
| MX | Specifies which server receives e-mail for the domain, including a priority |
| TXT | Arbitrary text attached to a name – used for things like SPF, DKIM, DMARC or domain-ownership verification |
| NS | Specifies which nameservers are responsible for a (sub)domain |
| SRV | Points at a server and port for a specific service (for example automatic mail-client configuration) |
What gets created automatically with a hosting
When a domain uses CloudWeb's nameservers and is attached to a hosting, the system automatically adds to its zone:
- an A record for
@(the root domain) – pointing at the hosting server's IP address - an A record for
www– pointing at the same IP address - an A record for
*(wildcard), if the hosting is configured so that all subdomains serve the main site - mail records for the domain (an MX record and supporting TXT records such as SPF and DMARC), if a mailbox is attached to the domain
An AAAA record (IPv6) is not created automatically. If you need an IPv6 address, add an AAAA record by hand – see Editing DNS records in the panel.
How long changes take to show up
When you change or add a DNS record, not every visitor sees it right away – browsers and internet providers cache DNS answers for the length of time set by the record's TTL (Time To Live), specified in seconds. Until a cached answer expires, some visitors may still see the old value for a while. Changing nameservers at your registrar also propagates across the internet gradually rather than instantly.
If you are planning a bigger change (such as moving your website), it is common practice to lower that record's TTL beforehand so the change takes effect faster once you make it.
Was this article helpful?
Your feedback helps us improve our documentation