Please register to participate in our discussions with 2 million other members - it's free and quick! Some forums can only be seen by registered members. After you create your account, you'll be able to customize options and access all our 15,000 new posts/day with fewer ads.
"Internet users face the risk of losing their internet connections on 5 May when the domain name system switches over to a new, more secure protocol.
While the vast majority of users are expected to endure the transition to DNSSEC smoothly, users behind badly designed or poorly configured firewalls, or those subscribing to dodgy ISPs could find themselves effectively disconnected...."
The vast, overwhelming majority of home internet users just use their ISP's DNS server, or perhaps a public DNS server such as the one's Google provides (8.8.8.8 for example). These users will not be affected by the adoption of DNSSEC, unless the organization who runs their DNS server was not ready for the switch. If your ISP is really dodgy, maybe you should write down the IP addresses of a few public DNS servers in case your ISP really buggers things up.
When they talk about "incompatible firewalls", they're talking about firewalls that pass DNS requests from a DNS server you are running, inside your firewall, to the outside world. Most of us do not run our own DNS server. Our DHCP clients get pointed at our router, and our router talks to our ISP's DNS server. The "incompatible firewall" problem doesn't affect people who don't run their own DNS server.
Yet another example of the media trying to make a mountain out of a molehill. They blew their wad on Y2K, though. I don't think they will ever get the public as afraid about nothing as they did then.
Yet another example of the media trying to make a mountain out of a molehill. They blew their wad on Y2K, though. I don't think they will ever get the public as afraid about nothing as they did then.
Y2K was the best. I enjoyed that paranoia. A lot of people made a lot of money on it, though. lol
Computers were going to think it was 1900, right?
That very phrase is contradictory. "Computers were going to think...."
A computer doesn't know that 00 is a lower number then 99. It just knows that it is the next number in the sequence.
Location: Mableton, GA USA (NW Atlanta suburb, 4 miles OTP)
11,334 posts, read 26,086,242 times
Reputation: 3995
Quote:
Originally Posted by Peregrine
Y2K was the best. I enjoyed that paranoia. A lot of people made a lot of money on it, though. lol
Computers were going to think it was 1900, right?
That very phrase is contradictory. "Computers were going to think...."
A computer doesn't know that 00 is a lower number then 99. It just knows that it is the next number in the sequence.
There are several issues. If you store a date as two digits and prepend a "19" to the year field, then 01/01/00 will appear as 01/01/1900 in many displays. There were many occurrences of this.
We had a serious but more subtle issue in the application I worked on at the time which showed up in testing ... most of the system stored date/time info as a large integer representing accumulated minutes past a given start date (I think Jan 1, 1967), and the conversation table in the library routine that almost all applications used to convert back and forth had arbitrarily been created only through December 31, 1999.
The system was originally brought online itself in 1967, though, so I can cut them some slack for choosing to build a table only 33 years into the future.
And yes, it's still running, at least if United Airlines still runs UNIMATIC in its original TIP+AIS environment ... the NWA version is being turned off by Delta (hiss) and replaced with whatever Delta uses. Too bad; I suspect WorldFlight is a better system in some ways. Hopefully Delta's MGL system is at least smart enough to allow FLEX (reduced thrust) takeoffs.
Please register to post and access all features of our very popular forum. It is free and quick. Over $68,000 in prizes has already been given out to active posters on our forum. Additional giveaways are planned.
Detailed information about all U.S. cities, counties, and zip codes on our site: City-data.com.