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
Copy file name to clipboardExpand all lines: dns_dhcp.rst
+27-1Lines changed: 27 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -220,6 +220,33 @@ To increase the limit from the CLI, run the following commands: ::
220
220
This option is not exposed in the UI, but the change will persist across updates and will not be overridden by the UI.
221
221
222
222
223
+
.. _dns_dhcp_domain_set_refresh-section:
224
+
225
+
Domain set refresh timing
226
+
-------------------------
227
+
228
+
:ref:`Domain set <domain_sets-section>` entries are refreshed when dnsmasq performs a new lookup for the domain.
229
+
When responses are served from the local cache instead of performing a new lookup, the IP addresses are not re-added to the set.
230
+
This can cause intermittent gaps if the ipset expires before the DNS TTL expires, or if the cache prevents dnsmasq from performing fresh lookups.
231
+
Note that Adblock may alter dnsmasq behavior and affect domain set refreshing.
232
+
233
+
A cron job runs every 10 minutes to refresh all domain sets, but it also depends on dnsmasq performing actual lookups rather than serving cached results.
234
+
235
+
To resolve domain set refresh issues, adjust the DNS cache TTL settings:
236
+
237
+
.. code-block:: text
238
+
239
+
uci set dhcp.@dnsmasq[0].max_cache_ttl=300
240
+
uci set dhcp.@dnsmasq[0].max_ttl=300
241
+
uci commit dhcp
242
+
reload_config
243
+
244
+
These settings ensure that cached entries expire promptly, allowing dnsmasq to perform fresh lookups and properly update domain sets.
245
+
Please note that setting will override the default TTL provided by upstream DNS servers.
246
+
Such a low TTL may increase the number of queries sent to upstream DNS servers, which can lead to increased network traffic and potential
247
+
performance issues if the upstream servers have rate limits or if there are many clients making frequent DNS requests.
248
+
Use this configuration with caution and monitor the system's performance after applying it.
249
+
223
250
DNS Rebind Protection
224
251
---------------------
225
252
@@ -363,4 +390,3 @@ External references
363
390
364
391
- `OpenWrt DNS and DHCP documentation <https://openwrt.org/docs/guide-user/base-system/dhcp>`_
0 commit comments