Knowledge Base

How to Point a Domain to a VDS Server

After purchasing a VDS server and installing your website, you need to point your domain name to the IP address of the VDS.

For example, if you want visitors entering example.com to reach the website hosted on your VDS, the appropriate DNS records must be configured.

In this guide, we explain how to point a domain to a VDS using an A record, configure the www hostname, and troubleshoot common DNS issues.

What Does Pointing a Domain to a VDS Mean?

Servers communicate over the internet using IP addresses.

For example, your VDS may use:

192.0.2.10

Instead of requiring visitors to remember this IP address, DNS allows them to use:

example.com

The basic relationship becomes:

example.com → 192.0.2.10 → VDS Server

An A record is commonly used for this purpose.

What Is an A Record?

An A record connects a domain or hostname to an IPv4 address.

For example:

This points:

example.com

to 192.0.2.10.

The @ symbol commonly represents the root domain, although the exact interface may vary between DNS providers.

What Information Do You Need?

You primarily need:

Domain:
example.com

VDS IP address:
192.0.2.10

Your VDS IP address is normally available from your hosting control panel or server information.

1. Open Your DNS Management Panel

Log in to the service currently responsible for your domain's DNS.

Look for a section such as:

DNS Management

DNS Records

DNS Zone

or:

Zone Editor

If your domain uses nameservers belonging to another DNS provider, make the changes at that provider rather than at the domain registrar.

2. Create an A Record for the Root Domain

Create a DNS record similar to:

Save the record.

Your root domain will then point toward the VDS IP address.

3. Configure the www Hostname

If you also want:

www.example.com

to work, create a DNS record for www.

A common configuration is:

Alternatively, www can use its own A record pointing to the same IP.

Using a CNAME can make management easier because www follows the root hostname.

4. Check for Old A Records

If your domain was previously hosted elsewhere, an old A record may still exist.

For example:

@ → 198.51.100.20

Check that the root domain points to the intended VDS.

Do not randomly delete other DNS records.

Records such as:

• MX
• TXT
• SPF
• DKIM
• DMARC

may be required for your email service.

5. Wait for DNS Propagation

DNS changes may not become visible across every network immediately.

This process is commonly known as DNS propagation.

Some DNS resolvers may see the new record quickly, while others may temporarily continue using cached information.

The time required depends on factors such as TTL values and DNS caching.

Seeing the old server shortly after a DNS change therefore does not necessarily indicate a problem.

6. Check Where Your Domain Resolves

On Windows, open Command Prompt and run:

nslookup example.com

This allows you to check the IP address returned for the domain.

You may also use:

ping example.com

but some servers block ICMP traffic. Therefore, a failed ping does not necessarily mean DNS is incorrect.

nslookup is generally more suitable for checking DNS resolution.

7. The Domain Points to the Correct IP but the Website Does Not Open

DNS only sends the domain toward the correct server.

Your VDS must also know which website should handle the request.

Depending on your setup, you may need:

• An Apache VirtualHost
• An Nginx Server Block
• A domain configured in your hosting control panel

If you use cPanel/WHM, Plesk, DirectAdmin, or another hosting panel, make sure the domain has also been added to the correct hosting account.

Think of the process as two separate layers:

DNS: Determines which server receives the request.

Web server: Determines which website should respond.

8. Check Ports 80 and 443

Standard web traffic commonly uses:

TCP 80 → HTTP

TCP 443 → HTTPS

If your server firewall blocks these ports, the website may remain inaccessible even when DNS is correct.

Ensure that your firewall configuration allows the required web traffic.

9. Install an SSL Certificate

After the domain points to your VDS, you can configure an SSL certificate so the website is available through:

https://example.com

You can use a free certificate such as Let's Encrypt or another suitable SSL certificate.

For many domain-validation methods, the domain must resolve correctly before the certificate can be issued successfully.

Do I Have to Change My Nameservers?

No.

Changing nameservers is not always necessary when pointing a domain to a VDS.

You can continue using your existing DNS provider and simply update the A record to your VDS IP.

Nameservers generally need to be changed only when you want another service or DNS server to manage the entire DNS zone.

What Is the Difference Between a Nameserver and an A Record?

A nameserver identifies where a domain's DNS records are managed.

For example:

ns1.exampledns.com
ns2.exampledns.com

An A record identifies the IPv4 address associated with a hostname.

For example:

example.com → 192.0.2.10

In simple terms, nameservers determine where DNS is managed, while an A record determines which IPv4 address a hostname resolves to.

What If I Use Cloudflare?

If your domain uses Cloudflare nameservers, edit the DNS records from the Cloudflare DNS management interface rather than from your registrar's DNS panel.

A typical configuration may include:

A → @ → VDS_IP

and:

CNAME → www → example.com

If Cloudflare's proxy feature is enabled, DNS lookups may return Cloudflare IP addresses rather than your VDS IP. This can be normal.

What Is an AAAA Record?

An A record is used for IPv4 addresses, while an AAAA record is used for IPv6.

If your VDS has properly configured IPv6 connectivity, an AAAA record can point your domain to that IPv6 address.

Do not create an AAAA record unless IPv6 is correctly configured on the server, because an incorrect IPv6 configuration may cause connectivity problems for some visitors.

Will Pointing My Domain Affect Email?

Changing only the website's A record will not normally change your email service.

However, if you replace the domain's nameservers entirely, the existing DNS records must also be recreated on the new DNS service.

Pay particular attention to:

• MX
• SPF
• DKIM
• DMARC

records.

Otherwise, your website may work while your email service stops working correctly.

What Happens If My VDS IP Address Changes?

If the server IP changes, update the domain's A record.

For example:

Old:

example.com → 192.0.2.10

New:

example.com → 203.0.113.10

After updating the DNS record, allow time for DNS caches to refresh.

Frequently Asked Questions

Do I need to change nameservers to connect a domain to a VDS?

Not necessarily. You can usually keep your existing DNS provider and point the A record to the VDS IP.

What is an A record?

An A record maps a hostname to an IPv4 address.

Does www require a separate record?

Usually yes. You can configure www using a CNAME or an A record.

How long does a DNS change take?

Some users may see the new record quickly, while cached DNS information can cause the old record to remain visible for longer.

DNS is correct, but my website does not open. Why?

Check your web server configuration, hosting account, firewall, HTTP/HTTPS ports, and SSL configuration.

Can I install SSL after pointing the domain?

Yes. Once the domain resolves to the correct server, you can configure an SSL certificate.

Conclusion

Pointing a domain to a VDS primarily involves configuring the domain's DNS records with the server's IP address.

A common configuration is:

A → @ → VDS IP

and for www:

CNAME → www → root domain

However, DNS is only one part of the configuration. Your VDS web server, firewall, hosting configuration, and SSL certificate must also be configured correctly.

When using an İde Bilişim VDS service, you can point your domains to your server using the IP address assigned to your VDS and the appropriate DNS records