Broken...
It looks like everyone who experienced the DND glitch on the 1st had theirs turn on on the 1st. Those who had it turn on on the 31st (11pm) for me, didn't have the problem on the first.
Fast forward to the 2nd, and all my devices did not turn off. All were set to go on at 11pm on the 1st, and the morning of the 2nd (today) all were still on.
So it's a bug either related to 1/1, or the year 2013 or possibly 1/1/13, and requires the DND feature to activate on 1/1 for it to happen. It matters not when it is programmed to turn off.
----------
This isn't a wide spread problem as my DND is not stuck on as the article suggests after this New Year. I would suggest anyone with there DND stuck on backup and restore there IOS device and sync there device, not restore from the backup as the issue might be something corrupted and replicate itself back from the backup.
You are nuts. Nobody is going to do what you say, completely wiping their phone and setting it up from scratch to resolve a bug that Apple will fix with a hot fix. Who has that kind of time or patience for a device that "just works"?
The option of "TURN THE FEATURE OFF UNTIL IT'S FIXED" is much more palatable than setting up a phone from scratch.
----------
So, running some tests on my iPhone 5 now that this has happened to me (didn't happen yesterday).
I set the feature to turn on in 5 minutes. As SOON as I adjust the turn on time, it turns itself on anyway, even though it's not time to do so. Without fail, it does this. I can turn the feature off manually, then readjust the time for 11pm, 12 hours from now, and as soon as I adjust the time, it turns itself on. But it WON'T turn itself on at the set time once I turn it off manually.
Completely broken.
It's a big bug not necessarily related to 1/1, more likely related to the year 2013.
Did nobody at Apple test this software with a different date and time than real time?