Google DNS is the only server not resolving domain

[fran.v...@gmail.com]

It's been around a week now and google dns is not resolving although everyone else is!
We actually migrated to google dns for this a week ago and same story. We have tried using the google's dns flush tool with no success.
Here are our cloud dns configurations:

fireworksit.com. A 300
45.55.112.21

fireworksit.com. MX 300
1 aspmx.l.google.com.
5 alt1.aspmx.l.google.com.
5 alt2.aspmx.l.google.com.
10 alt3.aspmx.l.google.com.
10 alt4.aspmx.l.google.com.
fireworksit.com. NS 21600
ns-cloud-b1.googledomains.com.
ns-cloud-b2.googledomains.com.
ns-cloud-b3.googledomains.com.
ns-cloud-b4.googledomains.com.
fireworksit.com. SOA 21600
ns-cloud-b1.googledomains.com. cloud-dns-hostmaster.google.com. 1 21600 3600 1209600 300

fireworksit.com. TXT 300
"google-site-verification=bZymcQsd_P6td7rCwo028YKuej3Uvs1kMBPKtTZH294"

calendar.fireworksit.com. CNAME 300
ghs.googlehosted.com.

drive.fireworksit.com. CNAME 300
ghs.googlehosted.com.

groups.fireworksit.com. CNAME 300
ghs.googlehosted.com.

mail.fireworksit.com. CNAME 300
ghs.googlehosted.com.

mg.fireworksit.com. A 300
45.55.112.21

mg.fireworksit.com. TXT 300
"v=spf1" "include:mailgun.org" "~all"

krs._domainkey.mg.fireworksit.com. TXT 300
"k=rsa"
"p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDdGc8Jqi0gXSqkGJ/QujeoG7Np/58xSZX5XJ0X1z4NOR+RQxH6sKQz5Cn0E9Rnv+codOkKqP/jiZnT9OI4s3OjDw2gI+GbwTJDXy6ftjWZSi1vNGTQwmh8LCUBEw6548stgsBK4voGsT2CtBHe922TZrwS1kcPZQ08KF32aArvYwIDAQAB"

email.mg.fireworksit.com. CNAME 300
mailgun.org.

pan.fireworksit.com. A 300
138.68.192.158

sites.fireworksit.com. CNAME 300
ghs.googlehosted.com.

turismo.fireworksit.com. A 300
138.68.192.158

www.fireworksit.com. CNAME 300
fireworksit.com.

[Alex Dupuy]

There are a couple of issues with your fireworksit.com domain that you need to fix at your registrar (according to WHOIS, this is eNom via Reseller: NameCheap).

1. Your domain is configured to use nameservers at Digital Ocean - it looks like you just changed this to try and fix your resolution problem.  To use the Google Cloud DNS service, you need to switch those back to the Cloud DNS nameservers.
   
• NameCheap instructions (https://www.namecheap.com/support/knowledgebase/article.aspx/767/10/how-can-i-change-the-nameservers)
2. You need to disable DNSSEC that was enabled at some point in the past (maybe if you were using GoDaddy as your registrar?) for Google Public DNS to work correctly; this involves removing the DS record at the .COM registry. (This is true for both DigitalOcean as well as Google Cloud DNS).
   
• NameCheap instructions (https://www.namecheap.com/support/knowledgebase/article.aspx/9722/2232/managing-dnssec-for-custom-dns)

It may be a bit tricky to "disable" DNSSEC at NameCheap since it probably thinks that DNSSEC is already disabled. You could try enabling DNSSEC and then disabling it. You will probably need to wait a while (up to a few hours) for this to be reflected at the .COM registry. It might be worth contacting NameCheap directly.

If you are actually using eNom rather than NameCheap to manage your domain registration, see the instructions at http://www.enom.com/helpme/ for directions on submitting a support request or contacting your reseller. Include all DS records reported by dig +cd +noall +answer +nottl DS fireworks.it in your support ticket.

[Francisco Vera]

Thanks, I have contacted namecheap and they have problems deleting the dnssec, so that must be it. They are fixing it now. Thank you again!

[Alex Dupuy]

You're welcome. Note that there is a separate discussion forum (https://groups.google.com/forum/#!forum/public-dns-discuss) for Google Public DNS (the open public resolver, which validates DNSSEC)—this forum is for Google Cloud DNS (the authoritative DNS cloud service). Your issues involved both (in different ways) so it wasn't wrong to post here, but it might have been a better fit for the other forum (especially once you saw that it was still not working after moving the nameservers to Digital Ocean).

[fran.v...@gmail.com]

On Thursday, May 5, 2016 at 3:47:24 PM UTC-5, Alex Dupuy wrote:
> You're welcome. Note that there is a separate discussion forum (https://groups.google.com/forum/#!forum/public-dns-discuss) for Google Public DNS (the open public resolver, which validates DNSSEC)—this forum is for Google Cloud DNS (the authoritative DNS cloud service). Your issues involved both (in different ways) so it wasn't wrong to post here, but it might have been a better fit for the other forum (especially once you saw that it was still not working after moving the nameservers to Digital Ocean).

You are right, sorry about that. Thank you for your time