Posted: Wed Jul 04, 2018 20:13 Post subject: resolv.conf in 36079
Hi, I have upgraded 6 Netgear routers 36079, all 30-30-30'd and configured through the control panel. All show the same fault: the nameserver line in /etc/resolv.conf is set to the IP address of the router not the control panel value.
5 Atheros & 1 Broadcom
WNDR2200
WNDR3400
WNDR3700v1
WNDR3700v2
WNDR3700v3
WNDR4500
...but I couldn't find an Atheros thread for 36079
I've no idea if this is new in 36079... but they were all factory reset to within an inch of their lives.
Last edited by tsgsh on Fri Jul 06, 2018 8:17; edited 1 time in total
Posted: Wed Jul 04, 2018 21:32 Post subject: Re: resolv.conf in 36079
tsgsh wrote:
Hi, I have upgraded 6 Netgear routers 36079, all 30-30-30'd and configured through the control panel. All show the same fault: the nameserver line in /etc/resolv.conf is set to the IP address of the router not the control panel value.
5 Atheros & 1 Broadcom
WNDR2200
WNDR3400
WNDR3700v1
WNDR3700v2
WNDR3700v3
WNDR450
...but I couldn't find an Atheros thread for 36079
I've no idea if this is new in 36079... but they were all factory reset to within an inch of their lives.
WNDR2200 yes AR7241
WNDR3400 yes BCM4718A1
WNDR3700v1 yes AR7161
WNDR3700v2 yes AR7161
WNDR3700v3 yes BCM4718A1
WNDR450 ???
WNDR4500 BCM4706 wiki says hold reset for 20 seconds...instal guide and peacock says yes
None of these are ARM units
Anyhow maybe some insite
Two of my R6300v2's on r35550M have:
/etc/resolv.conf
search "domain of my internet provider.com"
search "name of my local net"(I use a local DHCP Server)
nameserver "local ip address of router"
/tmp/resolv.dnsmasq
nameserver x.x.x.x (entered in "controle panel" by me)
nameserver x.x.x.x (entered in "controle panel" by me)
nameserver xxx.xx.xx.xx (assigned by my isp)
nameserver xxx.xx.xx.xx (assigned by my isp)
Hope this is helpful _________________ Location 1
R7800- DD-WRT v3.0-r53562 (10/03/23) Gateway
WNDR3400v1 DD-WRT v3.0-r35531_mega-nv64k (03/26/18 ) Access Point
WRT160Nv3 DD-WRT ?v3?.0-r35531 mini (03/26/18 ) Access Point
WRT54GSv5 DD-WRT v24-r33555_micro_generic (10/20/17) Repeater
Location 2
R7800- DD-WRT v3.0-r51855 (02/25/23) Gateway
R6300v2- DD-WRT v3.0-r50671 (10-26-22) Access Point
WNDR3700v2 DD-WRT v3.0-r35531 std (03/26/18 ) Access Point
E1200 v2 DD-WRT v3.0-r35531 mega-nv64k (03/26/18 ) Gateway(for trivial reasons)
RBWAPG-5HACT2HND-BE RouterOS-v6.46.4 (2/21/20) Outdoor Access Point
2x RBSXTG-5HPACD RouterOS-v6.46.4 (2/21/20) PTP Bridge 866.6Mbps-1GbpsLAN
Location 3
2x R7000- DD-WRT v3.0-r50671 (10/26/22) Access Points
2x RBWAPG-60AD RouterOS-v6.45.9 (04/30/20) PTP Bridge 2.3Gbps-1GbpsLAN
2x RBSXTsqG-5acD RouterOS-v6.49.7 (10/14/22) PTP Bridge 866.6Mbps-1GbpsLAN Thank You BrainSlayer for ALL that you do & have done, also to "most" everyone here that shares their knowledge
Posted: Thu Jul 05, 2018 22:48 Post subject: Re: resolv.conf in 36079
mrjcd wrote:
tsgsh wrote:
Hi, I have upgraded 6 Netgear routers 36079, all 30-30-30'd and configured through the control panel. All show the same fault: the nameserver line in /etc/resolv.conf is set to the IP address of the router not the control panel value.
5 Atheros & 1 Broadcom
WNDR2200
WNDR3400
WNDR3700v1
WNDR3700v2
WNDR3700v3
WNDR450
...but I couldn't find an Atheros thread for 36079
I've no idea if this is new in 36079... but they were all factory reset to within an inch of their lives.
See what 'cat /tmp/resolv.dnsmasq' says.
My apologies, the final line is a WNDR4500. Also, I just realised the WNDR3400 is on 33772... ignore that one.
I simply mentioned that they'd been 30-30-30'd just to assure everyone that this was not a residue of an older config.
/etc/resolv.conf reads
Code:
search my.domain.name
nameserver <Local IP Address>
/tmp/resolv.dnsmasq reads
Code:
nameserver <correct nameserver>
OK, if the DHCP Type is DHCP Server, then the DNSMasq setting for DNS has to be off. I'd always interpreted the two DNSMasq settings in the Network Address Server Settings (DHCP) section of the GUI to only be relevant if DHCP Server was enabled, so I just disabled the DHCP Server and didn't turn of DNSMasq for DNS. That's clearly not the right assumption.
So far, so simple... but the problem still exists in a slightly weird way.
3 of them were set to DHCP Forwarder... they have the correct nameserver in /tmp/resolv.dnsmasq and the local IP address in /etc/resolv.conf Once it's been put into DHCP Forwarder mode, I can find no combination of GUI steps that will disable DNSMasq for DNS short of editing the files directly.
