The error, as quite clearly shown, is DNS related and very likely specific to that network. This isn't a pfSense problem, its a DNS problem. Incidentally, you're running 1.2. Upgrade. 1.2.1 is out.
jose thomas wrote:
Thankyou Chritopher,

Thankyou for your mail.
In fact my another pfSense 1.2 box connecting from another network work fine. The only difference is that the network which have the squid enabled one have the problem for only "www.nytimes.com <http://www.nytimes.com>". I didn't see any other site shown this type of error.

With Best Regards
Jose



On Wed, Dec 31, 2008 at 5:55 PM, Christopher Iarocci <[email protected] <mailto:[email protected]>> wrote:

    Jose,

    I'm not sure I can help you figure out why it is not working for
    you, but I can tell you this which might help you eliminate
    certain things.

    I have version 1.2.1 release of PFSense running with squid and
    squidguard.  Both nytimes.com <http://nytimes.com> and
    www.nytimes.com <http://www.nytimes.com> work fine for me.  I used
    firefox on a windows computer to test it.  My DNS servers are
    internal on the network and my PFSense box also uses the internal
    DNS server.

    Christopher Iarocci

    Network Solutions Manager

    Twin Forks Office Products

    631-727-3354

    *From:* jose thomas [mailto:[email protected]
    <mailto:[email protected]>]
    *Sent:* Wednesday, December 31, 2008 8:21 AM
    *To:* [email protected] <mailto:[email protected]>
    *Subject:* [pfSense Support] Error thrown only for a URL

    Hello,

    I have installed pfSense 1.2 for our Office network and it is
    working perfectly with squid configured.
    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

    "The error is "Network Error (dns_server_failure)
    Your request could not be processed because a error occurred
    contacting the DNS server.
    The DNS server may be temporarily unavailable, or there could be a
    network problem."

    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.

    Can anybody suggest me how to resolve this.

    TIA
    Jose

-- Mobile: +971-50-9943477
    Office: +971-4-4370703
    Residence: +971-4-2232044




--
Mobile: +971-50-9943477
Office: +971-4-4370703
Residence: +971-4-2232044



!DSPAM:495ba2d915805753142211!



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Commercial support available - https://portal.pfsense.org

Reply via email to