9.11 can't validate sss.gov
warren at kumari.net
Mon Jan 22 16:21:49 UTC 2018
Unrelated to the DNS bit, but still silly / annoying:
http://www.sss.gov works OK, but http://sss.gov always seems to return
"The requested service is temporarily unavailable. It is either
overloaded or under maintenance. Please try later.".
There is a fair bit os disagreement over if a bare domain should
resolve / have a web-server listening, but ISTM that if you *do*, you
should have it work -- I wonder how many people have tried the bare
domain and never realized that adding in the 'www' "fixes" it.
On Mon, Jan 22, 2018 at 11:08 AM, Timothy A. Holtzen
<tah at nebrwesleyan.edu> wrote:
> I've informed the selective service (sss.gov) of the issue. They have
> supposedly passed it on to their "web support group". We will see if
> anything happens but I'm not holding my breath. At least a government
> agency should have more influence to get qwest to fix their servers than
> I do.
> Timothy A. Holtzen
> Campus Network Administrator
> Nebraska Wesleyan University
> Public PGP key CFB4 3AE8 B726 DEBF 00D9 CCFC 426E 76AF DABC B3D7
> On 01/19/2018 05:04 PM, Mark Andrews wrote:
>> Yes, qwest were informed years ago that there severs are broken. Report this to the .gov site operators. The servers return BADVERS to the queries which was never part of the EDNS spec and is a invention of the servers developers. FORMERR was permissible by STD13 but this was tightened when the EDNS spec was revised to say ignore unknown EDNS options.
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list
> bind-users mailing list
> bind-users at lists.isc.org
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
More information about the bind-users