Domains and DNS for a server owner

You can switch servers in an evening, but a domain stays with a project for years. Through DNS, the domain points to your server, your mail and third-party services, and a single wrong record can take the site offline or send your emails to spam. Here are the records a VPS owner will need, how caching works, where to keep the zone and how to move to a new server without visitors noticing.

Updated 06.11.2026 · Find a VPS for your needs →

A domain has three independent parts, and it helps to tell them apart. The registrar sells and renews the domain itself. The DNS servers listed at the registrar in the NS records host the zone, the list of the domain's records. The host provides the server with the IP address those records point to. All three roles can be played by one company or by three different ones, and that determines what you will have to change when you move.

The main DNS records

  • A is the server's IPv4 address for a name (RFC 1035). A website usually needs two: one for example.com and one for www.example.com.
  • AAAA is the same for IPv6 (RFC 3596). Add it only if the server really responds over IPv6: browsers try this address first, and broken IPv6 causes delays for some visitors. More on this in the article IPv4 and IPv6 on a server.
  • CNAME is an alias: one name points to another name, for example www to example.com or a subdomain to a CDN address. Under RFC 2181, a name with a CNAME cannot have any other records, so a CNAME is not placed on the bare domain: it already has NS and SOA records. Some DNS providers work around this with their own ALIAS or ANAME types, but that is an extension of a particular service, not a standard.
  • MX lists the servers that receive the domain's mail, with a priority: the lower number is the primary. An MX record must point to a name with an A or AAAA record, not to an IP address and not to a CNAME.
  • TXT holds arbitrary text. It is used for SPF, DKIM and DMARC for mail and for domain verification codes for search engines and other services. How to write the mail records is explained in the article Mail server on a VPS: SPF, DKIM, DMARC.
  • CAA specifies which certificate authorities may issue certificates for the domain (RFC 8659). The record is optional, but if it exists, an authority not named in it will refuse to issue. Certificates are covered in the article SSL certificates: free and paid.

A typical zone for a site on a VPS with mail at a third-party service looks like this: A and AAAA records for the domain and www, the mail service's MX, TXT with SPF and DMARC, CNAME or TXT for DKIM and a few TXT records with service verifications.

TTL: why changes do not show up immediately

TTL is the time in seconds for which the DNS servers of internet providers and visitors' devices remember an answer (RFC 2181, section 8). Until it expires, they do not query the zone again, so a new record reaches everyone no sooner than the TTL of the old one. That is where the common saying "DNS takes up to 72 hours to update" comes from: in reality, everything depends on the TTL you set yourself.

  • 3,600 seconds (an hour) is a sensible value for normal operation;
  • 300 seconds is for the period of a move or setup, when you may need to change the address quickly;
  • a day or more is for records that do not change for years, such as MX.

The absence of a record is cached too. If you query a subdomain before you have created it, the negative answer is remembered for the period set in the zone's SOA record (RFC 2308), often an hour. So create the record first and only then check it.

NS records at the registrar are a special case. Their TTL is set not by the domain owner but by the top-level zone. A query to the zone servers on 6 November 2026 showed that NS records for .com domains are cached for 172,800 seconds, that is two days, and for .ru domains for 345,600 seconds, four days. Changing a domain's DNS servers therefore always takes longer than changing an A record.

PTR: the reverse record for mail

Ordinary records translate a name into an address, while PTR translates an address into a name: 203.0.113.10 → mail.example.com. It does not live in your domain's zone but in the address zone in-addr.arpa or ip6.arpa, which is managed by the owner of the IP address, that is, the host. You set it in the host's control panel or through support.

A website does not need PTR, but mail does: Google requires senders to have a PTR record for the server's IP address and for the name in it to point back to the same address. Before buying a VPS for mail, check whether the host lets you change PTR and whether outgoing port 25 is open; such servers are collected in VPS for a mail server.

Where to keep the zone: registrar, host or a separate DNS service

  • At the registrar. Free and independent of the host: when you change servers, you change one A record. The downsides are a limited choice of record types, no API or a restricted one, and response speed that depends on the registrar's infrastructure.
  • At the host. Convenient when everything is in one panel, and some hosts fill in the zone for you. But if you move to another host, you will have to move the zone as well, and if the account is suspended or there is a dispute, DNS becomes unavailable along with the server, and with it your mail and all subdomains.
  • A separate DNS service. Servers in different countries with anycast, fast responses, an API for automation and for issuing wildcard certificates, and a change history. Many offer free basic plans. It suits projects with several servers or those that use a CDN.

The rule for every option: the registrar account and the domain must belong to the project owner, not to a contractor or the host. According to the accsly.io catalog as of November 2026, a free domain is mentioned in 494 shared hosting plans from 153 of 1,655 hosts, usually with annual payment. Before accepting such an offer, find out in whose name the domain is registered and how much it costs to renew in the second year. Hosting plans are collected in the section Website hosting.

Protect the domain itself as you would money: two-factor login at the registrar, auto-renewal with a valid card and an up-to-date owner email. Under the current ICANN rules, a domain in generic zones such as .com cannot be transferred to another registrar for 60 days after registration or a transfer, so it is better to choose the registrar right away.

How to move a site without downtime

  1. A day or two in advance, lower the TTL of the A and AAAA records to 300 seconds and wait for the old TTL to expire.
  2. Prepare the new server and test the site on it before changing DNS: curl --resolve example.com:443:203.0.113.10 https://example.com/ or an entry in the hosts file on your computer.
  3. Change the A and AAAA records to the new address. Within a few minutes most visitors will be on the new server.
  4. Do not switch off the old server for at least a day: devices with the cached address will still connect to it. If the site accepts data, make the old copy read-only for the duration of the move so that orders and comments do not end up split between two databases.
  5. Restore the TTL to its normal value once everything works.

The full procedure for moving files, the database and mail is described in the article How to move a website from shared hosting to a VPS.

If you are changing the domain's DNS servers along with the server, do it as a separate step. First copy all the records to the new zone and compare the answers from the old and new servers: dig @new-ns example.com MX, and so on for each record type. Only then change the NS records at the registrar, and keep the old zone working for at least the delegation TTL: two days for .com and four for .ru. If DNSSEC is enabled for the domain, remove the DS record at the registrar before changing NS or migrate the keys following the scheme in RFC 6781: otherwise DNSSEC-validating resolvers will stop resolving the domain.

How to check

The command dig example.com A +short shows the current answer, while dig example.com A +trace shows the path from the root servers to yours and helps you find which server is returning the old record. dig -x 203.0.113.10 checks PTR. To see the TTL remaining in a particular resolver's cache, query it directly without +short. If the site is behind a CDN, the A record will point to the CDN rather than to your server; how this works is explained in the article CDN: when a website needs one.

FAQ

How long does DNS take to update after a record change?

As long as the TTL of the old record: with a TTL of 300 seconds, about five minutes; with a TTL of a day, up to a day. Changing a domain's DNS servers at the registrar takes longer: NS records are cached for two days for .com and for four days for .ru.

What is the difference between an A record and a CNAME?

An A record points a name to an IP address, while a CNAME points it to another name, whose address is then taken from that name's records. A CNAME cannot be placed on the bare domain; only A and AAAA can.

Where is it better to keep DNS: at the registrar or at the host?

If you have one server and rarely change it, the registrar's DNS is enough, and it does not depend on the host. A zone at the host is convenient, but you will have to move it if you leave. A separate DNS service is needed when there are several servers, a CDN or a need for automation via an API.

Who sets up the PTR record?

The owner of the IP address, that is, the host: in the server control panel or on request to support. You cannot create a PTR record in your own domain's zone.

How do I move a site to another server without downtime?

A day in advance, lower the TTL to 300 seconds, test the site on the new server via the hosts file, change the A and AAAA records and keep the old server running for at least another day.

Do I need an AAAA record if the server has IPv6?

Yes, if the site on the server actually responds over IPv6 on ports 80 and 443. If IPv6 is assigned but the web server does not listen on it, it is better not to add the AAAA record: some visitors will get delays and errors.

Plans on this topic

VPS for a websiteVPS for WordPressVPS for an online store

More in the guide

  • CDN: when a website needs oneA CDN stores copies of a site's files on servers around the world and delivers them to each visitor from the nearest one. This speeds up loading of images, scripts and video and takes load off your server, but it does not make a slow CMS faster and does not replace choosing the right country for your server. Here is when a CDN is really needed and when a single VPS in the right place is enough.
  • SSL certificates: free and paidA free certificate encrypts the connection just as reliably as a paid one: browsers make no distinction between them in terms of security. The difference lies in what the certificate authority checks, how long the certificate lasts and who is responsible for renewing it. According to the accsly.io catalog as of November 2026, free SSL is explicitly listed in 1,449 shared hosting plans from 178 hosts. Here is when that is enough and when a certificate is worth paying for.
  • 152-FZ and hosting: where to store the dataIf a website or service collects personal data of Russian citizens, that data must be recorded and stored in databases located in Russia: this is Part 5 of Article 18 of Federal Law No. 152-FZ. For choosing a VPS, this means the data centre's country matters, not the host's, and copies abroad fall under separate rules. Here is what the law requires, what duties fall on the server owner, how it applies to companies outside Russia and which setups are used in practice.
  • GDPR and choosing a hostThe EU General Data Protection Regulation (GDPR) does not require data to be kept in the EU, but it does require a data processing agreement with the host and a lawful mechanism for any transfer of data out of the EU. According to the accsly.io catalog as of November 2026, 61% of VPS hosts have servers in the EU, but almost half of them are registered outside the European Economic Area. Here is why that matters and what to check in the terms.
  • Hosting provider jurisdiction: what it affectsEvery server has two countries: the one where the data centre stands and the one where the company renting it out is registered. According to the accsly.io catalog as of November 2026, these are different countries for 15% of VPS hosts. The first determines latency and the rules on where data is stored; the second determines the law of the contract, the court for disputes, the documents your accountant receives and whose authorities can request your data. Here is what each of them changes.
  • How to compare VPS prices: the price of a resource unitA plan's price tells you how much you will pay, but not how much you get for that money. According to the accsly.io catalog as of November 2026, a gigabyte of memory on a 1 GB plan costs a median $8.00 a month, while on a 4 GB plan it costs $5.00. Here is how to work out the price per vCPU, per gigabyte of memory and of disk, and what to bring to a common basis before you compare two offers.
  • SLA and uptime: what hosts promiseAn SLA of 99.9% allows a host 43 minutes of downtime a month, 99.99% about four. But a percentage in an advert is not yet a commitment: the commitment is the document that says what counts as downtime, what is excluded and how much you get back. Most often that is a discount on the next invoice, not money. Here is how to read such documents and how to check availability yourself.
  • Free trials and money-back guaranteesThere are two ways to test a server before paying for a month or a year: a free trial or a money-back guarantee. According to the accsly.io catalog as of November 2026, 11% of VPS hosts offer a trial and 36% a money-back guarantee. But at many of them the terms apply only to shared hosting, only to the first order or only to card payments. Here is what to check so that the guarantee actually works.
  • Cloud server or VPSA cloud server and a VPS are usually the same KVM virtual machine. The difference lies in what surrounds it: a cloud sells resources by the hour through an API and offers network disks, snapshots and ready-made services, while a classic VPS is a fixed monthly plan with a local disk and a traffic allowance. Here is which of this you actually need and what it costs.
  • Dedicated server or VPSA VPS is a slice of a physical server, a dedicated server is the whole machine. With 4 cores and 8–16 GB of memory a VPS costs almost half as much, with 4 cores and 32 GB the prices are equal, and with 64 GB on 8 cores or 128 GB on 16 cores a dedicated server in the catalog is a third cheaper than a virtual one. Here is what else changes besides the price: neighbours, guarantees, delivery time, hardware failures and remote management.
  • Shared hosting or VPS for a websiteShared hosting is a ready place for a site where the host looks after the server. A VPS is your own server where you set everything up. For a landing page or an ordinary WordPress site, hosting is enough and costs several times less. You need a VPS when the account limits are too tight for the site or when it needs software that hosting does not allow. Below is what each option includes, what it costs and a table to help you choose.
  • DDoS protection: what hosting providers actually give youEvery second host now lists "DDoS protection" in its plans. Behind that line there may be multi-terabit filtering, or only the right to take your address offline when an attack bothers the neighbours. Here is what protection is made of, how L3/L4 differs from L7, and how to tell from the contract what you are buying.
  • Mail server on a VPS: SPF, DKIM, DMARCInstalling Postfix or a ready-made bundle like Mailcow on a VPS takes an hour. Getting your mail into the inbox rather than spam is harder: mailbox providers look at the port, the server's address, its reputation and three DNS records. Here is what to check with the host before buying and how to set up SPF, DKIM and DMARC.
  • Server monitoring: uptime, load, alertsWithout monitoring you learn that the server is down from your visitors, and that the disk is running out when the database stops writing. A few checks from outside and a dozen metrics from inside are enough to see a problem before users do. Here is what to measure, where to run checks and how to do it for free.
  • How to read hosting plans: the hidden limitsA plan card shows cores, memory, disk and a monthly price. Yet two plans with identical numbers can cost different amounts a year later and behave differently under load. The difference lies in terms printed in small type, in the acceptable use policy, or only in the contract. Below are eight places worth checking before you pay.
  • IPv4 and IPv6 on a serverA typical VPS has one public IPv4 address and, if the host supports it, an IPv6 subnet. An extra IPv4 address almost always costs money, and the cheapest plans sometimes come without their own IPv4 at all. Here is where the shortage comes from, what you can do with IPv6 alone and which address settings a mail server needs.
  • Bandwidth and traffic: what 1 Gbps and unlimited really meanA server plan usually has two network lines: port speed and traffic volume. The first says how fast the server can send data, the second how much it can send in a month. They are linked by simple arithmetic, and once you know it, it is easy to see what "1 Gbps unlimited" actually offers and whether "5 TB" will be enough for you.
  • Docker on a VPS: getting startedDocker lets you run a bot, a website, a database and monitoring on one server without them getting in each other's way, and moving to another VPS comes down to copying a couple of files and the data. Installation takes five minutes; the real trouble starts later: database ports exposed to the internet, logs growing to tens of gigabytes and data that vanished along with a container. Here is how to avoid all of that from the start.
  • How to move a website from shared hosting to a VPSThe move itself takes a couple of hours; the mistakes usually happen around it: a forgotten cron job, .htaccess rules that nginx does not read, an AAAA record with the old address, or mail that disappeared along with the IP change. Below is the order of steps with commands and checks for a PHP and MySQL site.
  • Server control panels: ISPmanager, FASTPANEL, aaPanelA panel turns a VPS into the kind of dashboard you know from shared hosting: sites, databases, mail and certificates are set up with a few clicks instead of editing config files. The three panels most often installed on Russian and budget international servers are ISPmanager, FASTPANEL and aaPanel. They differ in price, memory requirements and how much of the server they take over.
  • Windows VPS for 1CA rented server for 1C saves you from the office PC under a desk that nobody updates or backs up. But 1C on a VPS has its own quirks: the software licence is tied to the parameters of the virtual machine, users need both 1C and Windows licences, and core speed matters more than core count. Here is how to put together a 1C server for a small company.
  • Windows VPS: licensing, RDP and secure sign-inA Windows server costs more than Linux not only because of memory: the price includes a licence, and how it is arranged decides whether you are compliant and how many people can connect. An exposed RDP port is also the most common way such servers get hacked. Here are both topics.
  • When to move from shared hosting to a VPSA VPS does not make a site faster by itself: it gives you resources and freedom, and with them the job of running a server. Here is how to tell that hosting has become too small, when the problem can be solved without moving, and how to migrate a site so visitors notice nothing.
  • VPS backups: strategies and toolsOn a VPS, backups are your job, even if the plan says "backups included". We go through what exactly to back up, why a host snapshot is not enough, how to set up restic or BorgBackup in half an hour, and how to make sure you can actually restore from a backup.
  • First 10 steps after buying a VPS: securityBots start guessing passwords on a new server within minutes of it getting a public IP. Below are ten steps that close the most common holes in about an hour: commands for Ubuntu and Debian, the differences for AlmaLinux and Rocky Linux, and the checks that keep you from locking yourself out of your own server.
  • How to choose a country for your serverPut the server where your visitors are. For an audience across Europe, Germany, the Netherlands and Finland are convenient; for North America, the US East Coast. If you serve EU users, keeping the data in the EU makes GDPR simpler. Price hardly decides it: at the same host a server in Frankfurt, Amsterdam or New York usually costs the same, and only Asia and Australia are noticeably more expensive.
  • Hourly billing: when it pays offHourly billing pays off if you need the server for less than three weeks a month: for a test, a build, a one-off heavy job. At most hosts an hour costs exactly the monthly price divided by 730 hours, so over a full month you hardly overpay. The overpayment hides elsewhere: hourly plans are dearer on average, and for a server that runs all year, monthly billing or a year paid in advance usually comes out cheaper.
  • How much RAM and how many cores a website needsMost websites are fine with 2 GB of memory and one or two cores; a shop with thousands of products needs 4 GB and two cores. Memory matters more than cores: when it runs out, the site slows down or crashes, while an extra core without memory adds almost nothing. Below I show how to work out the memory for your site and how to see what it actually uses.
  • KVM or OpenVZ: which to chooseIn 2026 KVM is almost always the right pick: it costs a dollar or two more per month than OpenVZ, but everything runs on it, from Docker to Windows. OpenVZ makes sense in one narrow case, explained below, and at the end you will find the commands to check your own server in a minute.
  • NVMe or SSD: does it matter for a websiteFor a small site the difference between NVMe and SSD is barely noticeable, because pages are served from memory rather than from disk. It shows up in shops and sites with a large database. At the same host NVMe costs only about $0.50–1 a month more, and sometimes less, so what usually decides it is not the disk type but its size and how the host has limited it.
  • What is a VPS, in plain EnglishA VPS is a slice of a powerful physical server that you rent and that behaves like a separate computer, with its own operating system, its own IP address and full control. Below is how it differs from shared hosting, who needs one, what it costs and what to check right after you buy it.
  • VPS for a Telegram bot: what the bot needs and how to pick a planA bot with a menu and a few commands runs fine on the cheapest server, while a bot with broadcasts, files and a database hits completely different limits. Here is what a bot really consumes, which Telegram limits shape the choice of server and how to avoid overpaying.
  • How to test VPS ping and speed before you payThe numbers in a plan do not tell you the latency to your users or how fast the disk really is. Most of this can be measured before you pay, the rest in the first hour after launch. Here are the tools and how to read the results.
  • Corporate network on a VPS: remote access to the officeA rented server can become the hub of a company's private network: remote employees and branch offices connect through it to the ERP, file server, CRM and Git. Here are the common layouts, protocols, server requirements and security basics.
  • How to choose a VPS: the 7 specs that matterTwo plans with the same "2 cores, 4 GB, 50 GB" can differ several times in speed and twice in price a year later. Here is what stands behind each line of a VPS plan and what to check before you pay.
  • VPS vs VDS: is there a difference and what actually mattersIn most markets VPS and VDS mean the same thing: a virtual server. The difference that really affects your work is hidden not in the name but in the virtualization type and whether resources are guaranteed.