Hi Paul, Thankyou for your suggestion.
My dig +short www.nytimes.com gives the following j...@jose-laptop:~$ dig +short www.nytimes.com 170.149.173.130 But "nytimes.com" gives the same as yours. I tried it after restarting the browser, and restarting the pfSense cache as well, but with same "Network error" -Jose On Wed, Dec 31, 2008 at 5:57 PM, Paul Mansfield <[email protected]>wrote: > jose thomas wrote: > > However, facing a problem for a single site - www.nytimes.com > > <http://www.nytimes.com>. > > The following error is thrown immediately giving the URL > > http://www.nytimes.com > ... > > If I try "nytimes.com <http://nytimes.com>" it works. > > www.nytimes.com <http://www.nytimes.com> is "ping"able as well as reach > > via traceroute from my PC as well as from the pfSense box. > > I suspect it's temporary... perhaps they're rebuilding a server or > renumbering hosts? > > >dig +short nytimes.com > 199.239.137.245 > 199.239.136.200 > 199.239.136.245 > 199.239.137.200 > > >dig +short www.nytimes.com > 199.239.136.200 > > I can connect to port 80 on all of those IP addresses; restart your > browser in case it has an old IP cached > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > Commercial support available - https://portal.pfsense.org > > -- Mobile: +971-50-9943477 Office: +971-4-4370703 Residence: +971-4-2232044
