I've been using the Date/Time Library with an NTP clock on a project lately. I have it re-sync with my NTP every hour and I find my drift over that hour is more then sufficient.
My question is related to the design of the library itself. It appears the Date/Time library is using millis() to keep it's time current. I don't see anything to handle the over flow of millis() which occurs about every ~54 days. Is there some compensation for this overflow spill in the library that I'm missing? I don't see anything in the documentation either.