CNAME on the root record of a zone is not allowed. .org servers delegate 021yy.org to ns1/2.booen.com with NS records, so ns1/2.booen.com must supply an SOA and one or more NS records for 021yy.org. Instead they provide an out-of-scope SOA, valid-looking A, MX, and CNAME (which is also a bogus combination) but return NXDOMAIN for NS.

The real answer is that ns1/2.booen.com have a wildcard for * with A, MX, and CNAME records. Somehow they also respond to any SOA request with an SOA for booen.com, and have no NS records.

I still suspect a botnet C&C DNS server is running, with probably a rapidly-changing set of domains delegated to it. Comcast is probably blocking delegations to those servers, and the only real choice (that isn't a lie) for DNS responses would be SERVFAIL (in this case due to policy). NOERROR+no ANSWER records or NXDOMAIN would not really be true.

The DNS for 021yy.org is rather fishy looking. The .org servers have NS records pointing to ns1.booen.com and ns2.booen.com, which have a 20 second time to live (vs. a normal 1 day TTL), which is common in botnet command & control networks. Also, the ns1/2.booen.com servers give answers to 021yy.org A lookups, but return NXDOMAIN for NS lookups (which is completely bogus; NXDOMAIN means that 021yy.org does not exist, not that it doesn't have NS records, which would still be bogus).

The NXDOMAIN for NS records would cause many caching servers to cache NXDOMAIN for all records (not just NS), which would cause the domain to not resolve (depending on the order things were looked up). Basically, I don't see this as a Comcast problem, but rather a problem with the DNS servers for 021yy.org. This may be accidental (although AFAIK no normal DNS server would reply with A records but return NXDOMAIN for NS records), but looks possibly like it is intentional and possibly part of a botnet C&C. There's a lot of that going on lately.

False. Yet another endlessly repeated "truth" based on invalid or non-existent studies.

Oops, yeah, I forgot Apollo 7. They probably would have been able to survive, although it might have been rough. The biggest problem probably would have been that they would not have had much choice in where they landed (could have ended up in a location where recovery was effectively impossible or would take too long, could have hit land instead of water, etc.).

There are risks in spaceflight that just can't really be overcome, except in hindsight. If what happened to Apollo 13 had happened to Apollo 8, the result would have been very different. Apollo 8 had no LM that could have been used as a "lifeboat", and it is unlikely that there would have been any other way to keep the astronauts alive. There's a good chance the Apollo program would have ended if NASA had two consecutive crews killed.

However, one thing from Apollo 8 helped Apollo 13: on Apollo 8, Jim Lovell accidentally erased the flight computer's memory and had to re-figure the position from start sightings. He had to do a similar task during Apollo 13 after the computer was powered down and restarted.

Let's say you and I can both buy a shelf at Wal-Mart for $10. Now I start making shelves for myself instead, and make an exact duplicate of Wal-Mart's $10 shelf. Should my nearest Wal-Mart be required to buy my shelf for $10, transport it to your nearest Wal-Mart, and then sell it to you for $10? They have trucks already, so why should they charge me for the transportation costs?

That's exactly the case. If they charge residential customers $0.10/kWh, you don't think all $0.10 goes to pay for the power plant, do you? They have to transport the power from the plant to the customer's location (which has loss in the system; they have to generate more than 1 kWh to deliver 1 kWh), they have to meter how much the customers use, bill for the usage, maintain the system, etc.

Pick-up and deliver only makes sense when you get more for the delivery than you pay for the pick-up.

What are you, a COBOL programmer? That's nice, we'll get off your lawn now.

The color of a Cray doesn't tell you the model; you could get them in different colors. NASA's were "NASA blue" for example.

Verizon doesn't "choose" ISPs; they _are_ a backbone provider (they don't buy transit from anybody). Cogent is known for peering disputes, as well as selling hard to content providers (and sometimes eyeball networks) they think will give them leverage in peering disputes.

Smaller ISPs (that do buy transit) know that you don't buy from Cogent unless you have at least two other paths to everything on the Internet.

I don't know about Australia, but in the US, you are responsible if you are causing interference in somebody else's licensed band. Even if you didn't mean to, you are transmitting (noise) on a licensed frequency without a license. If it even looks like it might be because you made some modifications to radio gear, you can be liable for a large fine (and depending on the band possibly jail time).

I remember a few years ago a convenience store near Miami's airport was closed by the FCC because they had some dodgy electronics (door opener or bar-code scanner) that was interfering with the air traffic control radio frequency. The FCC forced the store to close (and IIRC shut off the power because they weren't sure of the source device) until they could prove they had non-interfering equipment.

Even the ISM (the so-called "unlicensed") bands, like 900 MHz and 2.4 GHz, are very tightly controlled. Equipment must stay within regulations on channels, power limits, and usage. Your equipment must be able to handle interference from other devices operating within the regulations, but if somebody operates outside the limits, they are liable and must shut down (and face fines, etc.).

Yes, I read the owner's manual for my car. Then I ordered the shop manual and reviewed it as well. There's a lot of good info in there.

No, I couldn't do it; that's what trained experts are for. The concept is not that much different from the US National Weather Service offices issuing storm watches and warnings.

For something like this (where nobody died), you wouldn't attempt an evacuation. I believe that most of the injuries were from broken glass and other falling debris; it would be enough to warn people to either get outside (away from buildings, trees, and other objects that could be blown around by a shock wave) or to stay inside away from windows.

There are variants in the instruction set (just like there are in the x86 world, where i686 is a superset of i383 for example). However, that isn't the big problem with ARM; there isn't a single-standard way of booting like there is with x86 (where most things are IBM PC BIOS compatible, with some now moving to EFI/UEFI). Also, there's no device enumeration like ACPI; lots of ARM vendors build their own kernel with a static compiled-in list of devices, rather than having an easy way to probe the hardware at run-time.

Sure there is - you have to have a Facebook account. Facebook can terminate your account for various reasons (or no reason at all), which could render you unable to receive such information in a timely fashion.