So, if you don't have internet, then there is something amiss elsewhere... _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
Joined: 31 Jul 2021 Posts: 2146 Location: All over YOUR webs
Posted: Sat Sep 10, 2022 18:02 Post subject:
So after looking at your screenshot I sported a few issues.
Just for the heck of it remove the Domain name elyograg.org from optional settings. Hit save then apply, wait for a few seconds and reboot for good measure.
Gateway can also be safely set to the router IP 192.168.1.1
I have no idea what you're trying todo with setting the local DNS to 192.168.1.170 as well as the static DNS 1, unless your configuration is using pyhole or something similar this looks wrong.
If you have no extra DNS setup your Local DNS should be empty and your static DNS 1 point to 1.0.0.1 and a second fallback should be added e.g. 9.9.9.9 on static DNS 2
As far as I know, the Netgear CM-700 cable modem is not capable of anything other than bridging. I have never configured it at all, and in fact have reset it to factory defaults twice in the last few days.
The "turn everything off, wait 5 minutes, power back up without mac cloning" procedure is a magic cureall. I never would have thought of that on my own, thank you.
I got back my original public IP address. Everything also works without tcpdump running.
I think Comcast has some kind of a problem in their network, but now I don't need to be concerned about it.
It's not just Comcast that has this quirk with standard cable modems that are not combination wifi/ethernet routers. Glad to hear it resolved itself with the 5 minute power cycle trick <wink> _________________ "The woods are lovely, dark and deep,
But I have promises to keep,
And miles to go before I sleep,
And miles to go before I sleep." - Robert Frost
"I am one of the noticeable ones - notice me" - Dale Frances McKenzie Bozzio
Joined: 16 Nov 2015 Posts: 6388 Location: UK, London, just across the river..
Posted: Sun Sep 11, 2022 7:44 Post subject:
hmm... looking at your screenshot...
as the others noted:
-Basic Setup>Network Setup>local DNS must be left 0.0.0.0 unless you are using something special(pihole)..
as this interferes with DNSmasq
-Basic Setup>Optional Settings>Domain Name must be left clear
I would also suggest you to:
-disable Shortcut Forward Engine unless you have a gigantic WAN pipe 1 Gigbit + you don.t need this as this can interfere with few things...and can break few things too... (R9000 has lots of CPU power, so no need of SFE)
-Ignore WAN DNS - i would've click on this option(enable), as this will exclude your ISP DNS and will use only DNS that you specified on your router...
-Forced DNS redirection (enable) this will force devices connected to your router to use only the DNS you specified (optional)
-NTP>server ip / name - must be left blank or if you use it use IP instead of name...like 162.159.200.123 (cloudflare NTP time) _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 Gateway/DoT,Forced DNS,AP Isolation,Ad-Block,Firewall
TP-Link WR1043NDv2 -DD-WRT 55303 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear R7800 --DD-WRT 55363 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55363 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
I have my own internal DNS servers. They share a VIP using ucarp at the .170 internal IP address. These DNS servers are recursive internet resolvers as well as handling inside addresses for several of my own domains. I want all DNS requests to ultimately hit one of those servers.
After I solved the tcpdump problem with advice gotten here, I got DNS working exactly the way I want it by checking "Ignore WAN DNS" and disabling "No DNS Rebind". Clients are sent the router's IP address for DNS, and the router correctly queries the internal DNS server.