Insanely weird issue with DNS resolution to www.cdc.gov

johnpoz

I have been checking on this now and then... They are still freaking hosed.. They clearly made some sort of changes - but its still a freaking mess..

If you don't understand how to dnssec - just don't do it.. A borked dnssec is worse than not having it that is for damn sure..

edit:
Just some of the errors still being seen

RRSIG cdc.gov/A alg 7, id 42473: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1).
RRSIG cdc.gov/DNSKEY alg 7, id 42473: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1).
RRSIG cdc.gov/DNSKEY alg 7, id 65139: DNSSEC specification recommends not signing with DNSSEC algorithm 7 (RSASHA1NSEC3SHA1).

chewie198

I had been experiencing this issue myself for the last several months and it wasn't until my wife complained about it last week that I decided to investigate and came across this thread. I actually went ahead and submitted a message via their contact form and linked to this exact forum thread describing the issue. It's hard to say whether that was the impetus for their finally updating their DNS records, but it does at least seem to be working correctly now without using the 'domain-insecure: "cdc.gov"' workaround. Big thanks to everybody who actually took the time to discover the underlying issue. Now hopefully they don't break it again.

Imtech

This DNS issue for www.cdc.gov site should have been resolved. If anyone is still seeing similar issues, please let CDC know at imtech@cdc.gov. Thank you!

espalmer

This was driving me nuts also. Needed to access the CDC for Covid info and check in after vaccination. Yes "lucky" enough to get one, unless you count having a compromised immune system as not lucky :)

At first I blamed my pfsense and Ngblocker setup as I make ALOT of mistakes as I am just learning. But I found NO errors....I then found this topic and adding the server: domain-insecure: "cdc.gov" solved the issue.

Thanks I was getting ready to pull my DNS setup apart to figure out where I screwed up..........

johnpoz

Not sure I would call it "fixed" while its better - they still have stuff wrong if you ask me.. They are using algos they shouldn't be.

If your not going to follow best practices for dnssec - why even try and use it to be honest..

From RFC 8624

   +--------+--------------------+-----------------+-------------------+
   | Number | Mnemonics          | DNSSEC Signing  | DNSSEC Validation |
   +--------+--------------------+-----------------+-------------------+
   | 1      | RSAMD5             | MUST NOT        | MUST NOT          |
   | 3      | DSA                | MUST NOT        | MUST NOT          |
   | 5      | RSASHA1            | NOT RECOMMENDED | MUST              |
   | 6      | DSA-NSEC3-SHA1     | MUST NOT        | MUST NOT          |
   | 7      | RSASHA1-NSEC3-SHA1 | NOT RECOMMENDED | MUST              |
   | 8      | RSASHA256          | MUST            | MUST              |
   | 10     | RSASHA512          | NOT RECOMMENDED | MUST              |
   | 12     | ECC-GOST           | MUST NOT        | MAY               |
   | 13     | ECDSAP256SHA256    | MUST            | MUST              |
   | 14     | ECDSAP384SHA384    | MAY             | RECOMMENDED       |
   | 15     | ED25519            | RECOMMENDED     | RECOMMENDED       |
   | 16     | ED448              | MAY             | RECOMMENDED       |
   +--------+--------------------+-----------------+-------------------+

They are using 7.. plus their NS listed have issues.

gov to cdc.gov: The following NS name(s) were found in the authoritative NS RRset, but not in the delegation NS RRset (i.e., in the gov zone):
icdc-us-ns1.cdc.gov,
icdc-us-ns3.cdc.gov,
icdc-us-ns2.cdc.gov

gov to cdc.gov: The following NS name(s) were found in the delegation NS RRset (i.e., in the gov zone), but not in the authoritative NS RRset: 
auth00.ns.uu.net, 
auth100.ns.uu.net

But hey if its actually working, better than it was ;)

Gertjan

@johnpoz said in Insanely weird issue with DNS resolution to www.cdc.gov:

I would contact the cdc webmaster and show him that above dnsviz link.. Tell him to fix his shit..

Or : he was fired after all, and the new one wiped everything.

https://dnsviz.net/d/www.cdc.org/dnssec/ is clean for me. No more issues.

That is : www.cdc.org becames like the other 85 % (?) of the net : no DNSSEC.
( so, all is well, www.cdc.org is DNS spoofable again ).

https://dnsviz.net/d/www.cdc.org/dnssec/

@espalmer said in Insanely weird issue with DNS resolution to www.cdc.gov:

domain-insecure: "cdc.gov" solved the issue.

shouldn't be needed any more as they cleaned up (very recently ?).

Btw : Compare with this site : https://dnsviz.net/d/forum.netgate.com/dnssec/
No DNSSEC neither, and no need to inform unbound about it.

Maybe Netgate should activate DNSSEC, just to show that DNSSECworks without any settings on the 'viewers' side (neither our pfSense). After all, its about 'network' security and so.

msf2000

@johnpoz
I know this is very late, but CDC still hasn't fixed everything.

But thank you for the server directive tip. That resolved the issue for me.

server:domain-insecure: "cdc.gov"

johnpoz

Yeah I still show it as a big mess..

But at least they are only warnings, and not full on failures, etc.

gregarios

I'm also having this exact issue now on a Turris Omnia 2020 router with DNSSEC enabled or disabled and forwarding to OpenDNS turned on. If I bypass the router and use direct OpenDNS numbers on my computer I can get to cdc.gov but when I use the router's DNS which is supposed to send my requests up stream to OpenDNS it won't let it through. I don't even get the Block page from OpenDNS it just acts like it won't resolve in the router at all. Other sites seem to work just fine.

I've manually added cdc.gov numbers to the router's /etc/hosts file and it works for now, but this is too hacky and not sustainable, really. Also would like to know how many other sites on the internet aren't working unbeknownst to me.

DrPhil

I stumbled on this thread because I was having the same issue right now. I use openDNS on DNS resolver (unbound) on Pfsense (Netgate device).

I used JohnPoz domain override suggestion as a band aid, and it works. For other non-sophisticated home users like myself, here's an example of how to do it on the WebGUI.

Services / DNS Resolver / General Settings

"8.8.8.8" is Google's DNS and for some reason tolerates the incorrect DNS setup at cdc.gov (as described in this thread by people who understand such stuff).

Gertjan

@drphil :

https://cachecheck.opendns.com/

cdc.gov
and
www.cdc.gov

did resolve for me.

Maybe your own 'opendns' settings are to strict ?

gregarios

@gertjan My openDNS settings are set correctly since directly using them from my computer works fine. Only when the router uses forwarding does it not work.

Gertjan

@gregarios said in Insanely weird issue with DNS resolution to www.cdc.gov:

@gertjan My openDNS settings are set correctly since directly using them from my computer works fine. Only when the router uses forwarding does it not work.

The 'DNS' settings might be ok.
But OpenDNS - chekc your OpenDNS account - can use 'filters' like : nothing, no adds - no spam - no sex - no bitcoin - no whatever.

Again, check the (non filtered) OpenDNS resolver manually : https://cachecheck.opendns.com/
It resolves.

Depending on what you use as for a filtering
If your not uses any filtering on the OpenDNS side, then why use OpenDNS ? Use the real, build in stuff, : the official 13 root servers == use the resolver as your Resolver. Easy to set up, easy to maintain. Plain works.

Btw : Finally, the admins of cdc.org finally ditched DNSSEC support.
https://dnsviz.net/d/www.cdc.org/dnssec/

gregarios

@gertjan As I said... my setting on the router and my computer are correct. I have tested it by connecting successfully to the CDC using OpenDNS numbers on my computer. If I use the router's DNS that forwards to the same OpenDNS IP addresses, it does not work. If my filters were too strict it would not work when I connected to it from my computer.

I'll have to retest this though since now CDC has dropped their DNSSEC. Yesterday it was active and in error mode.

Gertjan

@gregarios said in Insanely weird issue with DNS resolution to www.cdc.gov:

I'll have to retest this though since now CDC has dropped their DNSSEC. Yesterday it was active and in error mode.

I saw the same thing.
First time it look clean like that : just a non DNSSEC domain.

No DNSSEC errors.

OpenDNS is a Resolver, you have to check with their policies, but I can image that if a domain announces "I have DNSSEC" that it should be implemented correctly. If not, well, it should fail.

If you were using the Resolver as a resolver, you could use an option in the custom box that excludes cdc.gov from any DNSSEC issues.
Maybe OpenDNS offers also such a possibility.

edit : Oh sh*t. OpenDNS has become less 'open' : it's bought by Cisco .... well. What to say : great ! (?)

johnpoz

I have not seen that - they still have a shit ton of errors.. If you do not know how to do dnssec - then you shouldn't even attempt to do it.. Which is what I suggest they should do.. Since clearly they have no idea how to do it correctly.

Its still a horrible mess as of test just did
2021-05-17 09:56:53 UTC

Gertjan

@johnpoz :

Strange, asked a new "Analysis" this morning, and it looked some what ok.

Re tested again just now, and it's pure BS again !

Now, I'm just a European guy, and I know one has to go to "cdc" when things go bad ( learned this from the Walking Dead ? ).
It looks like an important governmental agency to me.

edit : oh, wait : www.irs.gov isn't any better. And no one is complaining .....

gregarios

Just more proof the currnt U.S. government doesn't react in the slightest to any "warnings" — only flat-out catastrophic failure.

Gertjan

@gregarios
It's just an admin ** messing up.
I don't think using or adding DNSSEC is a governmental decision.
And give them some time, this issue started more then a year ago, not everybody (admins) have been replaced yet ;)

** On both sides : pfSense, using default DNS settings, works just fine.

DrPhil

@gertjan

To answer your question

If your not uses any filtering on the OpenDNS side, then why use OpenDNS ?

I am using their free family filter DNS. 208.67.222.123.
(I am a home user and need the filtering).

Use the real, build in stuff, : the official 13 root servers == use the resolver as your Resolver. Easy to set up, easy to maintain. Plain works.

I would love to. Is there an easy way to setup a filter that I don't have to maintain on an ongoing basis? I am willing to put in the time / effort upfront. I tried pfBlockerNG, but didn't like the experience and gave up.

Btw : Finally, the admins of cdc.org finally ditched DNSSEC support.
https://dnsviz.net/d/www.cdc.org/dnssec/

Whatever they did, isn't working for me yet. And I have a feeling it's not OpenDNS filtering that's causing the issue but an incorrect setup on CDC's side. (could it be that you're looking at cdc.org instead of cdc.gov?)

oh, wait : www.irs.gov isn't any better. And no one is complaining

irs.gov is working fine for me (through my openDNS setup). Whatever is making cdc.gov fail, it does not share with irs.gov