Home
Help
Search
Login
Register
OPNsense Forum
»
Archive
»
22.1 Legacy Series
»
DNSMasq becoming unresponsive every day or two
« previous
next »
Print
Pages: [
1
]
Author
Topic: DNSMasq becoming unresponsive every day or two (Read 1371 times)
thefunkygibbon
Jr. Member
Posts: 81
Karma: 2
DNSMasq becoming unresponsive every day or two
«
on:
February 25, 2022, 12:09:46 pm »
Hi all,
Not sure what else I can put really, i've been using DNSMasq for my DNS for the last week or two
I'm finding that in this time, a disconcerting number of times it seems, randomly, all internet stops.
Trying to troubleshoot exactly what has happened I worked out it was DNS that was the fault. I restarted DNSMasq and everything starts working again.
Log files show nothing that i can make out (from what I can see it was still receiving a lot of DNS requests, just wasn't doing anything with them (supposed to upstream to my pihole).
Anyone else having issues? or is there anything i can tweak/change to make it less prone to these sort of issues?
Logged
thefunkygibbon
Jr. Member
Posts: 81
Karma: 2
Re: DNSMasq becoming unresponsive every day or two
«
Reply #1 on:
February 26, 2022, 10:15:58 am »
any suggestions? please?
Logged
franco
Administrator
Hero Member
Posts: 17661
Karma: 1611
Re: DNSMasq becoming unresponsive every day or two
«
Reply #2 on:
February 28, 2022, 12:48:30 pm »
Is dnsmasq still running in these cases?
# pgrep dnsmasq
Anything in the respective log or on "dmesg" output?
What sort of dnsmasq configuration do you use? Do you use advanced settings via include directory?
Cheers,
Franco
Logged
thefunkygibbon
Jr. Member
Posts: 81
Karma: 2
Re: DNSMasq becoming unresponsive every day or two
«
Reply #3 on:
February 28, 2022, 08:41:49 pm »
yeah its still running. Looking through the log files it still seems to be 'doing stuff' although from the clients perspective thats a big fat lie.
config wise its not doing a lot. I've got a convoluted setup for dns so that everything works, i'd rather NOT have it like this but apparently it's the only way.
client > firewall dnsmasq (so that lan clients can access other lan clients etc via their hostname) > pihole (on server, docker) > firewall unbound (so that pihole can resolve hostnames for reporting etc)
(config of dnsmasq etc can be found -
https://pi-hole.net/blog/2021/09/30/pi-hole-and-opnsense
)
Logged
Print
Pages: [
1
]
« previous
next »
OPNsense Forum
»
Archive
»
22.1 Legacy Series
»
DNSMasq becoming unresponsive every day or two