pfSense 2.5.2 CE - DNS Resolver periodically stops working (ongoing)
-
I have to create a new post as a continuation of my post pfSense 2.5.2 CE - DNS Resolver periodically stops working:
DNS Resolver periodically (several times a week, at different times) stops working. And it doesn't restore itself. pfSense 2.5.2 (Community Edition), unbound 1.12.0.
...which was unfortunately marked as ‘Post content was flagged as spam by Akismet.com’.
I want to answer @steveits:
@steveits said in pfSense 2.5.2 CE - DNS Resolver periodically stops working:@oleg_v_les You said "restarted" unbound...so it was not stopped? In that case the Watchdog won't help because it starts stopped services. You wrote above it was crashing.
I hadn't heard of the buffer issue w/r/t shaping. I pulled up an SG-3100 router with shaping and there are 3 of those logged in the past 3 months. I did a quick search and found this Reddit post which says updating Realtek drivers was a solution...what kind of NIC do you have? Realtek gets talked down in this forum a lot, and I have seen a few posts in the last 3-6 months about updating Realtek drivers.
Steve, I apologize for misleading you about ‘crashing’! I meant rather ‘dysfunction’.
Thank you for the Realtek drivers updating post; I followed it but with no results, unfortunately. I mean, there are still the lines ‘No buffer space available’ in resolver.log. But the DNS resolving dysfunction has not yet manifested itself after the driver update. However, it takes time to monitor that…
I have also changed my hardware and I’m waiting for the results… I’ll describe the details a bit later. -
@SteveITS I have changed my hardware completely in attempting to avoid the issue.
Unfortunately it turned out each external (detachable) NIC I have is really Realtek (even if it seems as from another vendor). And each PC I might use for pfSense has the only internal (embedded) NIC. So I replaced the PC with a faster one and also the external NIC with another model (but still Realtek):
Before:
- Bare metal,
- Intel Core 2 Duo,
- 1 GB RAM,
- int. NIC ‘Intel(R) PRO/1000 Network Connection’,
- ext. NIC ‘RealTek 8169/8169S/8169SB(L)/8110S/8110SB(L) Gigabit Ethernet’ (aka TP-Link TG-3269(UN) ver.3.3);
Now:
- Bare metal,
- Intel Core i5-2400,
- 4 GB RAM,
- int. NIC ‘Atheros AR8151 v2.0 PCIe Gigabit Ethernet’,
- ext. NIC ‘RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet’ (aka TP-Link TG-3468(UN) ver.3.0).
And I also have updated the Realtek driver (as I mentioned in the previous post).
Now I’m waiting for the results… It might take a time (up to a week)...