I can think of a couple of compelling reasons:
1. They need to swap in the information about the new products and update information (including pricing) on existing products
2. No website can handle the kind of instantaneous load that making sure everyone has heard the presentation relieves
Nice theory, except in most cases with Apple the new product is not available in the store even after they bring it online.
I bet they didn't make any significant changes other than renewing their domain that had lapsed.
I don't think the domain lapsed. I can make changes to my dns here at SatelliteGuys and the last updated will also say today. The (unconfirmed) word I am getting was that one of their major backend servers failed, so they had to update the DNS to point to one of their backup servers.
The big question I have is why the DNS is taking so long propagate?
Taking a look they have the TTL set to a short 300 seconds on both dish.com and mydish.com
; <<>> DiG 9.7.3 <<>> @localhost dish.com ANY
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52145
;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;dish.com. IN ANY
;; ANSWER SECTION:
dish.com. 300 IN TXT "v=spf1 a:mailout1.dishnetwork.com a:mailout2.dishnetwork.com a:mailout3.dishnetwork.com a:mailout.dish.com ~all"
dish.com. 300 IN TXT "google-site-verification=1IRiy-kCjwaI5A4YNTSXLEE8AcxiRHwy70qtmV3RET4"
dish.com. 300 IN TXT "google-site-verification=AlAM-2gDHPArMMBv4LvQrNEnZAGEzUngNT2H-5hY4u0" "" ""
dish.com. 300 IN MX 10 mailin.dish.com.
dish.com. 3600 IN SOA ns-1.dishnetwork.com. hostmaster.dishnetwork.com. 246 900 600 86400 3600
dish.com. 187 IN A 66.170.250.4
dish.com. 3600 IN NS ns-2.dishnetwork.com.
dish.com. 3600 IN NS ns-1.dishnetwork.com.
;; Query time: 172 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Feb 5 18:31:21 2014
;; MSG SIZE rcvd: 451
There is a DNS issue out there somewhere.