How to Claim Your Minecraft Server

Step-by-step guide to claiming ownership of your Minecraft server listing using DNS TXT verification, with registrar-specific instructions for Cloudflare, Namecheap, GoDaddy, and more.

Overview

If your Minecraft server was listed on Lantern Servers by someone else, you can claim ownership by proving you control the server’s domain. This is done by adding a DNS TXT record with a unique verification token.

Once claimed, the server is transferred to your account, giving you full control over its listing - you can edit the description, update tags, upload a banner, and manage settings.

Prerequisites

• You have a Lantern Servers account. Create one if you don’t.
• Your server’s address is a domain name (e.g. play.example.net), not a raw IP address. DNS verification doesn’t work with IP addresses.
• You have access to your domain’s DNS management panel.

Step 1: Find Your Server

Search for your server on our server list and navigate to its detail page.

Step 2: Open the Claim Dialog

On the server’s detail page, click the “Claim this server” button. If you’re not signed in, you’ll see a “Sign in to claim this server” link instead - sign in first.

The claim modal displays your unique verification token in the format:

lantern-claim=abc123def456abcd

Copy this value - you’ll need it for the DNS record.

Step 3: Add the DNS TXT Record

We have instructions for specific DNS providers - if you’re DNS provier isn’t listed, you can skip down to Other Registrars.

Cloudflare

1. Log in to the Cloudflare dashboard.
2. Select your domain.
3. Go to DNS → Records.
4. Click Add record.
5. Set Type to TXT.
6. Set Name to match your server’s address shown in the dialog.
7. Set Content to lantern-claim=your-token-here.
8. Click Save.

Cloudflare propagates DNS changes almost instantly (usually within a minute).

Namecheap

1. Log in to Namecheap.
2. Go to Domain List → Manage next to your domain.
3. Click Advanced DNS.
4. Under Host Records, click Add New Record.
5. Set Type to TXT Record.
6. Set Host to match your server’s address shown in the dialog.
7. Set Value to lantern-claim=your-token-here.
8. Set TTL to Automatic or a low value.
9. Click Save Changes.

Namecheap DNS changes typically propagate within 30 minutes.

GoDaddy

1. Log in to GoDaddy.
2. Click Manage next to your domain.
3. Go to DNS → Manage Records.
4. Click Add Record.
5. Set Type to TXT.
6. Set Name to your subdomain (e.g. play).
7. Set Value to lantern-claim=your-token-here.
8. Set TTL to Custom (600 seconds or lowest available).
9. Click Save.

GoDaddy changes usually propagate within 30 minutes to an hour.

Squarespace

1. Log in to Squarespace Domains (Google Domains was migrated).
2. Select your domain.
3. Go to DNS Settings → Custom Records.
4. Click Add Record.
5. Set Type to TXT.
6. Set Host to match your server’s address shown in the dialog.
7. Set Data to lantern-claim=your-token-here.
8. Click Save.

Other Registrars

The process is the same across all DNS providers:

1. Find the DNS management or zone editor for your domain.
2. Add a new TXT record.
3. Set host/name to match your server’s address shown in the dialog.
4. Set the value/content to lantern-claim=your-token-here.
5. Save and wait for propagation.

If you’re unsure where to find DNS settings, search your registrar’s help docs for “add TXT record” or ask them for help.

Step 4: Verify the Claim

Go back to the claim modal on our site and click “Verify Claim.” We query your domain’s DNS records and check for a matching TXT record. If found, the server is instantly transferred to your account.

Troubleshooting

Claim verification failed

DNS changes don’t propagate instantly. It typically takes 5-15 minutes, but can take up to 48 hours in rare cases. Wait 10 minutes and try again. You can verify the record exists using an online DNS lookup tool to check TXT records for your domain.

“DNS verification is only available for domain names”

This means your server’s address is a raw IP (e.g. 192.168.0.42), not a domain. DNS verification requires a domain name. If your server uses a raw IP, contact an admin for manual verification.

Wrong TXT record format

Make sure the value is exactly lantern-claim= followed by your token, with no extra spaces. Some DNS providers:

• Wrap values in quotes automatically - you don’t need to add quotes yourself.
• Add a trailing dot to the record name - this is normal and won’t cause issues.
• Require you to enter the full record value without the prefix - check your provider’s documentation.

Multiple TXT records on the same domain

Having other TXT records (e.g. for SPF, DKIM, or domain verification) is fine. We search all TXT records on the domain for a match. Just make sure the claim record is present alongside them.

DNS propagation is slow

If your registrar has slow propagation:

• Lower the TTL to the minimum value before adding the record.
• Wait up to 48 hours in rare cases.

After Claiming

Once the claim succeeds:

• The server appears in your dashboard alongside any other servers you own.
• You can edit the description, tags, versions, banner, and links.
• You can delete the server if needed.

Need more help?

If you’re stuck, check your server’s detail page and look for the Claim button, or read our guide to listing your server.