Transfer a domain Help
WHOIS lookup DNS records Price list Transfer a domain
English Русский
Find a domain
Domains
Pricing
Transfer
WHOIS
DNS
Blog
Company
Contacts

DNS and nameservers

A domain on its own points nowhere. DNS is what connects it to a site, a mailbox or a service, and it is included with every name registered through Apply.

.com$8.98 .net$13.98 .org$12.48 .io$42.00 .co$28.00 .dev$15.00

No account needed to check a name. Registration takes minutes once the invoice is paid.

Records you will actually use

Five record types cover almost every setup. The rest exist for cases you will know when you meet them.

Record What it does Typical value
APoints the domain at an IPv4 address of a server203.0.113.10
AAAAThe same for IPv62001:db8::10
CNAMEMakes a subdomain an alias of another namewww to yourbrand.com
MXSends mail for the domain to a mail providermx.provider.net, priority 10
TXTHolds verification strings, SPF and DKIM for mailv=spf1 include:provider.net ~all
NSDelegates the whole zone to a set of nameserversns1.apply.domains

Pointing a domain at hosting

Two ways to do it. Pick one and stay with it, because mixing them is where most broken setups come from.

01

Keep DNS with us

Leave the nameservers as they are and add an A record with the address your hosting gave you. Changes take effect within minutes.

02

Or delegate the zone

Replace the nameservers with the ones your hosting provides. From that moment every record lives in their panel, not ours.

03

Set up mail separately

MX records are independent of the site. Mail can sit with one provider while the site runs somewhere else entirely.

04

Wait for propagation

Resolvers cache answers for as long as the TTL says. Lower the TTL a day before a planned move and the switch becomes almost instant.

Questions that come up during a move

Our nameservers publish a change immediately, but resolvers around the world keep the old answer until the TTL expires. With a TTL of one hour that is the worst case. Changing nameservers themselves is slower, because registry data propagates for up to a day.

Different resolvers hold different cached copies during propagation. It resolves itself once the TTL runs out everywhere. Flushing the local DNS cache helps on the machine you control.

Yes. www is a subdomain and needs its own A or CNAME record. The usual setup is an A record on the bare domain and a CNAME for www pointing at it.

Almost always because the zone was delegated to a new provider and the MX records were not copied over. Write down the MX and TXT records before switching nameservers, then recreate them on the new side.

Want us to set the records up?

Send the domain and where it should point. We configure DNS and mail records and check that everything resolves.

Answer time
Within one business day