Re: DNS resolution for apps vs Terminal?

2016-06-14 Thread Rick Mann
Thanks for the answers. Sigh. A little more investigation showed that it had something to do with my router's DNS cache. Normally, it serves up itself as the DNS server for DHCP clients. When I reconfigured it to serve up Google's DNS servers instead, all apps started working normally. This

Re: DNS resolution for apps vs Terminal?

2016-06-14 Thread Alastair Houghton
On 14 Jun 2016, at 15:13, Michael Nickerson wrote: > >> On Jun 14, 2016, at 5:11 AM, Rick Mann wrote: >> >> Just now Safari stopped being able to load facbook.com. So did Chrome. Both >> reported DNS failures. >> >> But dig on the command line, and

Re: DNS resolution for apps vs Terminal?

2016-06-14 Thread Michael Nickerson
> On Jun 14, 2016, at 5:11 AM, Rick Mann wrote: > > Just now Safari stopped being able to load facbook.com. So did Chrome. Both > reported DNS failures. > > But dig on the command line, and curl, both succeed. > > How are these two domains different? > Safari and

Re: DNS resolution for apps vs Terminal?

2016-06-14 Thread Aandi Inston
Really facbook.com ? If so, maybe it's some kind of protection, the site is owned by MarkMonitor; perhaps there is a blocker on these things. On 14 June 2016 at 10:11, Rick Mann wrote: > Just now Safari stopped being able to load facbook.com. So did Chrome. > Both

DNS resolution for apps vs Terminal?

2016-06-14 Thread Rick Mann
Just now Safari stopped being able to load facbook.com. So did Chrome. Both reported DNS failures. But dig on the command line, and curl, both succeed. How are these two domains different? -- Rick Mann rm...@latencyzero.com ___ Cocoa-dev mailing