How to update an A record

Quick answer: An A record maps a hostname to an IPv4 address. To update it, open your DNS provider's control panel, edit the record's value to the new IP (for a Cloud2Y server — the Dedicated IP from your Client Area), save, and wait for the old TTL to expire.

Overview

The A record is the most common DNS record — it decides which server answers when someone opens your domain. You change it when moving a site to a new server, adding a subdomain, or fixing a typo in the IP.

Before you start

• The new IPv4 address (your Cloud2Y Dedicated IP is on the service page).
• Access to the DNS management panel that is authoritative for the domain.
• Optional but smart: lower the record's TTL to 300 seconds a few hours in advance, so the switch is fast (why this helps).

Step-by-step guide

1. Log in to your DNS provider and open the domain's zone/records page.
2. Find the A record you need: host @ for the bare domain, or the subdomain name (e.g. blog).
3. Replace the value with the new IPv4 address.
4. Keep or set a sensible TTL (300–3600 seconds is typical).
5. Save the zone and verify:

dig +short A example.com
dig @8.8.8.8 +short A example.com   # what Google's resolver sees

Common issues

• Still resolving to the old IP: caches hold the old value for the previous TTL — this is normal, not an error.
• Multiple A records: if two values exist, browsers may hit either server; delete the stale one.
• Subdomain typo: creating www.example.com.example.com by entering the full name where the panel expects only the host part.

When to contact support

A record edits happen at your DNS provider, but if you are unsure which IP to use for your Cloud2Y service, or the site misbehaves after the switch, open a ticket — we will confirm the correct address.

Frequently asked questions

What does an A record do?

An A record maps a hostname such as example.com to an IPv4 address, deciding which server answers when visitors open that name in a browser or an app connects to it.

What TTL should I set for an A record?

For stable sites 3600 seconds (1 hour) is a good default. Before planned migrations, lower it to 300 seconds a day ahead so the switch to the new IP happens within minutes.

Why does the old IP still load after I changed the record?

Resolvers keep the previous value until its TTL expires. This is normal caching behaviour, not an error — the old address disappears once the timer runs out.

Related articles

• How to point a domain to Cloud2Y VPS
• How to update an AAAA record
• How long does DNS propagation take?
• Common DNS mistakes

Ready to get started? Order a VPS at Cloud2Y →