You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Very strange issue here. inotify running on a router serving as DNS server.
If i nslookup a local name from CLI, it correclty resolves through the local DNS server.
If i nslookup the very same name inside a inotify pipe or loop, the query is sent to the WAN dns server failing.
Sample script:
#!/bin/sh
echo "Resolving out of the loop"
nslookup accesspoint.lan
echo "Looping"
inotifywait -m /tmp/dhcp.leases -e delete,close_write,move |
while read action; do
nslookup accesspoint.lan
done
Sample output
Resolving out of the loop
Server: 127.0.0.1
Address: 127.0.0.1:53
Name: accesspoint.lan
Address: 192.168.1.2
Non-authoritative answer:
Looping
Setting up watches.
Watches established.
Server: 2001:4860:4860::8888
Address: [2001:4860:4860::8888]:53
** server can't find accesspoint.lan: NXDOMAIN
** server can't find accesspoint.lan: NXDOMAIN
as you can see the first nslookup correctly uses the local DNS server, but the second uses directly the google ipv6 DNS server (that is the server setup for my WAN connection)
i honestly have no idea
thanks
The text was updated successfully, but these errors were encountered:
Maintainer: @dangowrt - Daniel Golle [email protected]
Environment: X86-64 - Both 23.05.5 and 24.10-RC4
Description:
Very strange issue here. inotify running on a router serving as DNS server.
If i nslookup a local name from CLI, it correclty resolves through the local DNS server.
If i nslookup the very same name inside a inotify pipe or loop, the query is sent to the WAN dns server failing.
Sample script:
Sample output
as you can see the first nslookup correctly uses the local DNS server, but the second uses directly the google ipv6 DNS server (that is the server setup for my WAN connection)
i honestly have no idea
thanks
The text was updated successfully, but these errors were encountered: