Eye friendly ip monitor with dns lookup?

[lleachii]

@thejoke123

only resolves local hostnames,not out

• Fix WAN DNS resolution
• I surmise this issue is related to your thread about setting up WARP and DNS resolution thru the tunnel and my warning

@lleachii

Lastly:

@thejoke123

option endpoint_host 'engage.cloudflareclient.com'

WAN must use a DNS that doesn't route over WG.

@thejoke123

changed

option endpoint_host 'engage.cloudflareclient.com'

to

option endpoint_host '162.159.192.1'

You must recall that you setup your device to use Cloudflare - additionally not to use DNS to lookup the endpoint name; but rather use its IP - so that it can connect without DNS resolution.

Now you want DNS resolution on WAN - so you'll need to fix this:

@thejoke123

config interface 'wan'
        option device 'eth1'
        option proto 'dhcp'
        option peerdns '0'

option peerdns '1' should work without need to add custom ones. Then reload network. Any DNS settings on WAN should work and route thru WAN - because you only setup LAN clients as SRC to use WG with IP routes/rules (i.e. your routing policy). Additionally, you setup LAN clients to use 1.1.1.1 (i.e. Cloudflare) as DNS instead of the OpenWrt via DHCP Option No. 6. The OpenWrt should use the ISP/WAN IP address as SRC for lookups - and hence use WAN for DNS resolution - which should fix your issue with DNS resolution on the Connections page.

(If you don't know the consequences of your configs, you may want to re-think setting up your device in that manner - or ask.)