securedparty
DD-WRT Novice
Joined: 07 Dec 2017
Posts: 31
|
 Posted: Sat Jan 24, 2026 11:26 Post subject: R6260 as DNS+DHCP Server, issues |
 |
| Quote: | I recently switched units going from E2500 to R6260 as a DNS and DHCP server for my local network. All worked good when using the E2500, not one hiccup. I had mainly switched from the one to the other because I could wall mount the R6260.
For the R6260 I had initially used the r6260-webflash (01-17-2026-r63391).bin as the first firmware, but encountered an issue.
It seems that after the initial doling out of DHCP on the local network, that the devices cannot seem to renew their IPs?
What ends up happening is I restart the R6260, disconnect and reconnect devices and they'll eventually find a renewed IP address.
When I was having issues with r63391, I moved down to 03-12-2025-r60269, which another router was on that didn't appear to be having trouble. I still ran into the issue again, so I moved on down to match the firmware on the E2500, 07-01-2023-r53133.
So I am moved to firmware DD-WRT v3.0-r53133 std (07/01/23) on the R6260. The issue still persists.
The settings between the old E2500 device and the R6260 are identical, yet the R6260 appears to hold the same issue.
On the Services page, I am using DNSMasq, "Additional Options." On the setup page I am using "Use dnsmasq for DNS" and "DHCP-Authoritative" turned on.
Dnsmasq Infrastructure
Enable dnsmasq - Enable
Encrypt DNS - Disable
Cache DNSSEC Data - Disable
Validate DNS Replies (DNSSEC) - Disable
Check Unsigned DNS Replies - Disable
No DNS Rebind - Enable
Query DNS in Strict Order - Disable
Add Requestor MAC to DNS Query - Disable
RFC4039 Rapid Commit Support - Disable
Any suggestions? Does anyone else using a Netgear R6260 experience a related issue? |
Disregard. The issue was spotted in under Setup > Basic Setup page, where even though there were statically assigned devices, the "Maximum DHCP Users" under section "Dynamic Host Configuration Protocol (DHCP)" was set too low.
While I had only included provision for the for actual intended maximum number of devices to receive IPs that were not otherwise pre-unassigned, it was having an effect on devices that were assigned a static IP address.
So, I learned that the "Maximum DHCP Users" includes those who are assigned a static IP address in addition to those that are not assigned a static IP address.
So, instead of setting "Maximum DHCP Users" to 8, I had to set it higher to encompass all devices which are not manually assigned an IP address on the device itself. |
|
