Google Public DNS does not resolve some domains.

In the past few months, complaints from users began to arrive that mail from their partners often did not reach them. Mail is raised on its own server, so I began to study the logs. But there was nothing criminal in the logs. In addition, all the test letters that I sent to this domain from my mailboxes were excellent, and, with a shrug, I decided that these were some local problems.

After a while, I got the log of sending a letter to our domain from another server, and then I was struck on the head like an ax. It turns out that their DNS informs the mail server that the domain name is not recognized.

Naturally, I immediately checked the domain registration, which showed that the domain is active, paid until next year and delegated to the registrar's DNS server. Began to make requests for all available dns-servers:
')
Request for own DNS servers:

Z:\>nslookup ufsin45.ru ╤: serv.domain.local Address: 10.45.15.249    : ╚ : ufsin45.ru Address: 85.249.4.35 

Request to root a-server:

 Z:\>nslookup ufsin45.ru a.dns.ripn.net 128.232.193.in-addr.arpa nameserver = int3.dns.ripn.net 128.232.193.in-addr.arpa nameserver = ns.relarn.ru 128.232.193.in-addr.arpa nameserver = int2.dns.ripn.net int2.dns.ripn.net internet address = 195.209.10.37 int3.dns.ripn.net internet address = 194.226.76.90 int3.dns.ripn.net AAAA IPv6 address = 2001:6d0:ffd9:316:194:226:29:50 ╤: UnKnown Address: 193.232.128.6 ╚ : ufsin45.ru Served by: - ns2.nameself.com ufsin45.ru - ns1.nameself.com ufsin45.ru 

And the most interesting thing is Google’s favorite Public DNS:

 Z:\>nslookup ufsin45.ru 8.8.8.8 ╤: google-public-dns-a.google.com Address: 8.8.8.8 *** google-public-dns-a.google.com    ufsin45.ru: Server failed Z:\>nslookup ufsin45.ru 8.8.4.4 ╤: google-public-dns-b.google.com Address: 8.8.4.4 *** google-public-dns-b.google.com    ufsin45.ru: Server failed 

Knowing how many admins (yes, I think, many providers sin with this) without bothering to put these easily remembered numbers of ip-addresses as the main name-servers, I understand that our domain is losing visitors and, most importantly, trust in the postal service.

And not only to ours. Around this time, the user complained to me that he could not send mail to some very important person to his official address. Looking in the logs, I saw the same line that the DNS server could not recognize the domain name. Quickly changing the address of the transfer from Google's public servers to the addresses of Yandex public servers on our local DNS servers, everything went fine.

I honestly tried to find in the jungle of Google technical support, who can be contacted with this problem, but apparently they have a public name-server as a kind of secondary service, without infrastructure and support. And, judging by the increasing demands on the forums on Google products , on other forums, as well as the verbal reviews of their colleagues, this problem is gaining momentum and, perhaps, soon another free service of the Dobra Corporation will disappear into oblivion ...

PS After stormy discussions, with the help of a respected company, I come to the conclusion that Google is guilty only in the mega-popularity of its resolver.
But the final cause has not yet been found ...

PPS I don’t know whether the positive energy of the habrasoobshchestvo had such an impact, or if someone from the people involved in the problem read this post and corrected it quietly, maybe the mystical poltergey “played yes gave” and maybe it affected the SOA update, but now everything earned. All 21 servers have registered our domain. Once again, many thanks to all who answered, May the Great Information Force arrive with you! :)