Overview

To serve a website or application from your Pod, the domain must resolve to the Pod's public IP address. This article shows how to point a domain (or subdomain) at a Pod, whether the domain's DNS is managed by ALYPOD or elsewhere.

Before you begin

• A Pod with a public IPv4 (and optionally IPv6) address — find it under Networking in the ALYPOD Console.
• A domain you control.
• The web service on the Pod should already be running and listening on port 80/443.

Option A: DNS managed by ALYPOD

1. Log in to account.alypod.com and open Domains, then the domain.
2. Open the DNS records editor.
3. Add an A record pointing the root to your Pod's IP:

| Type | Name | Value | TTL | |------|------|--------------|------| | A | @ | 203.0.113.10 | 3600 |

1. Optionally add a www record. Point it to the same IP with an A record, or use a CNAME to the root.
2. If you have IPv6, add a matching AAAA record.
3. Save and verify:

bash dig +short A example.com dig @1.1.1.1 A example.com +short

Option B: DNS managed elsewhere

Log in to your DNS provider and create the same A/AAAA records manually, using the Pod's public IP as the value. There is nothing to change on the Pod itself.

Finishing touches

• Make sure the Pod's firewall (ufw or firewalld) and the ALYPOD cloud firewall allow ports 80 and 443.
• Install a TLS certificate; Let's Encrypt via Certbot works once DNS resolves correctly.
• Update the webserver's server name / virtual host to match the domain.

Troubleshooting

• Problem: The domain still shows an old site. Solution: Check the TTL and query a public resolver; clear any CDN or browser cache.
• Problem: DNS resolves but the site does not load. Solution: Confirm the webserver is listening (sudo ss -tlnp) and that ports 80/443 are open in both firewalls.
• Problem: Wrong IP is returned. Solution: Remove duplicate or conflicting A records and wait for the TTL to expire.

Related articles

• [Managing DNS records (A, AAAA, CNAME, MX, TXT)]
• [Changing nameservers]