Empty answers for A-queries of ukit.com

[opiu...@gmail.com]

We have a three nameservers ns1.ukit.com ns2.ukit.com and ns3.ukit.com. 

The software is PowerDNS 4.1.5 packed into docker containers, the network ports are exposed via docker-proxy (not "--net=host").

The backend for the PowerDNS is "remote", and it interacts with our self-made restful service which serves records from MongoDB.

The problem is that Google's public DNS sometimes returns our SOA record for the queries of A-records, like there is no A-record at all. In result our websites are becoming inaccessible at random time from random locations across the world, according to reports from host-tracker.com (a geo-spread monitoring service) our users also have reported us about theese problems with availability of their sites. We also could get these empty anwers ourselves quering 8.8.8.8 and 8.8.4.4 (approximately 1 from 10 attempts), while other public DNS services seemed not to encountered the same, we tried 1.1.1.1 and 77.88.8.8.

The questions are:

- Why Google's public DNS does so?

- Are there any special requirements for authoritative DNS-servers to be operable normally via Google's public DNS? E.g. response time, answers format etc.

- Is there a way to check compatibility with Google's public DNS ourselves, apart from listed here https://developers.google.com/speed/public-dns/docs/troubleshooting?

Additional info:

The date and time you encountered the problem

Started from 01.30.2019 15-00 UTC.

Your location

ns1 - Moscow, Russia

ns2 - Ashburn, USA

ns3 - Amsterdam, Netherlands

The platform on which you are noticing the problem (e.g. Mac, Windows, router, etc.)

I think it doesn't depend on platform

The hostname(s) for which you are having a problem

ukit.com, ulanding.io, divly.ru (actually there are some more).

Whether the problem is continuous or intermittent

I'd say it's continiously intermittent.

The links to the tools' name server diagnosis report page

https://intodns.com/ukit.com

https://intodns.com/divly.ru

https://intodns.com/ulanding.io

https://www.host-tracker.com/ru/InstantCheck/3/ec227f42-5825-e911-85b2-0003ff73517a/

The output of the commands you ran in the diagnostic tests

http://prntscr.com/mf75m7

http://prntscr.com/mf760v

http://prntscr.com/mf76fl

[Puneet Sood]

The names mentioned appear to be resolving correctly with Google Public DNS now.

Is this still a problem on your end?

On Mon, Feb 4, 2019 at 1:17 PM <opiu...@gmail.com> wrote:
>
> We have a three nameservers ns1.ukit.com ns2.ukit.com and ns3.ukit.com.
> The software is PowerDNS 4.1.5 packed into docker containers, the network ports are exposed via docker-proxy (not "--net=host").
> The backend for the PowerDNS is "remote", and it interacts with our self-made restful service which serves records from MongoDB.
>
> The problem is that Google's public DNS sometimes returns our SOA record for the queries of A-records, like there is no A-record at all. In result our websites are becoming inaccessible at random time from random locations across the world, according to reports from host-tracker.com (a geo-spread monitoring service) our users also have reported us about theese problems with availability of their sites. We also could get these empty anwers ourselves quering 8.8.8.8 and 8.8.4.4 (approximately 1 from 10 attempts), while other public DNS services seemed not to encountered the same, we tried 1.1.1.1 and 77.88.8.8.
>
> The questions are:
>
> - Why Google's public DNS does so?
> - Are there any special requirements for authoritative DNS-servers to be operable normally via Google's public DNS? E.g. response time, answers format etc.
> - Is there a way to check compatibility with Google's public DNS ourselves, apart from listed here https://developers.google.com/speed/public-dns/docs/troubleshooting?

That is our recommended approach.

>
>
> Additional info:
>
> The date and time you encountered the problem
> Started from 01.30.2019 15-00 UTC.
>
> Your location
> ns1 - Moscow, Russia
> ns2 - Ashburn, USA
> ns3 - Amsterdam, Netherlands
>
> The platform on which you are noticing the problem (e.g. Mac, Windows, router, etc.)
> I think it doesn't depend on platform
>
> The hostname(s) for which you are having a problem
> ukit.com, ulanding.io, divly.ru (actually there are some more).
>
> Whether the problem is continuous or intermittent
> I'd say it's continiously intermittent.
>
> The links to the tools' name server diagnosis report page
> https://intodns.com/ukit.com
> https://intodns.com/divly.ru
> https://intodns.com/ulanding.io
>
> https://www.host-tracker.com/ru/InstantCheck/3/ec227f42-5825-e911-85b2-0003ff73517a/
>
> The output of the commands you ran in the diagnostic tests
>
> http://prntscr.com/mf75m7
> http://prntscr.com/mf760v
> http://prntscr.com/mf76fl
>

> --
> 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.
> To post to this group, send email to public-dn...@googlegroups.com.
> Visit this group at https://groups.google.com/group/public-dns-discuss.
> To view this discussion on the web visit https://groups.google.com/d/msgid/public-dns-discuss/abf57182-b419-4ffb-91b7-1c9ff3ea9a1f%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[opiu...@gmail.com]

We switched our pdns-servers to mysql-backend, after this the problem seem to had gone, but we still can't understand the reason. According to our tests the answers are equal with both backends. Is there a way to find it out?

среда, 6 февраля 2019 г., 0:24:53 UTC+3 пользователь Puneet Sood написал:

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