On 2021-09-22 19:28, Warren Kumari wrote:
On Wed, Sep 22, 2021 at 1:01 PM Brown, William wrote:
We have a school district that is trying to resolve the domain
deltamath.com [1]. This issue is impacting the classroom use of
this service.
The authoritative servers are tani.ns.cloudflare.com
From: dns-operations On Behalf Of Erik
Stian Tefre
Sent: Wednesday, September 22, 2021 3:38 PM
To: dns-operations@lists.dns-oarc.net
Subject: Re: [dns-operations] Oddness with Cloudfare authoritative servers
> Possibly not a DNS issue at all, but something like this:
>
The correct thing to do is to contact the service provider and say that you are
getting inconsistent
DNS results. That when you only get back 172.64.80.1 it doesn’t work.
Mark
> On 23 Sep 2021, at 05:58, Brown, William wrote:
>
> From: dns-operations On Behalf Of Erik
> Stian Tefre
> Sent:
We have a school district that is trying to resolve the domain deltamath.com.
This issue is impacting the classroom use of this service.
The authoritative servers are tani.ns.cloudflare.com and
jarred.ns.cloudfare.com. Tani seems to work correctly. Jarred however, will
return two different
On Wed, Sep 22, 2021 at 1:01 PM Brown, William wrote:
> We have a school district that is trying to resolve the domain
> deltamath.com. This issue is impacting the classroom use of this service.
>
>
>
> The authoritative servers are tani.ns.cloudflare.com and
> jarred.ns.cloudfare.com. Tani
On Wed, Sep 22, 2021 at 7:26 PM Adam David wrote:
> This does not seem to be a DNS resolution/misconfiguration issue on
> Cloudflare's end.
>
> https://172.64.80.1/ provides an error message (as it should) indicating
> it is a CloudFlare IP. If you can't see that in a web browser, then the
>
Oh, testing now gives a different / working result:
$ curl -v https://www.deltamath.com --connect-to deltamath.com:443:172.64.80.1
2>&1 | grep "HTTP/2 200"
So, looks like the issue is likely resolved.
W
On Wed, Sep 22, 2021 at 7:49 PM Warren Kumari wrote:
>
>
> On Wed, Sep 22, 2021 at 7:26 PM
This does not seem to be a DNS resolution/misconfiguration issue on
Cloudflare's end.
https://172.64.80.1/ provides an error message (as it should) indicating it
is a CloudFlare IP. If you can't see that in a web browser, then the issue
is local to your network.
The main causes that I gather
On Wed, Sep 22, 2021 at 7:38 PM Ethan Katz-Bassett
wrote:
> Cloudflare in particular is experimenting with returning different IP
> addresses to different queries for all kinds of reasons:
> https://mislove.org/publications/IP-Unbound-SIGCOMM.pdf
>
Yup — but in this case, at least one of the
