Okay so that means there is corruption in DNS. No surprisingly, since I have a Sprint WiFi cell data dongle which won’t work or work well when I use the default DNS, but when I switch to Google DNS it starts working famously.
Another possible cause would be DNS cacheing. Changing the DNS setting will wipe the cache, so it is possible you may have had some old cache data that was not getting purged when it became stale. In the future, on PC’s use ipconfig /flushdns and on OS X (Tiger and beyond I believe) use dscacheutil -flushcache. As I mentioned, once you change the DNS this happens automagically. Bob On Feb 15, 2014, at 11:43 , Richmond <richmondmathew...@gmail.com> wrote: > On 15/02/14 21:30, Mark Wieder wrote: >> Richmond- >> >> Hmmm... possible dns resolution issues? >> Can you ping www.livecode.com ? >> If not, can you ping 37.59.205.89 ? >> >> You might also try reconfiguring your dns settings to point to >> Google's dns servers at 8.8.8.8 to see if that helps. >> > > pinging 37.59.205.89 perfectly well. > > I edited /etc/resolv.conf with leafpad but putting this at the end: > > |nameserver 208.67.222.222 > nameserver 208.67.220.220 > nameserver 202.51.5.52 > > and "bingo", everything is lovely. > > Thank you so much for your advice. > > Richmond. > | > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
