Domain Not Resolving

If your domain isn't loading your website or connecting to your server, the issue is almost always related to DNS configuration. Here's how to diagnose and fix it.

DNS propagation delay

After making DNS changes, records don't update instantly across the internet. Propagation can take:

• A few minutes for most locations
• Up to 24-48 hours for full global propagation

If you just changed your DNS records, wait a few hours and try again before troubleshooting further.

Verifying your DNS records

Check that your DNS records are correctly set up:

1. Go to an online DNS checker like dnschecker.org
2. Enter your domain name
3. Select the record type you want to check (A, CNAME, MX, etc.)
4. Verify the results match what you configured

What to look for

• A record for websites: should point to your hosting server's IP address
• SRV record for Minecraft: should point to your game server's IP and port
• CNAME record for subdomains: should point to the target domain
• MX record for email: should point to your mail server

Checking nameserver configuration

If none of your DNS records are resolving, your nameservers might not be correctly configured.

1. Check your domain registrar's settings
2. Verify the nameservers are set to the correct provider:

• If using FPS.ms DNS: use the nameservers shown in your domain settings
• If using an external DNS provider (Cloudflare, etc.): use their nameservers

3. Nameserver changes can take 24-48 hours to take effect

Common mistakes

Wrong record type

• Use an A record to point to an IP address (e.g., 123.45.67.89)
• Use a CNAME record to point to another domain (e.g., mango.fps.ms)
• Don't put an IP address in a CNAME record or a domain name in an A record

Missing records

Make sure you've created records for both the root domain (yourdomain.com) and the www subdomain (www.yourdomain.com) if you want both to work.

Wrong IP address

Double-check that the IP address in your A record matches your actual server IP. You can find your server's IP in the panel under the Network or Console tab.

TTL caching

If you recently changed a DNS record, the old value may be cached. Records with high TTL (Time to Live) values take longer to update. Most FPS.ms DNS records use a TTL of 3600 seconds (1 hour).