Cannot access website from mac

Hi all,

I have installed openwrt on my router.

I have a strange problem now. I cannot access "" from a mac connected to the network. I tried with an iPhone connected to the network, and it works. Both the mac and iPhone connect to the router via wifi.

Note that the mac can access any other webpage without issue. But the mac cannot even ping or traceroute (via Terminal) "".

I have tried everything I could think of, this problem persists across system reboots, and I've been having this problem for months.

I am a little lost. Any advice on how I can diagnose this issue?


Can you try the following on the mac?
nslookup; nslookup


Hi @trendy, thanks for your help.


Non-authoritative answer:	canonical name =	canonical name =	canonical name =

$ nslookup

Non-authoritative answer:	canonical name =	canonical name =	canonical name =

Name resolution works fine. Try to ping and open a page from the mac to this address and capture on the router the packets.
Install tcpdump on OpenWrt, if it is not there already.
tcpdump -i any -evn -c 50 host


Thanks for that trendy. I won't be able to do it right now, but will try that later.

1 Like


I haven't been able to download tcpdump and analyze the traffic (I need to get familiarized with all this first).

But I have some further info on this issue.

I now have this issue on I can access any other sites without problem, except this one.

What I found out is that if I do
"ping", it blanks out (it can't ping it).

However, if I do an nslookup, I get :


Non-authoritative answer:

and if I ping this IP address ( it does work !

So it seems nslookup directs to the correct IP, but my browser and ping do not.

Any chance that gives more color to understand my problem?

A tcpdump would be more helpful to identify the issue.


Ok, I'll try to sort out the tcpdump. Thanks.


so I have gotten around to installing and running tcpdump in this manner : tcpdump -i br-mynetwork icmp

Unfortunately, it does not show anything.

So here's the situation :

  1. on the mac if I run ping, nothing happens, and nothing shows in the tcpdump in the openwrt router
  2. on the mac, pinging other domains works fine
  3. on the openwrt router itself, ping works fine
  4. on the mac, pinging the underlying ip (found by nslookup works fine

Any clue what I could try now?

Thank you

Oh, I think I have just found a very significant pointer : if I run /etc/init.d/https-dns-proxy restart on the router, everything now works fine !

I run the following version :

/etc/init.d/https-dns-proxy version

on openwrt 19.07.7

Are there known issues?

I am not familiar with this package. Moreover it would help troubleshooting if you had mentioned it earlier. Bottom line is that you need to provide more information on the configuration of this package to understand why it blocks only one domain for one device in your network.

I didn't mention it earlier because I didn't know it was the issue.

Here's the configuration :

config main 'config'
	option force_dns '0'
	list force_dns_port '53'
	list force_dns_port '853'
	option update_dnsmasq_config '-'

config https-dns-proxy
	option listen_addr ''
	option bootstrap_dns ',,2606:4700:4700::1111,2606:4700:4700::1001'
	option resolver_url ''
	option listen_port '5053'

config https-dns-proxy
	option listen_addr ''
	option bootstrap_dns ',,2606:4700:4700::1112,2606:4700:4700::1002'
	option resolver_url ''
	option listen_port '5054'

Because the problem only appears after a while, I am wondering if it's a buffer running out of space, or something like that.

ubus call system board; uci show dhcp; \
netstat -l -n -p | grep -e dnsmasq -e https-dns; \
head -v -n -0 /etc/resolv.* /tmp/resolv.* /tmp/resolv.*/*

Hey thanks @vgaetera.

The problem seems solved for now, thanks for your help!

1 Like

If you're still facing resource exhaustion issues with this proxy, it sounds familiar.
My take is it's an expensive option unless you're okay with no shared network cache.

I've since switched to unbound that has the additional advantage of caching at the router to speed up lookups. I use unbound with nextdns as the forward zone. It has been solidly stable on 19.0x,21.0x and snapshots.

**Documentation: **

With unbound-control you have tooling to perform interrogation of your DNS server performance, metrics e.t.c.

My Configuration

unbound.fwd_nextdns.server='<your-unique-id>' '<your-unique-id>'

dhcp config


Hi @laingo, what you are saying is very interesting.

I want to make sure I understand it fully :

"no shared network cache" I am unclear what you mean by that. Do you mean that there is an option to disable shared network cache that i should consider?

Also, I do think the issue is ressource exchaustion, but I am not 100% certain. Is there a way for me to confirm that's the issue at hand ?


@SharkScout what I meant was that https-radius-proxy is non-caching, so all DNS queries to the router will be forwarded to the upstream (from whichever client).

So unless every client maintains their own cache, each query will get out to the internet including the same query from different clients on your LAN side.

unbound on the other hand, is a proper DNS server just like dnsmasq, with caching support and in-built support for DNS over TLS/HTTPS to an upstream. You can turn off caching in unbound as well - it is just a more robust solution for secure DNS.

1 Like

Ok, I understand. Thanks for the explanation, that makes sense.

I think I looked very briefly into unbound in the past, but felt the config was more complex than https-dns-proxy. So I opted for the latter. Maybe I should revisit this.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.