Hi,
I posted about this awhile ago, but it seems my Vodafone router goes screwy occasionally. It's been working fine for ages, and I've come to go online tonight and found that alot of external services don't seem to work. When checking into the syslog on the router, I've found these events:
12.03.2023 20:41:12 data Info using only locally-known addresses for domain broadband
12.03.2023 20:41:12 data Info using only locally-known addresses for domain bind
12.03.2023 20:41:12 data Info using only locally-known addresses for domain invalid
12.03.2023 20:41:12 data Info using only locally-known addresses for domain local
12.03.2023 20:41:12 data Info using only locally-known addresses for domain localhost
12.03.2023 20:41:12 data Info using only locally-known addresses for domain onion
12.03.2023 20:41:12 data Info using only locally-known addresses for domain test
12.03.2023 20:41:12 data Info reading /tmp/resolv.conf.auto
12.03.2023 20:41:12 data Info using only locally-known addresses for domain broadband
12.03.2023 20:41:12 data Info using only locally-known addresses for domain bind
12.03.2023 20:41:12 data Info using only locally-known addresses for domain invalid
12.03.2023 20:41:12 data Info using only locally-known addresses for domain local
12.03.2023 20:41:12 data Info using only locally-known addresses for domain localhost
12.03.2023 20:41:12 data Info using only locally-known addresses for domain onion
12.03.2023 20:41:12 data Info using only locally-known addresses for domain test
I know that resolv.conf is related to DNS look up, which would explain why I can't access game launchers which are checking for updates and also services like Office 365. Even Windows Update isn't working on my Windows 10 laptop because it "can't talk to the Windows Update" service.
I've seen some historical posts where DPI on the Vodafone side goes abit whacky, but this looks like my router essentially falls over when loading the resolv.conf file and thus can't get to active DNS so resorts to a temp (rather limited) version.
I'll also add that the messages from the syslog above do not appear when the router is working fine. I've had to "fix" this before by running a factory reset of the router. Typically it has to be done monthly.
