Googleadservices

[t84a]

More:

[EricPerl]

The DNS lookup from OPN (last screenshot) is a dead giveaway that this particular FQDN is blocked (0.0.0.0) by OPN or its upstream server(s).

You can identify the process handling DNS using

Code Select Expand

sockstat | grep :53Console or ssh.

Then you can dig in the configuration of that service.

Edit: ping failed on OPN because the DNS query returned 0.0.0.0 (typical blocked behavior) from OPN.
As you can see from your last post, if you resolve externally, you can ping that site from your Windows machine.

[t84a]

Thanks. Unfortunately, we're starting to get above my head.

[EricPerl]

Let's assume you are using Unbound (default on OPN) then.

Take screenshots of the General, Overrides, Blocklist (advanced mode checked), Query Forwarding, and DNS over TLS config pages.

[t84a]

Thanks Eric.

[Patrick M. Hausen]

You have a blocklist enabled. What do you expect? It blocks ads - that's the point. Disable the blocklist feature and the problem will be solved.

[t84a]

You have a blocklist enabled. What do you expect? It blocks ads - that's the point. Disable the blocklist feature and the problem will be solved.

Post #1

[Patrick M. Hausen]

So if you disable the blocklist, then restart Unbound, you still get 0.0.0.0?

[t84a]

So if you disable the blocklist, then restart Unbound, you still get 0.0.0.0?

[Patrick M. Hausen]

And the result of an nslookup on that desktop system with the error message gives what address?

[t84a]

And the result of an nslookup on that desktop system with the error message gives what address?

[Patrick M. Hausen]

Is that a web page that performs a lookup? I meant open a command line window and type "nslookup www.googleadservices.com" followed by the ENTER key. When you receive IP addresses, no filtering is taking place. When you receive "0.0.0.0" *something* is still filtering that request.

You have problems connecting to googleadservices.com from a PC behind your OPNsense, right? So a web service somewhere on the Internet performing a lookup is pretty worthless. We need to check what your PC receives.

[verfluchten]

Is that a web page that performs a lookup?

It looks like some sort of Network Tools web site, so the OP is not running this from their system/LAN while they should.

None of this is rocket science. If something is not working on the Internet, you have one or several of the following reasons:
1. DNS server is not resolving.
- It simply does not have an address record for the name.
- It has but refuses to resolve, i.e. has a block.
2. hosts file overrides DNS resolution.
3. Firewall is blocking.
4. You are using a proxy that is blocking the address.
5. You are using a personal firewall on your device.
When you suspect that DNS or firewall are blocking, you ssh into the OS and use its shell to run nslookup or ping, to eliminate anything on your device or your LAN before the OS router.
Copy/paste this comment into a text file and keep it for future reference.

[t84a]

Is that a web page that performs a lookup? I meant open a command line window and type "nslookup www.googleadservices.com" followed by the ENTER key. When you receive IP addresses, no filtering is taking place. When you receive "0.0.0.0" *something* is still filtering that request.

You have problems connecting to googleadservices.com from a PC behind your OPNsense, right? So a web service somewhere on the Internet performing a lookup is pretty worthless. We need to check what your PC receives.

From Command Prompt, all zero

[t84a]

Is that a web page that performs a lookup?

It looks like some sort of Network Tools web site, so the OP is not running this from their system/LAN while they should.

None of this is rocket science. If something is not working on the Internet, you have one or several of the following reasons:
1. DNS server is not resolving.
- It simply does not have an address record for the name.
- It has but refuses to resolve, i.e. has a block.
2. hosts file overrides DNS resolution.
3. Firewall is blocking.
4. You are using a proxy that is blocking the address.
5. You are using a personal firewall on your device.
When you suspect that DNS or firewall are blocking, you ssh into the OS and use its shell to run nslookup or ping, to eliminate anything on your device or your LAN before the OS router.
Copy/paste this comment into a text file and keep it for future reference.

I'm basically using OPNSense with no modifications.  It does it from my phone as well when connected to wifi.