Is that where you have a lot of Assessors going around every website and server and TLD finding out what they're worth and how much tax can be levied from them?
1086 and all that...
Engineers have recommended a small but important change to the internet's underlying structure in order to avoid a possible doomsday scenario. A report [PDF] from the Root Server System Advisory Committee (RSSAC) argues that a key parameter in the internet's address books – namely, how long the information should be stored – …
How about getting someone to write a corrections process that uses functionality similar to Splunk's create-new-extractions. Also one that, when I'm logged in, allows me to simply click a button to submit the correction, since I can't be bothered to look up the email account password just to send an email telling you that you should have already hired a proofreader (or that you need a different one.)
This could have been handled more eligantly by simply making a link of the first instance of the term to it's Wiki article that explained it.
Not being quite old enough to remember back in the early Thousand A.D., I was unaware of the fact that the DomesDay Book meant the DoomsDay Book, an accurate examination of all the property, holdings, & livestock plus the value thereof in order to keep a legal record for The Tax Men. Having now read (located at https://en.wikipedia.org/wiki/Domesday_Book) I am educated to that fact & humbly retract my whiney blurb to the contrary.
But I still think it sounds silly. When I hear "dome" I think of architectural things not the end of the world. I reserve that link for phrases like "Microsoft Works", "Microsoft Linux", and "Ballmer for President".
I know this is a bit OT (we're quite some time from the 5th of November, for one), but the word "bonfire" was originally "bone-fire". It might seem a bit of a pointless factoid except for (a) burning Guy Fawkes in effigy and (b) modern Irish still uses "tine chnámh" (literally "bone fire").
Anyway, I guess I'm just chyming in to support your regurgitation of obsolete/archaic/obscure words. You never know, it might end up giving them a resurgence in use.
So *if* the TLD is DNSSEC signed, *and* a recursive server is validating it, *and* a root server is still answering queries *but* doesn't have sufficient connectivity to get the updated keys, *then* you get a stale signature and so DNSSEC rejects it?
DNSSEC breaks things in much more severe ways than this. Just don't deploy it.
Biting the hand that feeds IT © 1998–2021