Fortigate 60c 504 DNS look up failed

[Voke]

Hello Everyone I have a fortigate 60c that serves as UTM, i have enabled web proxy On all client pc, i have added the ip of the proxy appliance problem is users keep getting 504 DNS look up failed when browsing How do i solve this?

[FortiRack_Eric]

explicit proxy on a 60C is a bad idea. To little perf/resources, stick to implicit proxy.

[Voke]

Thanks securelayers-eric Please how do i apply the implicit proxy. Thanks

[Christopher_McMullan]

These two KB articles came up after a quick search. I' ve used the first one myself. They can be a little opaque at times, but the first is generic, and uses two FortiGates in the examples. You could just as well use one FortiGate with two VDOMs, if this is really something you want to shoot for... Technical Note: Sample configuration of FortiGate WCCP server and client (traffic redirector and transparent proxy), with verification and troubleshooting procedures http://kb.fortinet.com/kb/microsites/search.do?cmd=displayKC&docType=kc&externalId=FD32926&sliceId=1&docTypeID=DT_KCARTICLE_1_1&dialogID=63662107&stateId=0%200%2063664072 WAN Optimization, Web Cache, Explicit Proxy, and WCCP (PDF Document) http://kb.fortinet.com/kb/microsites/search.do?cmd=displayKC&docType=kc&externalId=fortigate-wanopt-cache-proxy-40-mr3pdf&sliceId=&docTypeID=DT_PRODUCTDOCUMENTATION_1_1&dialogID=63662107&stateId=0%200%2063664072

[Voke]

Hello Everyone This is what i have done to disable explicity proxy on fortigate 60C on the interface (internal) i have unchecked the explicity proxy box on the explicity proxy i have also unchecked the http/https box i have also removed the ip address on the web browser i have also deleted the web proxy policy still yet i am unable to browse is there something am missing?

[Christopher_McMullan]

Run a sniff and a flow trace and post it here for comments.

[Voke]

i disabled the explicit web proxy feature and everything seems to work just fine thanks

[Christopher_McMullan]

Be aware that disabling the feature in the GUI only hides it from display - it has no impact on the feature' s actual operation. Something else changed behind the scenes over time which allowed you to browse again. Glad to hear it' s resolved, in any case!