I have been noticing a *lot*, lately -- one day in three-ish -- that my Sprint 4G phone will, for a lengthy but apparently random period between 0100 and 0300EST, lose the ability to resolve DNS names using the resolvers that I am provided by Sprint. I think I reported a version of this before, but hadn't nailed down quite what was going on then. I have since found the SetDNS app, and proved that during these outages -- during which FB and Twitter, frex, still worked, because they had internally cached the relevant server IPs, but web browsing would not and neither would manual DNS lookup with testing tools -- if I used SetDNS to switch to, say, openDNS, then everything immediately started working. If I then disabled SetDNS and rebooted (cause there seems no way to get SetDNS to reset the addresses it found), it immediately broke again. So, is this poorly managed scheduled maintenance on *both* the resolvers that Sprint hands me? Or something else? Anyone else with Sprint LTE (non-Spark) in the Tampa or other markets who can confirm or deny? Cheers, -- jra -- Make Election Day a federal holiday: http://wh.gov/lBm94 100k sigs by 12/14 Jay R. Ashworth Baylink jra@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://baylink.pitas.com 2000 Land Rover DII St Petersburg FL USA #natog +1 727 647 1274