*.af.mil no longer resolving under Cloudflare

Zero Trust 1.1.1.1
1

Good morning,
A number of my co-workers and I who use the 1.1.1.1 resolver on home PCs are finding it impossible to connect to our teleworking sites under the *.af.mil domain as of this past Friday (6 Nov 2020).

As an example, here is my nslookup output:

c:\Windows>nslookup www.af.mil 1.1.1.1
Server: one.one.one.one
Address: 1.1.1.1

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** one.one.one.one can’t find www.af.mil: Server failed

c:\Windows>nslookup www.af.mil 1.0.0.1
Server: one.one.one.one
Address: 1.0.0.1

*** one.one.one.one can’t find www.af.mil: Server failed

c:\Windows>nslookup www.af.mil 8.8.8.8
Server: dns.google
Address: 8.8.8.8

Non-authoritative answer:
Name: e11218.dscb.akamaiedge.net
Addresses: 2600:1402:19:29f::2bd2
2600:1402:19:28c::2bd2
23.73.94.114
Aliases: www.af.mil
www.afpw.af.mil.edgekey.net

c:\Windows>nslookup -class=chaos -type=txt id.server 1.1.1.1
Server: one.one.one.one
Address: 1.1.1.1

Non-authoritative answer:
id.server text =

    "ATL"

c:\Windows>nslookup -class=chaos -type=txt id.server 1.0.0.1
Server: one.one.one.one
Address: 1.0.0.1

Non-authoritative answer:
id.server text =

    "ATL"

For the moment, we’ve all switched back to Google’s DNS in order to continue working from home.
Has anyone else encountered this?

2

Hello @gpgrizzle,

Sorry for the trouble, it should work now.

1 Like
3

@anb, thank you!
I’ve just double-checked and it seems to work just fine. I guess now I can go clear out my hosts file…

4

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.