| 25 May 2021 |
 alexey96 | Redacted or Malformed Event | 17:39:25 |
 andi- | Maybe dnsmasq is just overloaded by the amount of filters you have? How many are there? Have you tried removing the fiters to see if that improves anything? | 17:39:30 |
| alexey96 | I am using configuration suggested here: https://github.com/NixOS/nixpkgs/issues/61617#issuecomment-623934193 | 17:41:01 |
| alexey96 | Same block-lists from pi-hole repository | 17:41:19 |
| alexey96 | except for listen address, i have added machine's static address to resolve inbound requests | 17:42:39 |
| alexey96 | and have opened TCP and UDP ports 53 | 17:43:08 |
| alexey96 | It is in loop indeed. Have just checked log file:
May 25 20:44:22 dnsmasq[27139]: forwarded router.asus.com.home to 192.168.1.1
May 25 20:44:22 dnsmasq[27139]: query[A] router.asus.com.home from 192.168.1.1
May 25 20:44:22 dnsmasq[27139]: forwarded router.asus.com.home to 192.168.1.1
May 25 20:44:22 dnsmasq[27139]: query[A] router.asus.com.home from 192.168.1.1
May 25 20:44:22 dnsmasq[27139]: forwarded router.asus.com.home to 192.168.1.1
May 25 20:44:22 dnsmasq[27139]: query[A] router.asus.com.home from 192.168.1.1
May 25 20:44:22 dnsmasq[27139]: forwarded router.asus.com.home to 192.168.1.1
May 25 20:44:22 dnsmasq[27139]: query[A] router.asus.com.home from 192.168.1.1
May 25 20:44:22 dnsmasq[27139]: forwarded router.asus.com.home to 192.168.1.1
May 25 20:44:22 dnsmasq[27139]: query[A] router.asus.com.home from 192.168.1.1
May 25 20:44:22 dnsmasq[27139]: forwarded router.asus.com.home to 192.168.1.1
May 25 20:44:22 dnsmasq[27139]: query[A] router.asus.com.home from 192.168.1.1
May 25 20:44:22 dnsmasq[27139]: forwarded router.asus.com.home to 192.168.1.1
| 17:45:22 |
| alexey96 | I have a stock AsusWRT on my router and i have no way of disabling it broadcasting itself as secondary DNS for local domain | 17:47:34 |
| alexey96 | So the only option to prevent this looping is removing it from resolv.conf on the NixOS machine and i have trouble with this | 17:48:29 |
| alexey96 | * So the only option to prevent this looping is removing ip 192.168.1.1 from resolv.conf on the NixOS machine and i have trouble with this | 17:49:03 |
| alexey96 | Network and dnsmasq configs: # DNS server
services.dnsmasq.enable = true;
services.dnsmasq.extraConfig = ''
domain-needed
bogus-priv
no-resolv
server=208.67.220.220
server=8.8.8.8
listen-address=::1,127.0.0.1,192.168.1.100
bind-interfaces
cache-size=10000
log-queries
log-facility=/tmp/ad-block.log
local-ttl=300
conf-file=/etc/nixos/assets/hosts-blocklists/domains.txt
addn-hosts=/etc/nixos/assets/hosts-blocklists/hostnames.txt
# address=/nixos.home/192.168.1.100
'';
| 17:51:21 |
| alexey96 | networking.useDHCP = false;
networking.interfaces.eno0.useDHCP = true;
networking.interfaces.wlp2s0.useDHCP = true;
networking.nameservers = [ "127.0.0.1" "::1" ];
| 17:52:55 |
| andi- | That log is interesting. As you've set no-resolv it should only use the server statements to do the resolving. What arguments is dnsmasq launched with? | 17:53:04 |
| alexey96 | How can i get that information? | 17:54:46 |
| andi- | systemctl cat dnsmasq should show you the cmdline that process was launched with | 17:55:03 |
