ThisCalculator

Everyday

Custom Domain for ARK: Survival Ascended Server

Updated · Standard formula, shown below

Setting up a custom domain for your ARK: Survival Ascended server lets players connect using a memorable name like play.yourclan.com instead of a raw IP address and port. This guide covers DNS configuration and in-game setup so your community can join reliably. You’ll need a registered domain name, access to its DNS settings, and your server’s public IP address.

What You’ll Need

  • A registered domain name (e.g., from Namecheap, GoDaddy, Cloudflare)
  • Access to your domain’s DNS management panel
  • Your ARK server’s public IP address and query port (default 7777)
  • An ARK: Survival Ascended dedicated server (official or unofficial)
  • Optional: a static IP or dynamic DNS service if your IP changes

Step-by-Step

  1. Find your server’s public IP and port. If your server is hosted on a provider like Nitrado or G-Portal, copy the IP and port from their control panel. If self-hosted, check your router’s WAN IP via sites like whatismyip.com and ensure the query port (default 7777) is forwarded to your server’s local IP.
  2. Log in to your DNS provider. Go to your domain registrar or DNS hosting service (e.g., Cloudflare, Route 53) and navigate to the DNS management or Zone Editor section.
  3. Create an A record for your subdomain. Add a new record with these values:
    • Type: A
    • Name/Host: ark (this will make ark.yourdomain.com)
    • Value/Points to: your server’s public IP address
    • TTL: 300 seconds (or 5 minutes) for faster propagation
  4. Save the record. Wait for DNS propagation, which can take from a few minutes to 48 hours. Use a tool like nslookup or dnschecker.org to verify the record resolves to your IP.
  5. Test the connection. Open ARK: Survival Ascended, go to the server browser, and click “Add Server.” Enter ark.yourdomain.com:7777 (replace 7777 with your query port). If the server appears, the DNS is working.
  6. Set the server’s public IP in config (if needed). Some server setups require you to specify the domain in Game.ini or command-line arguments. Add ?PublicIP=ark.yourdomain.com to the server launch parameters or ServerSettings to ensure the server advertises the correct address.
  7. Update your server’s MOTD or Discord. Share the new domain with your players so they can connect easily.

Common Mistakes

  • Using the wrong port. ARK uses port 7777 for the game and 7778 for Steam query. Players need the query port (7777) in the connection string, not the RCON port (27020) or the game port (7777 is correct, but some setups use 7778).
  • Forgetting to forward ports. If self-hosting, ensure UDP ports 7777 and 7778 are forwarded to the server’s local IP. TCP is rarely used.
  • Typing the subdomain wrong. Double-check the A record name. ark vs arkserver matters.
  • Using a CNAME for the root domain. For a subdomain like ark.yourdomain.com, an A record is fine. A CNAME can work but may conflict with other records.
  • Not waiting for propagation. DNS changes aren’t instant. Test after 30 minutes, but allow up to 24 hours.

Tips

  • Use a subdomain, not the root domain. ark.yourdomain.com is cleaner and avoids issues with email or web hosting records.
  • Set a low TTL (300 seconds) before making changes. This speeds up propagation, then you can raise it later.
  • If your IP changes often, use a dynamic DNS service like DuckDNS or No-IP, and point your domain to their hostname via a CNAME record.
  • Test with the IP first. Verify the server works via IP:port before adding DNS, so you isolate issues.
  • Use a tool like PingPlotter or ARK’s server browser to confirm the domain resolves correctly.

Troubleshooting

  • Domain doesn’t resolve. Check the A record spelling and that you saved it. Use nslookup ark.yourdomain.com on Windows or dig ark.yourdomain.com on Mac/Linux. If it returns the wrong IP, wait or contact your DNS provider.
  • Server doesn’t appear in the browser. Confirm the port is correct and that the server is running. Try connecting via IP:port to rule out DNS. If IP works but domain doesn’t, re-check the A record.
  • Players get “Connection timed out.” Ensure the query port (7777) is open in your firewall and forwarded. Also check that your server’s ServerSettings has PublicIP set to the domain or IP.
  • DNS works but server shows as “Unreachable” in the browser. This often means the server’s advertised IP is wrong. Add ?PublicIP=ark.yourdomain.com to the launch parameters or ServerSettings.
  • Changes not propagating after 24 hours. Clear your local DNS cache (ipconfig /flushdns on Windows) and try a different DNS like Google’s 8.8.8.8. If still failing, check that your registrar isn’t overriding the nameservers.

Frequently Asked Questions

Can I use a custom domain without a static IP?

Yes, but you’ll need a dynamic DNS service that updates your domain’s A record when your IP changes. Many routers support DDNS, or you can run a client on the server.

Do I need to change the port in the domain?

No, the domain only maps to an IP address. The port is still required in the connection string (e.g., ark.yourdomain.com:7777).

Can I use a CNAME record instead of an A record?

Yes, for subdomains you can use a CNAME pointing to a hostname that resolves to your IP (like a DDNS hostname). However, you cannot use a CNAME for the root domain (e.g., yourdomain.com) in most setups.

Will a custom domain reduce ping or improve performance?

No, DNS only translates the name to an IP. The connection is identical to using the IP directly.

How long does DNS propagation take?

Typically 5-30 minutes for most DNS providers, but can take up to 48 hours globally. Use a low TTL (300) to speed it up.

Do I need to configure anything on the ARK server side?

Yes, it’s recommended to set PublicIP to your domain in the server config so the server advertises the correct address to the master server list.

Related

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.