Related

Tool Instant DNS Lookup Tool Tool
How to configure Bind9 to work with wildcard domains? Question Question
PTR *removal* only IP address - reverse DNS Question Question

Question

MX/TXT records not being served - Protonmail setup

Posted March 31, 2017 2.9k views
UbuntuDNS

I have tried everything to get my MX and TXT records working. I am currently using Zoho and although my email seems to be working when I check anything on mxtoolbox or dig it returns nothing. Zoho constantly notifies me that my mx records on not pointing at them. I am attempting to move over to ProtonMail but I cant get their verify TXT record to work. What am I doing wrong here?

$ORIGIN snugpixel.com.
$TTL 1800
snugpixel.com. IN SOA ns1.digitalocean.com. hostmaster.snugpixel.com. 1490980679 10800 3600 604800 1800
snugpixel.com. 1800 IN NS ns1.digitalocean.com.
snugpixel.com. 1800 IN NS ns2.digitalocean.com.
snugpixel.com. 1800 IN NS ns3.digitalocean.com.
snugpixel.com. 1800 IN MX 10 mx.zoho.com.
snugpixel.com. 1800 IN MX 20 mx2.zoho.com.
snugpixel.com. 1800 IN A 162.243.209.80
snugpixel.com. 1800 IN MX 30 mx3.zoho.com.
mail._domainkey.snugpixel.com. 3600 IN TXT “v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCxx2dD1aLhDkfAqNaTn5K1c6dnEtw4UVyfEMr4JbJ/aQiJSQ6fb09IM6IlJDQsp3tEm/sZ36/xuhZDiPt3tDe7Ti9XLGOcdsMrxoAXThQkB5Ke9V6PK3xeWYFDiYpV1KJV004ulu1gWVGq4XD8lYwZ66PIYTmAG0sBEdIAoLoptwIDAQAB”
snugpixel.com. 3600 IN TXT “protonmail-verification=541823790c8d063cff1cd46b62c56f919fc9c9f7”
www.snugpixel.com. 43200 IN CNAME snugpixel.com.
*.snugpixel.com. 43200 IN CNAME snugpixel.com.

Add a comment
mvvs
By:
mvvs
Add a comment

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
2 answers
hansen March 31, 2017

Is snugpixel.com your real domain? Because I’m getting this when I use dig

snugpixel.com.      3599    IN  SOA dns1.name-services.com. info.name-services.com. 1490779673 172800 900 1814400 3600
snugpixel.com.      3599    IN  NS  dns3.name-services.com.
snugpixel.com.      3599    IN  NS  dns2.name-services.com.
snugpixel.com.      3599    IN  NS  dns5.name-services.com.
snugpixel.com.      3599    IN  NS  dns4.name-services.com.
snugpixel.com.      3599    IN  NS  dns1.name-services.com.
snugpixel.com.      1799    IN  A   98.124.243.34

Did you just change the NameServer records to DigitalOcean, because then you sometimes have to wait up to 48 hours for your old NS to transfer authority to DigitalOcean.

Reply Report
jtittle1 March 31, 2017

@mvvs

I’m showing the name servers for the domain to be:

dns1.name-services.com
dns2.name-services.com
dns3.name-services.com
dns4.name-services.com
dns5.name-services.com

When doing an MX look-up on the domain, no MX records are found. So my first question would be, are you setting those records up in the DigitalOcean Control Panel or at you domain registrar?

If what you’ve posted is from the DigitalOcean Control Panel, you’ll need to modify the name servers at the registrar (who you registered the domain with) to point to:

ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com

… and then let the name servers resolve before those records will be valid.

Reply Report
Submit an Answer

Related

Looking for something else?

Ask a new question Search for more help