How to Configure PTR Records in GoDaddy DNS for Email Server IP Reputation


4 views

Based on your provided information:

IP: 64.250.113.235
Current PTR: notification.pokemoncraft.com

This shows your hosting provider has already set up the reverse DNS entry on their nameservers. The crucial point here is that the forward (A record) and reverse (PTR) must match for proper email deliverability.

While you can't directly create PTR records in GoDaddy's DNS manager (since these are typically controlled by the IP owner, usually your hosting provider), you should ensure your forward DNS records align with the existing PTR:

;; Example DNS records that should exist in GoDaddy
notification.pokemoncraft.com.  IN  A     64.250.113.235
mail.pokemoncraft.com.          IN  A     64.250.113.235
pokemoncraft.com.               IN  MX    10 mail.pokemoncraft.com.

To verify everything is configured correctly:

# Linux/macOS terminal commands
dig +short notification.pokemoncraft.com
# Should return: 64.250.113.235

dig +short -x 64.250.113.235
# Should return: notification.pokemoncraft.com.

For optimal email deliverability, consider these additional records in GoDaddy:

;; SPF Record
pokemoncraft.com.  IN  TXT  "v=spf1 ip4:64.250.113.235 -all"

;; DKIM Record (example)
default._domainkey.pokemoncraft.com. IN TXT "v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQC..."

;; DMARC Record
_dmarc.pokemoncraft.com. IN TXT "v=DMARC1; p=none; rua=mailto:postmaster@pokemoncraft.com"

If you experience mismatches, check these points:

  • PTR record must resolve back to your A record
  • TTL values should be reasonable (300-3600 seconds)
  • No conflicting records in your DNS zone

For complete verification:

# Windows PowerShell equivalent
Resolve-DnsName notification.pokemoncraft.com
Resolve-DnsName 64.250.113.235 -Type PTR

When checking your existing PTR record through mxkit.com, we can see it's currently resolving to notification.pokemoncraft.com for IP 64.250.113.235. The DNS hierarchy shows this is properly delegated to your hosting provider's nameservers.

Since your hosting provider has already established the PTR record (as evidenced by the in-addr.arpa zone resolution), you don't actually need to configure anything in GoDaddy's DNS manager for reverse DNS. PTR records are managed by the party that owns the IP block - typically your hosting provider or ISP.

You can confirm your forward DNS matches the reverse DNS using these command line tools:

# Check PTR record
dig -x 64.250.113.235 +short

# Verify forward DNS matches
dig notification.pokemoncraft.com +short

The only scenario where you'd configure PTR in GoDaddy is if:

  1. You're using GoDaddy's mail servers
  2. You want to set up proper forward-confirmed reverse DNS (FCrDNS)

If you were setting up mail servers with GoDaddy, you would create these records:

; Example zone file entries
mail IN A 64.250.113.235
235 IN PTR mail.yourdomain.com.

If you encounter PTR verification problems, check:

  • TTL values (wait for propagation)
  • DNS delegation for the in-addr.arpa zone
  • Consistency between forward and reverse records

For those managing DNS programmatically, here's a Python example using GoDaddy's API:

import requests

headers = {
    "Authorization": "sso-key your_api_key:your_api_secret",
    "Content-Type": "application/json"
}

ptr_data = {
    "data": "mail.yourdomain.com",
    "ttl": 3600
}

response = requests.put(
    "https://api.godaddy.com/v1/domains/yourdomain.com/records/PTR/235.113.250.64.in-addr.arpa",
    headers=headers,
    json=ptr_data
)