As promised, I said if I discovered why I turned off Cloudflare's DNS I would return to tell why. So I am.
Cloudflare's DNS blocks me from being able to see all the computers on my local lan, and it keeps me from being able to log into my Verizon router (which I don't do often, but that's what led me to rediscovering the issue.)
So I can either visit Octane forums fast with Cloudflare, or I can see all the computers on my local network and log into my router with no trouble but wait forever to read about the latest Octane update.
I wish either this site's webmaster or Verizon would fix this. But I'll reiterate...this is the only website that requires me to change my DNS server so I can browse it. So I'm inclined to believe the problem lies here.
Issues accessing fourm
Hi BCres,
As for the slow loading times, after some research on Verizon specific DNS issues I discovered that they have implemented a feature called "DNS Assistance" / "Verizon Search assist" which tries to determine if a server is online before returning DNS results (likely having a significant impact on resolution times). Verizon's guide for opting-out of this "feature" involves changing the DNS servers on your router in a similar way to what I recommended above (except using "123.123.123.14" instead of "1.1.1.1"): https://www.verizon.com/support/residen ... dns-assist
You can probably avoid this issue by setting your router to use "1.1.1.1", instead of your computer. How to do this varies based on the router (some may not even have the option to set this), but if you are using a router provided by Verizon you should be able to find your router's manual here: https://www.verizon.com/support/residen ... nt/routersBCres wrote:Cloudflare's DNS blocks me from being able to see all the computers on my local lan, and it keeps me from being able to log into my Verizon router (which I don't do often, but that's what led me to rediscovering the issue.)
As for the slow loading times, after some research on Verizon specific DNS issues I discovered that they have implemented a feature called "DNS Assistance" / "Verizon Search assist" which tries to determine if a server is online before returning DNS results (likely having a significant impact on resolution times). Verizon's guide for opting-out of this "feature" involves changing the DNS servers on your router in a similar way to what I recommended above (except using "123.123.123.14" instead of "1.1.1.1"): https://www.verizon.com/support/residen ... dns-assist
Thank you, hellguy, that's very helpful. I know my way around the router so that won't be a problem to test. We're having to deal with Hurricane Florence over the next few days, so it may not be until later next week (if we still have power.)
I guess Verizon's attempt to fix one thing, broke another.
I guess Verizon's attempt to fix one thing, broke another.