About 24 hours ago, 8.8.8.8 stopped resolving my subdomains

[bill....@gmail.com]

I've run through the diagnostics and more.

My DNS registrar is hover.com and I've reviewed the configuration with them.

I have a number of subdomains under acadiant.eu

acadiant.eu resolves fine through 8.8.8.8

About 24 hours ago, subdomains -- take txn.acadiant.eu as the test example -- stopped resolving.

Did something change, perhaps enhanced security?  This occurred after months of stable resolution, with no configuration change on our part.

According to whatsmydns.net, Google / Mountain View is an outlier.  Twenty other global ISPs all resolve both A records and CNAME records correctly for the subdomains.

Bill Chute

[sync...@gmail.com]

We're seeing the same here for all records with CNAMES pointing to amazon load balancers.

[Yunhong Gu]

The nameserver ns1.hover.com return SERVFAIL for txn.acadiant.eu. The status code should be NOERROR.

; <<>> DiG 9.8.3-P1 <<>> txn.acadiant.eu @ns1.hover.com

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 51375

;; flags: qr rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; WARNING: recursion requested but not available

;; QUESTION SECTION:

;txn.acadiant.eu. IN A

;; ANSWER SECTION:

txn.acadiant.eu. 900 IN CNAME acadiantlb-1415673629.eu-west-1.elb.amazonaws.com.

;; Query time: 73 msec

;; SERVER: 216.40.47.26#53(216.40.47.26)

;; WHEN: Fri Apr 17 14:25:31 2015

;; MSG SIZE  rcvd: 96

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to
public-dns-disc...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[sync...@gmail.com]

That's most likely due to the fact that this nameserver (like ours) doesn't resolve the cnames. Google DNS apparantly has issues resolving the cnames supplied by other nameservers.

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

[Yunhong Gu]

Yes, you are right, asking for cname record it returns NOERROR.

The cname itself is OK:

dig @8.8.8.8 acadiantlb-1415673629.eu-west-1.elb.amazonaws.com +short

54.228.196.62

54.246.113.119

Looks like there is something else...

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.

[Yunhong Gu]

The nameserver ns1.hover.com seems to return a malformed response for UDP queries. Our new release no longer retry TCP for this situation. 

dig +norecurse txn.acadiant.eu @216.40.47.26

;; Warning: Message parser reports malformed message packet.

[sync...@gmail.com]

looks like our provider is doing the same 

;; Warning: Message parser reports malformed message packet.

;; Truncated, retrying in TCP mode.

is there anything we can do about it?

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

[Bill Chute]

THANK YOU.  I'll get on this.  That explains the behaviour.

[Bill Chute]

I've been tracking the status closely. Obviously, I care about it getting fixed.

At this moment, ns1.hover.com will still return a SERVFAIL status when I dig the address of my subdomain, but returns the CNAME, and no A record. I understand this has "always" been the behavior, and most other DNS resolvers deal with it.

8.8.8.8 returns only SERVFAIL and does not pass on the CNAME.

I notified Hover. They've acknowledged the issue and are working on it:
hoverstatus.com

I am guessing that this technical change is peripherally related to Google's new DNS products:
www.theregister.co.uk/2015/04/13/google_cloud_networking/

Either Google might decide to return to "standard practice" of resolving via TCP from other nameservers for a better customer experience, or each individually "misconfigured" nameserver provider will need to "fix" their UDP responses. Hopefully both?

I'll post when I see this resolved. In the meantime, I'm interested in the experiences of other upstream DNS providers with "misconfigured" nameservers.

Bill.

On Apr 18, 2015, at 10:34 AM, sync...@gmail.com wrote:

> Hello,
>
> the problem seems to be solved. Did you rollback to an earlier release that allows TCP fallback?
>
> Kind regards

[Yunhong Gu]

Hi, Bill

The change is not related to other Google products. We made the change based on past statistics that about 99% of those TCP retries on malformed responses never succeed anyway. We can manually whitelist a small number of nameservers and domains to send TCP queries if they affect many users.

Yunhong

[Bill Chute]

Thank you very much Yunhong.  I'll pass that information on to hover.com too.

Bill.

[Yunhong Gu]

I whitelisted two hover.com nameservers. This should work in the next 1 - 2 hours. We will remove the whitelist once the problem is fixed on their side.

[sync...@gmail.com]

Contrary to my earlier statement, the issue is not resolved yet. I can't get to anyone at internetx today, so could you do us a massive favor and whitelist the nameservers at internetx (our provider) for us? 

These four servers are problematic:

b.u-ns.net

a.u-ns.net

c.u-ns.net

d.u-ns.net

since they're responding with malformed packets the google bot can't reach the sites and we're losing SEO Rankings aswell as SEM and our CNAMEs don't resolve.

Thanks a lot in advance,

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

[Yunhong Gu]

On Sat, Apr 18, 2015 at 11:56 AM, <sync...@gmail.com> wrote:

Contrary to my earlier statement, the issue is not resolved yet. I can't get to anyone at internetx today, so could you do us a massive favor and whitelist the nameservers at internetx (our provider) for us? 

These four servers are problematic:

b.u-ns.net

a.u-ns.net

c.u-ns.net

d.u-ns.net

These are whitelisted as well. It should become effective in a few hours.

 

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.

[Bill Chute]

Bless you Yunhong.  Hover have been notified.

dig @8.8.8.8 txn.acadiant.eu

; <<>> DiG 9.8.3-P1 <<>> @8.8.8.8 txn.acadiant.eu

; (1 server found)

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44946

;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;txn.acadiant.eu. IN A

;; ANSWER SECTION:

txn.acadiant.eu. 899 IN CNAME acadiantlb-1415673629.eu-west-1.elb.amazonaws.com.

acadiantlb-1415673629.eu-west-1.elb.amazonaws.com. 59 IN A 54.228.196.62

acadiantlb-1415673629.eu-west-1.elb.amazonaws.com. 59 IN A 54.246.113.119

;; Query time: 450 msec

;; SERVER: 8.8.8.8#53(8.8.8.8)

;; WHEN: Sat Apr 18 17:25:32 2015

;; MSG SIZE  rcvd: 128

[de...@cask.co]

Hi,

It appears mediatemple (ns[1,2].mediatemple.net) is also affected by this.  I've contacted them but haven't heard back yet.

$ dig +norecurse docs.cask.co @ns1.mediatemple.net

;; Warning: Message parser reports malformed message packet.

;; Truncated, retrying in TCP mode.

$ dig docs.cask.co @8.8.8.8

; <<>> DiG 9.8.3-P1 <<>> docs.cask.co @8.8.8.8

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 23358

;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;docs.cask.co. IN A

;; Query time: 183 msec

;; SERVER: 8.8.8.8#53(8.8.8.8)

;; WHEN: Sun Apr 19 14:30:02 2015

;; MSG SIZE  rcvd: 30

Thanks,

-Derek

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

[in...@trendgroup.de]

Hi,

same Probleme here for the following nameservers. Would be great if you could add them to your whitelist until the issue is solved:

a.ns14.net

b.ns14.net

c.ns14.net

d.ns14.net

Example Request:

➜ dig +norecurse www.cleverkaufen.de @a.ns14.net

[Oliver Peter]

Hi Yunhong,

Could you please whitelist the following ranges of IP addresses?

We host more than thousand customer NS in this ranges, milliones of zones... all affected by this issue:

62.116.131.31/32

62.116.159.0/24

217.160.113.0/24

83.169.55.0/24

89.146.248.0/24

74.208.254.0/24

Please also let me know for you long this whitelist will be valid for so I can plan any infrastructure updates on our side.

Cheers

Oliver

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

[in...@trendgroup.de]

Thanks for adding our Nameservers to your whitelist. It seems to solve the issues for Google Public DNS. As can be checked with dig.

Nonetheless other google tools still can not access the website. This is currently true for Google Webmastertools (Fetch as Google and therefor probably affecting the google bot itself) and tools like the mobile friendly check.

Examples:

➜ dig www.acadiant.eu @8.8.8.8 +short

acadiantlb-1415673629.eu-west-1.elb.amazonaws.com.

54.246.113.119

54.228.196.62

But

https://www.google.com/webmasters/tools/mobile-friendly/?url=http%3A%2F%2Fwww.acadiant.eu

=> Error fetching requested URL

[Yunhong Gu]

On Mon, Apr 20, 2015 at 11:16 AM, Oliver Peter <faust...@gmail.com> wrote:

Hi Yunhong,

Could you please whitelist the following ranges of IP addresses?

We host more than thousand customer NS in this ranges, milliones of zones... all affected by this issue:

62.116.131.31/32

62.116.159.0/24

217.160.113.0/24

83.169.55.0/24

89.146.248.0/24

74.208.254.0/24

Please also let me know for you long this whitelist will be valid for so I can plan any infrastructure updates on our side.

Cheers

Oliver

These are whitelisted now (expect to be effective in 1 - 2 hours). Please let us know when the issues are fixed so that we can stop sending them TCP queries (unless TC bit is set).

 

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.

[Yunhong Gu]

I will investigate this as well, but it may take longer time.

[de...@cask.co]

Can you also white-list Mediatemple's nameservers?  ns[1,2].mediatemple.net

Thanks,

-Derek

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

[Yunhong Gu]

On Mon, Apr 20, 2015 at 3:53 PM, <de...@cask.co> wrote:

Can you also white-list Mediatemple's nameservers?  ns[1,2].mediatemple.net

Done.

 

Thanks,

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.

[titan...@gmail.com]

We are having the same issue. We host 100's of DNS for different domains. The name servers are ns1.titanweb.net.au, ns2.titanweb.net.au and ns3.titanweb.net.au.

All has been working fine up till yesterday. Now google DNS has issues resolving the www records sometimes. This domain premierautopaints.com.au has had issues with it's www record.

I am thinking that the issue is the same can you please confirm and are you able to "whitelist" these servers as well? 

Thanks,

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

[Oliver]

We are having the same issue here; both 8.8.8.8 and 8.8.4.4 stopped resolving our AWS Load balancer CNAME yesterday

Thanks,

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

[pa...@docmosis.com]

Hello.

Could you please white-list:
  ns1.name-services.com.au
  ns2.name-services.com.au
  ns3.name-services.com.au
  ns4.name-services.com.au
  ns5.name-services.com.au
?

This is causing problems for us.
Regards,
Paul.

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

[titan...@gmail.com]

Hi Yunhong, This is a very very serious problem that Google is currently having so I do ask that you have a look at this as soon as possible.

This is a Google technical issue that is currently affecting many clients and other digital agencies and ISP's. This is a problem Google is having as it is only Google DNS that can't find the sites.

The big issue we now have is our clients ranking are beginning to suffer as well as Titan's own because Googles DNS are playing up. This is critical request. Our phones are now jammed with upset clients who have lost rankings. I am sure Google understands it is very difficult to sell PPC when clients are this upset. 

Please look into this issue as soon as you can.

[Yunhong Gu]

On Wed, Apr 22, 2015 at 12:09 AM, <titan...@gmail.com> wrote:

Hi Yunhong, This is a very very serious problem that Google is currently having so I do ask that you have a look at this as soon as possible.

This is a Google technical issue that is currently affecting many clients and other digital agencies and ISP's. This is a problem Google is having as it is only Google DNS that can't find the sites.

The big issue we now have is our clients ranking are beginning to suffer as well as Titan's own because Googles DNS are playing up. This is critical request. Our phones are now jammed with upset clients who have lost rankings. I am sure Google understands it is very difficult to sell PPC when clients are this upset. 

Please look into this issue as soon as you can.

On Tuesday, April 21, 2015 at 9:12:25 PM UTC+8, titan...@gmail.com wrote:

We are having the same issue. We host 100's of DNS for different domains. The name servers are ns1.titanweb.net.au, ns2.titanweb.net.au and ns3.titanweb.net.au.

All has been working fine up till yesterday. Now google DNS has issues resolving the www records sometimes. This domain premierautopaints.com.au has had issues with it's www record.

I am thinking that the issue is the same can you please confirm and are you able to "whitelist" these servers as well? 

Your nameservers seem to work just fine. premierautopaints.com.au  is resolved OK on all Google Public DNS locations:

dig @8.8.8.8 premierautopaints.com.au +short

54.252.105.221

Do you have another domain name that I can use to verify?

 

Thanks,

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.

[Yunhong Gu]

Paul, can you tell me a domain name that is served by these nameservers so that I can verify?

Yunhong

On Wed, Apr 22, 2015 at 12:15 AM, <pa...@docmosis.com> wrote:

Hello.

My registrar (aussiedomains.com.au) is having the same troubles.  Their name servers are ns[12345].name-services.com.au  (eg ns1.name-services.com.au).
Our cname alias to AWS ELBs are not resovlving via google (8.8.8.8).  Other servers suggested by Google diagnostics are aok (eg 4.2.2.1 can resolve it aok).

This is causing us grief.  Can ns[12].name-services.com.au be white-listed too if that is the solution?


Regards,
Paul.

 

On Saturday, April 18, 2015 at 2:24:07 AM UTC+8, sync...@gmail.com wrote:

We're seeing the same here for all records with CNAMES pointing to amazon load balancers.

On Friday, April 17, 2015 at 4:10:58 PM UTC+2, bill....@gmail.com wrote:

I've run through the diagnostics and more.

My DNS registrar is hover.com and I've reviewed the configuration with them.

I have a number of subdomains under acadiant.eu

acadiant.eu resolves fine through 8.8.8.8

About 24 hours ago, subdomains -- take txn.acadiant.eu as the test example -- stopped resolving.

Did something change, perhaps enhanced security?  This occurred after months of stable resolution, with no configuration change on our part.

According to whatsmydns.net, Google / Mountain View is an outlier.  Twenty other global ISPs all resolve both A records and CNAME records correctly for the subdomains.

Bill Chute

[voncken...@gmail.com]

Hi Yunhong,

Can you also add the following nameservers to the whitelist:

nsb4.schlundtech.de
nsc4.schlundtech.de
nsa4.schlundtech.de
nsd4.schlundtech.de

We are having massive problems and losing visibility in search results with sunnycars.nl / sunnycars.de and sunnycars.be

Thanks in advance!


Gr,
Claudia

[titan...@gmail.com]

Hi Yunhong, thanks for looking into this.

Sorry can you try dig @8.8.8.8 www.premierautopaints.com.au +short

We are having trouble only with the subdomains. I just tested this and got 2 no response and 1 response.

Thanks

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

[Paulj]

Thanks Yunhong Gu.

White listing the name-servers has resolved the issue.  We will continue with our provider to have the UDP response that is the root cause corrected:

(as shown by dig)

;; Warning: Message parser reports malformed message packet.

;; Truncated, retrying in TCP mode.

Regards,

Paul.

On Wednesday, April 22, 2015 at 12:25:37 PM UTC+8, Yunhong Gu wrote:

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

[rtgo...@gmail.com]

Please also whitelist the following DNS Servers:

nsb4.schlundtech.de

nsc4.schlundtech.de

nsa4.schlundtech.de

nsd4.schlundtech.de

[titan...@gmail.com]

Hi Yunhong

We appreciate your help.
The issue is not with the apex records (eg premierautopaints.com.au) which are simple A records. They seem to work find.

The problem is with the www. records which are CNAMEs pointing at AWS load-balancers. For example:
www.premierautopaints.com.au.
www.freedomcarcare.com.au.

Resolving these records through 8.8.8.8 or 8.8.4.4 is hit-and-miss, i.e. sometimes the correct information is returned, or sometimes we get SERVFAIL.

Reading through the posts here tells me that we're not alone with this problem.

Again, thanks for your help.

Thanks,

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

[stepha...@gmail.com]

Can someone please advise on the way forward. Are we waiting for Google to make a call to roll back or do we need to insist our providers fix the UDP response or do we need to get white-listed. Our provider is tiny so sounds silly to get them white-listed.

[in...@trendgroup.de]

Hi Yunhong,

thanks for your ongoing efforts. While whitelisting the nameservers solves part of the problem (public dns can resolve the domain names for now) a bigger issue persists:

It seems like the google crawler is affected by this update, and whitelisting does not take effect here. A lot of people report error message from Google Webmaster tools about their sites not being reachable by google. A quick way to check if a site is affected is the "mobile friendly check" [1]. People already started to notice changes in their rankings.

Can you provide further informations on how to handle the situation? Is there a guide for registrars on how to setup their nameserver accordingly?

Thanks,

Paul

[1] https://www.google.com/webmasters/tools/mobile-friendly/?url=http%3A%2F%2Fwww.cleverkaufen.de%2F

[titan...@gmail.com]

Hi Yunhong,

Thanks for looking into this. As you have found out the Apex record is fine and the Nameservers work fine but if you do the query dig @8.8.8.8 www.premierautopaints.com.au +short you often get no result which is our issue

Thanks

On Tuesday, April 21, 2015 at 9:12:25 PM UTC+8, titan...@gmail.com wrote:

[alinago...@googlemail.com]

Hello Yunhong,

we (www.sunnycars.de) have the same problem. Could you please check it and put us to the whitelist?

Our nameservers are:

nsb4.schlundtech.de

nsc4.schlundtech.de

nsa4.schlundtech.de

nsd4.schlundtech.de

Please let me know if you need more information.

Thank you and Regards,

Alina

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

[titan...@gmail.com]

Hi Yunhong,

Thanks for looking into this. As you have found out the Apex record is fine and the Nameservers work fine but if you do the query dig @8.8.8.8 www.premierautopaints.com.au +short you often get no result which is our issue

Thanks

[titan...@gmail.com]

Hi Yunhong,

Thanks for looking into this. As you have found out the Apex record is fine and the Nameservers work fine but if you do the query dig @8.8.8.8 www.premierautopaints.com.au +short you often get no result which is our issue

Thanks

Thanks,

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

[titan...@gmail.com]

Hi Yunhong

We appreciate your help.

The problem is with records like www.premierautopaints.com.au which is a CNAME pointing at a AWS load-balancer. Resolving it through 8.8.8.8 or 8.8.4.4 is hit-and-miss (i.e. either we get the correct information or a SERVFAIL).

Other examples are:
www.freedomcarcare.com.au
www.agj.com.au

Simple A type records (like the premierautopaints.com.au apex record) seem to work fine. We don't have issues resolving those.

Again, thanks for your help.

Thanks,

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

[titan...@gmail.com]

hi Yunhong, Thanks for looking into this. Yes APEX records are fine and as you have said the nameservers are working fine. but if you do a request to the www. record for premierautopaints.com.au you will see that the results are different and very sporadic. So dig @8.8.8.8 www.premierautopaints.com.au +short often returns nothing.

Thanks again as this is very urgent for us.

Thanks,

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

[stepha...@gmail.com]

Hi Yunhong

Where can i get information to give to my DNS provider about exactly what the issue is and how they can fix it?

Stephan Roux

[Bill Chute]

Stephan,

Google have not said that there is any 'roll back' planned but they have been accommodating in whitelisting any upstream DNS providers we have asked.

Early on in the thread I hoped that both: (1) Google would offer temporary relief; and (2) the name servers at the individual providers would be remediated.

It looks like my hope has come true.  Yunhong has been whitelisting on request, which gives the broken name servers time to be fixed.

In my case, I confirmed with my provider hover.com, and indeed their name servers are not answering correctly on the first try, and they've acknowledged this.

In the short term, hover.com (and now a number of other providers) are whitelisted.  In the medium term, they really do need to bring their name servers into

compliance with the protocol.  I think that's fair.

So I'd say get your "tiny" provider whitelisted, while at the same time telling them to fix their UDP response for DNS resolution.  I find the 'dig' tool 

(in Unix/OS X/ other operating systems) is useful to illustrate the issue.

Good luck.

Bill.

[Yunhong Gu]

Your nameservers are added to the whitelist (should be effective in 1 - 2 hours). Sorry about the delay.

Thanks,

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.

[Yunhong Gu]

On Wed, Apr 22, 2015 at 8:44 AM, <alinago...@googlemail.com> wrote:

Hello Yunhong,

we (www.sunnycars.de) have the same problem. Could you please check it and put us to the whitelist?

Our nameservers are:

nsb4.schlundtech.de

nsc4.schlundtech.de

nsa4.schlundtech.de

nsd4.schlundtech.de

These are already whitelisted from another user' request. They are included in the following IP range:

62.116.131.31/32

62.116.159.0/24

217.160.113.0/24

83.169.55.0/24

89.146.248.0/24

74.208.254.0/24

 

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.

[Yunhong Gu]

Hi, all

We are working on improvements to Google Public DNS to better handle some corner cases affected by this change, especially those involved with AWS LB CNAMEs. We plan to have a new release next week. In the meanwhile, we will continue to add more nameservers to the whitelist.

We are also working with other Google teams to improve the situation on crawler, etc to address this.

Yunhong

[voncken...@gmail.com]

Hi Yunhong,

Thanks for this update.

Will you keep us informed on the new release as well?





Op woensdag 22 april 2015 17:57:47 UTC+2 schreef Yunhong Gu:

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

[sync...@gmail.com]

Hello Yunhong,

first, thank you for the whitelisting. This resolved some of the issues. Unfortunately Google's Webmaster Tools still report DNS failures around 80% - Is there a way you could contact the other teams, whether they're aware of the issue or what can be done not to lose rankings in the process? I attached a screenshot of the failure graph. Those are AWS LB CNAMEs too. Not sure why this still fails, since our provider's nameservers have been whitelisted and are no longer producing SERVFAILs by manually digging @8.8.8.8 - do the google bots respect the whitelist?

Cheers,

Alex

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

[Yunhong Gu]

I checked the webmaster link from another user's email and it is already working again:

https://www.google.com/webmasters/tools/mobile-friendly/?url=http%3A%2F%2Fwww.cleverkaufen.de%2F

If yours still cannot be reached from the webmaster tool, can provide a link for me to check?

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.

[sync...@gmail.com]

The project owner just told me there's still errors for sites like www.fluege.de and all our other european portals - crawler errors to be specific. The mobile friendly check you linked however works. If you could check if the crawler does something differently, that would be great. Unfortunately I don't have access to the webmaster tools myself, but if you could check if there's still something wrong for www.fluege.de (as an example), that would be very helpful.

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

[sync...@gmail.com]

crawler errors seem to be decreasing for the 22nd of april, since we can only check data from 2 days back, we'll have to see, but it looks better now.

[cgyo...@tucowsinc.com]

Hi Yunhong,

Would it be possible to request the whitelisting of the following nameservers as well, as we have customers on all 3 platforms being impacted by this change:

ns1.systemdns.com

ns2.systemdns.com

ns3.systemdns.com

ns1.shopco.com

ns2.shopco.com

ns1.mdnsservice.com

ns2.mdnsservice.com

ns3.mdnsservice.com

We have our developers looking into correcting our DNS platforms to address the malformed UDP responses, but would appreciate a whitelisting on the Google Public DNS service as well (as they worked prior to this change).

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

[sync...@gmail.com]

Hello,

would you please be so kind as to add a few more servers to the whitelist for us?

a.ns14.net

b.ns14.net

c.ns14.net

d.ns14.net

Thanks a lot in advance

Am Donnerstag, 23. April 2015 15:38:48 UTC+2 schrieb Yunhong Gu:

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

[tsf...@gmail.com]

 

Hi Yunhong,

 

Could you please whitelist the following NameServers?

 

ns1.brennanit.net.au.
ns2.brennanit.net.au.
ns3.brennanit.net.au. 

 

Currently 8.8.8.8 is having trouble resolving www.forevernew.com.au to it's AWS Load Balancer CNAME. I have contacted Brennan IT to correct their NS misconfig.

 

Best regards,

Terry

[tsf...@gmail.com]

Hi Yunhong,

 

Could  you please whitelist the following Nameservers?

 

ns1.brennanit.net.au.
ns2.brennanit.net.au.
ns3.brennanit.net.au.

 

currently 8.8.8.8 will not resolve www.forevernew.com.au to it's AWS Load Balancer CNAME. I have contacted Brennan IT to have them resolve their DNS misconfig.

 

Cheers,

Terry

[Shen Wan]

I have whitelisted these three nameservers. Expect it to become effective in a few hours.

[j...@seeds.no]

Hi

We are experiencing the same problems. Can you please whitelist my three nameservers:

ns4.eonisp.net

ns5.eonisp.net

ns6.eonisp.net

-Jo Henrik

[tsf...@gmail.com]

Hi Shen,

 

Thank you for whitelisting. Our propagation looks much better. However we are still unable to fetch data using either Google webmaster tools or Google's mobile-friendly test. Should whitelisting have resolved this issue?

 

Thanks,

Terry

[jp...@tucowsinc.com]

Hi Shen,

[Shen Wan]

I have whitelisted these (and above) nameservers. Expect it to become effective in a few hours.

[Peter van Dijk]

Hello everybody,

we are receiving reports that occurrences of this problem correlate strongly with installations of PowerDNS 2.9.22.

If you are suffering from this issue due to CNAMEs to AWS or other parties with long names, please considering lowering ‘send-root-referral’ from ‘on’ or ‘yes’ down to ‘lean’. We strongly suspect this will solve the issue for you, and avoid having to ask for a whitelist.

After that, please read [Pdns-announce] PowerDNS Autoritative Server 2.9.22 issues at http://mailman.powerdns.com/pipermail/pdns-announce/2015-April/000236.html

Please contact us if you have any questions.

Kind regards,
--
Peter van Dijk
PowerDNS.COM BV - https://www.powerdns.com/

[bert....@gmail.com]

Hi everybody,

We expect these issues correlate with PowerDNS Authoritative Server 2.9.22.x. If you are affected by the truncation issue, can you check if setting 
root-referral=lean solves it for you?

We think it should, but we'd love to hear of this makes google public DNS happy again.

    Bert (PowerDNS)

[tsf...@gmail.com]

Hi Bert,

Our nameserver (ns1.brennanit.net.au) attempted this change last night on their 2.9.22.x environment and it did not have an effect - it still returns an over 512 byte UDP packet for queries. They are now investigating upgrading to version 3.

Thanks,

Terry

[Sylvie Cousineau]

Hi Yunhong Gu, I have the same trouble

Can you whitelist the following nameservers

ns1.scva-web.com
ns2.scva-web.com

We have change server a month ago and I have 80 customers who are having trouble receiving gmail email.

Here's the result that I have error

dig @2001:4860:4860::8888 www.scva-web.com AAAA
dig @2001:4860:4860::8888
; <<>> DiG 9.8.3-P1 <<>> @2001:4860:4860::8888 www.scva-web.com AAAA
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached

[bill....@gmail.com]

Hi Yunhong.

I am happy that Hover.com have remediated their servers:

ns1.hover.com

ns2.hover.com

So you can probably remove them from the whitelist!  Please check first, if you can, of course.

Thank you for your temporary fix while they brought things in line. I appreciate it.

Bill.

[Yunhong Gu]

The servers have been removed from the TCP whitelist. We also released a new version that deals with this situation better.

Thanks,

Yunhong

--

--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.

[Bryan Price]

DNSsec failures.

http://dnsviz.net/d/mjpromotions.nl/dnssec/

Comcast isn't resolving it either.

On Tue, May 19, 2015 at 5:31 PM, <jerimia...@nationalnet.com> wrote:

Hello,

I was wondering if anybody from google can help me out. I'm unable to resolve a certain domain's A and MX records from google's 8.8.8.8 server, I supposed other google DNS servers as well.

bob$ dig @4.2.2.2 +short mjpromotions.nl
69.50.128.155
bob$ dig @37.235.1.174 +short mjpromotions.nl
69.50.128.155
bob$ dig @216.146.36.36 +short mjpromotions.nl
69.50.128.155
bob$ dig @8.8.8.8 +short mjpromotions.nl
bob$

The authoritative DNS server supports both TCP and UDP. Any ideas?

Thanks,
Bob

--

"I never said half the things the Internet says I said." -- Mark Twain

[morris....@gmail.com]

I am having this same issue with remote.waters.com. Can you please add it to the white-list in the interim while the issue is fixed? Thank you.

[seina...@gmail.com]

Hi,

We run a popular FreeDNS system at https://www.1984hosting.com/ and now we are getting complaints about this issue, please whitelist ns0.1984.is 

Best

Siggi

[c00l...@gmail.com]

hi,

im having problem with wheelspine.com.

ive setup dns and ips on google cloud dns,

but 

nslookup -debug wheelspine.com ns-cloud-c1.googledomains.com

Server: ns-cloud-c1.googledomains.com

Address: 216.239.32.108#53

------------

    QUESTIONS:

wheelspine.com, type = A, class = IN

    ANSWERS:

    AUTHORITY RECORDS:

    ADDITIONAL RECORDS:

------------

** server can't find wheelspine.com: REFUSED

Server: ns-cloud-c1.googledomains.com

Address: 216.239.32.108#53

------------

    QUESTIONS:

wheelspine.com.lan, type = A, class = IN

    ANSWERS:

    AUTHORITY RECORDS:

    ADDITIONAL RECORDS:

------------

** server can't find wheelspine.com.lan: REFUSED

please advice,

thank you

[Bryan Price]

On Mon, Jul 13, 2015 at 4:59 AM, <c00l...@gmail.com> wrote:

hi,

im having problem with wheelspine.com.

Fix your DNSSEC

http://dnsviz.net/d/wheelspine.com/dnssec/

[claud...@gmail.com]

Hello,

It seems that since yesterday the domain netdania.com is not getting resolved by google public dns (8.8.8.8 or 8.8.4.4) . The SOA output is this:

netdania.com

        primary name server = dns150.a.register.com

        responsible mail addr = root.register.com

        serial  = 2000063191

        refresh = 10800 (3 hours)

        retry   = 86400 (1 day)

        expire  = 604800 (7 days)

        default TTL = 14400 (4 hours)

The nslookup is this: > server 8.8.8.8

Default Server:  google-public-dns-a.google.com

Address:  8.8.8.8

> www.netdania.com

Server:  google-public-dns-a.google.com

Address:  8.8.8.8

*** google-public-dns-a.google.com can't find www.netdania.com: Server failed

> netdania.com

Server:  google-public-dns-a.google.com

Address:  8.8.8.8

DNS request timed out.

    timeout was 2 seconds.

Is there a way to solve this ?

[yuyu...@gmail.com]

hey, i have a similar problem with one of the domains i'm running

km-bsafe.com

this is the nslookup result using 8.8.8.8

Server:  google-public-dns-a.google.com

Address:  8.8.8.8

*** google-public-dns-a.google.com can't find km-bsafe.com: Server failed

this is the result using 4.2.2.1

Server:  a.resolvers.level3.net

Address:  4.2.2.1

Non-authoritative answer:

Name:    km-bsafe.com

Address:  66.147.244.97

google please fix this.

thank you

[ju...@pdfen.nl]

Hello,

Could you please add ns1.satserver.nl,ns2.satserver.nl and ns3.satserver.nl to do the whitelist, since the domain werelds.nu is not resolved anymore:

------------

nslookup werelds.nu 8.8.8.8

Server:  google-public-dns-a.google.com

Address:  8.8.8.8

*** google-public-dns-a.google.com can't find werelds.nu: Server failed

nslookup werelds.nu 4.2.2.1

Server:  a.resolvers.level3.net

Address:  4.2.2.1

Non-authoritative answer:

Name:    werelds.nu

Address:  109.71.49.230

-----------

Thank you

[Bryan Price]

On Tue, Sep 22, 2015 at 8:12 AM, <ju...@pdfen.nl> wrote:

Hello,

Could you please add ns1.satserver.nl,ns2.satserver.nl and ns3.satserver.nl to do the whitelist, since the domain werelds.nu is not resolved anymore:

------------

nslookup werelds.nu 8.8.8.8

Server:  google-public-dns-a.google.com

Address:  8.8.8.8

*** google-public-dns-a.google.com can't find werelds.nu: Server failed

nslookup werelds.nu 4.2.2.1

Server:  a.resolvers.level3.net

Address:  4.2.2.1

Non-authoritative answer:

Name:    werelds.nu

Address:  109.71.49.230

-----------

Thank you

While http://dnsviz.net/d/wereids.nu/dnssec/ looks good, you've got more problems than just Google.  It looks like the only DNS resolving your domain is currently Level 3.  114dns, OpenDNS (not listed, I just added it to the list that I check, and I'm not recopying my results!) and Comcast also do no resolve it.


c:\>nslookup wereids.nu 8.8.8.8
*** google-public-dns-a.google.com can't find wereids.nu: Non-existent domain

Server:  google-public-dns-a.google.com
Address:  8.8.8.8


c:\>nslookup wereids.nu 114.114.114.114
*** public1.114dns.com can't find wereids.nu: Non-existent domain

Server:  public1.114dns.com
Address:  114.114.114.114


c:\>nslookup wereids.nu 75.75.75.75
*** cdns01.comcast.net can't find wereids.nu: Non-existent domain

Server:  cdns01.comcast.net
Address:  75.75.75.75


c:\>nslookup wereids.nu 4.2.2.1
Non-authoritative answer:

Server:  a.resolvers.level3.net
Address:  4.2.2.1

Name:    wereids.nu
Addresses:  198.105.254.11
      198.105.244.11


c:\>f:\bind\dig @8.8.8.8 wereids.nu

; <<>> DiG 9.10.1 <<>> @8.8.8.8 wereids.nu

; (1 server found)
;; global options: +cmd

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 47207
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;wereids.nu.            IN    A

;; AUTHORITY SECTION:
nu.            1648    IN    SOA    catcher-in-the-rye.nic.nu. hostmaster.nic.nu. 2015092210 28800 3600 864000 7200

;; Query time: 36 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Sep 22 16:31:53 Eastern Daylight Time 2015
;; MSG SIZE  rcvd: 109


c:\>f:\bind\dig @114.114.114.114 wereids.nu

; <<>> DiG 9.10.1 <<>> @114.114.114.114 wereids.nu

; (1 server found)
;; global options: +cmd

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 42429
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;wereids.nu.            IN    A

;; AUTHORITY SECTION:
nu.            3553    IN    SOA    catcher-in-the-rye.nic.nu. hostmaster.nic.nu. 2015092210 28800 3600 864000 7200

;; Query time: 52 msec
;; SERVER: 114.114.114.114#53(114.114.114.114)
;; WHEN: Tue Sep 22 16:31:53 Eastern Daylight Time 2015
;; MSG SIZE  rcvd: 109


c:\>f:\bind\dig @75.75.75.75 wereids.nu 

; <<>> DiG 9.10.1 <<>> @75.75.75.75 wereids.nu

; (1 server found)
;; global options: +cmd

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 34271
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;wereids.nu.            IN    A

;; AUTHORITY SECTION:
nu.            7074    IN    SOA    catcher-in-the-rye.nic.nu. hostmaster.nic.nu. 2015092210 28800 3600 864000 7200

;; Query time: 14 msec
;; SERVER: 75.75.75.75#53(75.75.75.75)
;; WHEN: Tue Sep 22 16:31:53 Eastern Daylight Time 2015
;; MSG SIZE  rcvd: 109


c:\>f:\bind\dig @4.2.2.1 wereids.nu

; <<>> DiG 9.10.1 <<>> @4.2.2.1 wereids.nu

; (1 server found)
;; global options: +cmd

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31199
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;wereids.nu.            IN    A

;; ANSWER SECTION:
wereids.nu.        10    IN    A    198.105.254.11
wereids.nu.        10    IN    A    198.105.244.11

;; Query time: 29 msec
;; SERVER: 4.2.2.1#53(4.2.2.1)
;; WHEN: Tue Sep 22 16:31:53 Eastern Daylight Time 2015
;; MSG SIZE  rcvd: 60


From Florida, USA ISP Comcast

[ad...@decorprice.com]

Hi,

I am also facing issues with this.
We got to know about the issue through Google Search Console(see screnshot attached)

Here is the response of my nslookup

nslookup decorprice.com 8.8.8.8
Server:        8.8.8.8
Address:    8.8.8.8#53

Non-authoritative answer:
Name:    decorprice.com
Address: 162.252.104.154

Google please whitelist us

[ad...@decorprice.com]

Hi,

I am also facing issues with this.
We got to know about the issue through Google Search Console(see screnshot attached)

Here is the response of my nslookup

nslookup decorprice.com 8.8.8.8
Server:        8.8.8.8
Address:    8.8.8.8#53

Non-authoritative answer:
Name:    decorprice.com
Address: 162.252.104.154

Google please whitelist us

[Shen Wan]

I just checked and all of our servers resolve the domain fine. Is this still an issue for you? If so, please tell us which location do you experience trouble resolving this domain.

[nvanga...@gmail.com]

Hi,

I am having trouble resolving my domain nielsgl.com with Google's DNS servers. This is the result from my terminal:

nslookup nielsgl.com 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53

but with other name servers it works fine:

$ nslookup nielsgl.com 4.2.2.1

Server: 4.2.2.1

Address: 4.2.2.1#53

Non-authoritative answer:

Name: nielsgl.com

Address: 104.236.134.55

and

$ nslookup nielsgl.com 208.67.222.222
Server: 208.67.222.222
Address: 208.67.222.222#53
Non-authoritative answer:
Name: nielsgl.com

Address: 104.236.134.55 

It seems to be a problem with these servers:

dns1.registrar-servers.com 

dns2.registrar-servers.com 

dns3.registrar-servers.com 

dns4.registrar-servers.com 

dns5.registrar-servers.com

which I got from my hosting provider.

Any help is kindly appreciated!

Thanks in advance!

 - Niels 

[Bryan Price]

On Tue, Mar 8, 2016 at 2:26 PM, <nvanga...@gmail.com> wrote:

Hi,

I am having trouble resolving my domain nielsgl.com with Google's DNS servers. This is the result from my terminal:

nslookup nielsgl.com 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53

DNSSEC issues.

http://dnsviz.net/d/nielsgl.com/dnssec/