![]() ![]() It's unlikely (though I wouldn't past Comcast - they are known for being unreliable) that your internet is cutting out every hour. It seams that I can not have a log over an entire day because it is flushed. I ironically found the issue to be related to DNSMasq as once I disabled a few things via shell there were no more unreplied messages. I can se that on the graph because it was cleared and the new graph start from 10.00 AM. Apparently then it was flushed automaticly. The log was recorded from 00.00 AM until 10.00 AM. If someone can confirm this, than it I will leave the setup as it is.īack to actually what was my first question, flushing the log. I guess thats it, I have to let router as custom1 upstream dns so local names are resolved. server: the upstream DNS servers (since I enabled no-resolv). ![]() I dont like it, as it can mess with temporary failures in name resolution. Once you have the information, you should be able to set it up using DD-WRT. Lets dissect one by one: no-resolv: dont read /etc/nf, as Ill specify the upstream DNS servers myself, right into this nf. What I have read on this forum is to let pihole manage dhcp and local names but I do not want that. If you arent registered, register one and setup (add) your dynamic domain name first. You can also use SmartDNS to use DoH and or DoT. Under Static DNS 1,2,3 add your own trusted DNS servers e.g. Under WAN Connection Type you should tick/enable 'Ignore WAN DNS' to stop the ISP DNS server added to your DNS servers. It appears the issue is that the Pi's DNS requests are being intercepted regardless of what rules I attempt to put on the router. Gateway and Local DNS should be kept at its default 0.0.0.0. Local names and dhcp are managed from my router. Entering the commands you suggested breaks the internet and causes a loops with hundreds of unreplied DNS queries showing in the DDWRT connections log within a very short space of time. UDP Unreplied timeout is often set to 30 by default in consumer routers) a. Why are then mostly all request from 192.168.1.222 (pihole) to router (192.168.1.1) and back from 192.168.1.1 to 192.168.1.222, unreplied?Īlready tried that, you ar right I know that, but if i remove 192.168.1.1 from upstream dns custom1 then pihole does not resolve my local names any more. occurs when Local DNS records and XProxyServerRedundancy are enabled in the. ![]()
0 Comments
Leave a Reply. |