pfsense url not resolved

troubleshooting74

we've a problem to reach some url , i've just make a policy , to solve this problem , but it persist .

Jarhead

@troubleshooting74
Thanks for letting us know.

troubleshooting74

@jarhead

i'm doing a new rule in floating area with source and destination area by 80 port

Gertjan

@troubleshooting74 said in pfsense url not resolved:

to reach some url

What url ?
pfSense, out of the box, will work with everything on the Internet.
That is, as long as there are no issues along the road (and back).

Jarhead

@troubleshooting74 said in pfsense url not resolved:

@jarhead

i'm doing a new rule in floating area with source and destination area by 80 port

How about you actually tell us what the problem is with some details. "I have a problem" tells us nothing.

There's no need for floating rules.

troubleshooting74

@jarhead said in pfsense url not resolved:

due , some url destination is not resolved , it's responding from ping , from lan with prompt and from ping trough pfsense

stephenw10

If it responds to a ping request it must be resolving.

So how exactly are you testing? And what is the exact error you're seeing?

Steve

troubleshooting74

@stephenw10

ERR_CONNECTION_TIMED_OUT

this is a result of browser surfing

rcoleman-netgate

@troubleshooting74 Can you provide screen shots of the rules you mentioned earlier you have implemented? Any information about your configuration would be helpful at this point as you've provided mostly riddles.

stephenw10

Ok so it resolves and you get no reply.

Did this happen before you added the 'policy'?

What exactly did you add?

Do you have more than one WAN?

Steve

troubleshooting74

@rcoleman-netgate

rcoleman-netgate

@troubleshooting74 What are the rest of the rules on the LAN interface? Again, please, provide more information to make it easier to help you -- if people feel like they have to pull teeth to get details they won't engage or follow-up.

troubleshooting74

@troubleshooting74

troubleshooting74

@stephenw10 only 1 wan

rcoleman-netgate

@troubleshooting74 Why do you have this rule:

LAN already passes all traffic, you showed that in your other screen shot. If you are disabling that rule and only using this one now you lack DNS if your client is told to use a public DNS server.

What is at 31.11.32.177? You only allow TCP so if that's a DNS server you aren't allowing UDP53.

Again... the more information you provide the more likely we can help