Eye friendly ip monitor with dns lookup?

[thejoke123]

like this, with dns lookup, integrated openwrt feature not working correctly i just need to see who is connecting to whos ip

[frollic]

@thejoke123

integrated openwrt feature not working correctly

what's wrong with it ?

[thejoke123]

does not dns resolve hostname lookup of destination ips so i want to know if there is something better

[frollic]

@thejoke123

does not dns resolve hostname lookup of destination ips

so it's (probably) not actually broken, but doesn't provide the functionality you're looking for ... ?

@thejoke123

i want to know if there is something better

adguardhome ?

[thejoke123]

i have a crappy router

AdGuard Home

[frollic]

there's a "off LAN" version, where you use their DNS, over internet, but I don't know how capable it is, and if the features you require come for free.

[lleachii]

@thejoke123

does not dns resolve hostname lookup of destination ips

Did you hit the button for it to resolve hostnames?

[thejoke123]

Yes and not working only resolves local hostnames,not out

[thejoke123]

Sounds neat

[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.)

[thejoke123]

is there any possible way to config DOT or DOH, while WARPing ?

[thejoke123]

but that would use my isp dns which are heavily compromised and also crappy:S

[frollic]

For the router itself, which shouldn't be an issue ?

[lleachii]

@thejoke123

is there any possible way to config DOT or DOH, while WARPing ?

• Are you asking about the LAN clients configured to use WARP/1.1.1.1 (i.e. a topic for your previous thread); or
• Are you asking about the router?

In both cases, yes, it's possible.

@thejoke123

but that would use my isp dns which are heavily compromised and also crappy

@lleachii

work without need to add custom ones.

Then simply add custom ones.