Re: [public-dns-discuss] Google's DNS not working for some domains; affecting emails. No problems with non-Google DNS

Message has been deleted

Yunhong Gu

unread,

Aug 16, 2012, 10:39:25 AM8/16/12

to public-dn...@googlegroups.com

I found that the two name servers that serves ({ns310, ns371}.csoft.com) these domains occasionally timeout our queries. if you manages these domains, you may contact them.

This list of IP addresses may be helpful: https://developers.google.com/speed/public-dns/faq#locations

Thanks

Yunhong

On Tue, Aug 14, 2012 at 2:54 AM, <joe...@gmail.com> wrote:

Hi,

It appears that I am seeing some DNS problems that is affecting MX resolution and is breaking mail (gmail, calendar notifications, et cetra) sent from Google's machines.

This is happening with at least three domains: tajchiu.com, joechiu.com, and tcavjohn.com

When I query 8.8.8.8, I currently get valid results -- but the problem has been affecting email delivery for at least 3 days now -- so whatever Google DNS servers the Google mail servers are using is apparently broken.

Thanks for any help you can provide with this!

Sincerely,
Joseph

--
========================================================
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
========================================================

Joseph Chiu

unread,

Aug 30, 2012, 12:06:03 PM8/30/12

to public-dns-discuss

When this problem last occured, I did various DNS queries to csoft's
DNS servers, to other ISP's DNS servers, and even Google's public DNS
server at 8.8.8.8. I did not get DNS timeouts from any of the sources
that I tried; yes, at the same time, at least one of your mail servers
was still reporting DNS delay problems.

Moreover, this problem has come back in the last few days again, where
non-Gmail e-mails are successfully delieverd, every day and throughout
the day, to the affected domains, but the DNS server queried by the
affected Gmail server was continuing to return bad DNS resolution.
I'm not entirely sure this is a Google public-DNS problem, or if
there's a separate internal DNS system that Google maintains, but I
still suspect that it is a DNS problem inside Google.

I have seen this problem reported recently for a few other domains:

http://productforums.google.com/d/topic/gmail/da2Zrc4VNX8/discussion
http://productforums.google.com/d/topic/gmail/bWTX_VUAtLA/discussion
http://productforums.google.com/d/topic/gmail/v9EYITRmQpQ/discussion
http://productforums.google.com/d/topic/gmail/An5vPR6Sk3U/discussion

There is one intriguing possibility that I will check now -- that the
SOA/serial number might need to get bumped up
https://groups.google.com/d/topic/public-dns-discuss/UluoITOlbww/discussion

On Aug 16, 7:39 am, Yunhong Gu <g...@google.com> wrote:
> I found that the two name servers that serves ({ns310, ns371}.csoft.com)
> these domains occasionally timeout our queries. if you manages these
> domains, you may contact them.
> This list of IP addresses may be helpful:https://developers.google.com/speed/public-dns/faq#locations
>
> Thanks

Yunhong Gu

unread,

Aug 31, 2012, 1:25:51 AM8/31/12

to public-dn...@googlegroups.com

On Fri, Aug 31, 2012 at 12:22 AM, <kev....@gmail.com> wrote:

On Friday, August 31, 2012 2:06:03 AM UTC+10, Joseph Chiu wrote:
Moreover, this problem has come back in the last few days again, where
non-Gmail e-mails are successfully delieverd, every day and throughout
the day, to the affected domains, but the DNS server queried by the
affected Gmail server was continuing to return bad DNS resolution.
I'm not entirely sure this is a Google public-DNS problem, or if
there's a separate internal DNS system that Google maintains, but I
still suspect that it is a DNS problem inside Google.

I'm now quite convinced that this is a problem with Gmail, or with the DNS that it uses (whatever that might be).

It is likely to be a problem (networking or firewall) beween some resolvers and the two name servers - TIMEOUT happened to certain location only. We have started to investigate this.

Thanks

Yunhong

Recently affected emails are ending up failing permanently, but in the previous episode (around Aug 13), some mails were delivered days late. Here's one set of headers from an affected email, they clearly indicate that the delay (~ 28hrs) is within Gmail/Google's internal network. Specifically, 10.50.219.161 looks to be implicated. I have a few more emails, but would have to dig them out. Obviously I would love to see headers for more recent emails, but as they haven't been delivered (and now bounced back as a permanent failure), I can't.

Received: from mail-gh0-f179.google.com (mail-gh0-f179.google.com [209.85.160.179])
        by mail63.csoft.net (Postfix) with ESMTP id 9EF3128437
        for <.....@pulo.com.au>; Mon, 13 Aug 2012 10:24:40 -0400 (EDT)
Received: by ghbg2 with SMTP id g2so2835479ghb.38
        for <.....@pulo.com.au>; Mon, 13 Aug 2012 07:24:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
        :cc:content-type;
        bh=wcvgaFUKOqrsP1D10uaFNCdHSCJIdTFgfvBOy6DcLjM=;
        b=U+8lkQrvDEqXXc79nA+bFL52NWXGTF17CQahFEvlsXGrMl9R8/jfRNqs/HOyJDUDEj
        5ODEM3+yH+CKk62ypb3worN3inveZOo0rgLrJHHzG2UuyxMUfpBUzJTeC/qUa8NPRG30
        JDx2j2RaNXY5fJnWGHfc6q5p3aGEUtLbXd0nQ4u6u0Pyhy564YFaDYsCVdFofKYPXUME
        iJL1RY331YORWlX5qbbpPTbY901LCOlsstUKW0S71nCVg3Ih/jEOcZYeWkCAHreX1VEZ
        2cofZIHR1bwpc6zTEqD6RR26wUiDO7Qb/C1KU5tuAX0wsHTOLUJGUCq8E4Upkl+76UMx
        F02g==
MIME-Version: 1.0
Received: by 10.50.219.161 with SMTP id pp1mr2626805igc.19.1344765776913; Sun,
        12 Aug 2012 03:02:56 -0700 (PDT)
Received: by 10.64.93.233 with HTTP; Sun, 12 Aug 2012 03:02:56 -0700 (PDT)

Yunhong Gu

unread,

Aug 31, 2012, 1:44:35 AM8/31/12

to public-dn...@googlegroups.com

On Fri, Aug 31, 2012 at 1:25 AM, Yunhong Gu <g...@google.com> wrote:

On Fri, Aug 31, 2012 at 12:22 AM, <kev....@gmail.com> wrote:

On Friday, August 31, 2012 2:06:03 AM UTC+10, Joseph Chiu wrote:
Moreover, this problem has come back in the last few days again, where
non-Gmail e-mails are successfully delieverd, every day and throughout
the day, to the affected domains, but the DNS server queried by the
affected Gmail server was continuing to return bad DNS resolution.
I'm not entirely sure this is a Google public-DNS problem, or if
there's a separate internal DNS system that Google maintains, but I
still suspect that it is a DNS problem inside Google.

I'm now quite convinced that this is a problem with Gmail, or with the DNS that it uses (whatever that might be).

It is likely to be a problem (networking or firewall) beween some resolvers and the two name servers - TIMEOUT happened to certain location only. We have started to investigate this.

Thanks
Yunhong

This should have been resolved (it is indeed networking/firewall issue and it is not a problem of mail server or DNS resolving process).

Reply all

Reply to author

Forward