Experimenting with Alternate DNSs
Currently using CloudFlare: 1.1.1.1 1.0.0.1 2606:4700:4700::1111 2606:4700:4700::1001 Have set the router DNS as well as on devices (initially). Eventually I think the automatic should pick u...
Forum Discussion
Seems to be fast, but am having a problem with Bing this morning... but that could just be Bing being Bing.
Edit: ...which it was. Seems ok now at 0735.
Well, I caved. I decided to try it. I set IPv4 and IPv6 back to automatic in my desktop, and set my HughesNet modem's IPv4 DNS to Cloudflares. I flushed and renewed the DNS cache in my desktop (rather than restarting it) and, amazingly, it does seem to be faster. And this is on a Sunday evening, when everybody and their brother are trying to stream a movie and my overall speeds are down a good amount because of it.
I ran nslookup to be sure my modem was using Cloudflare, and though the default server didn't quite match what it showed in an article, it was close. The article said it should show "1dot1dot1dot1.cloudflare-dns.com", yet mine showed "one.one.one.one". The article was from April 5th, so maybe it's been updated since then.
I'm a little confused about the whole IPv4 and IPv6 thing, but the article said that if my "router" only had settings for IPv4, which is the case with the HughesNet modem, it would be fine. It said the following... "It's worth noting that you don't need to apply the IP version 6 addresses on your router if your network is already using IP version 4." I guess this is the case if I use the IPv4 version, which is the only one I can use in the HughesNet modem, right?
We'll see how it goes.
Does yours show the same?
I don't have the same level of knowledge and experience about this stuff to try this - the last time I tried a change my network didn't care for it at all. Herp derp.
nslookup works different in *nix, plus my DNS is set manually.
But yes, 1.1.1.1 is resolving to one.one.one.one.
MarkJFine wrote:nslookup works different in *nix, plus my DNS is set manually.
But yes, 1.1.1.1 is resolving to one.one.one.one.
I keep forgetting that you aren't using Windows. :S
GabeU wrote:I keep forgetting that you aren't using Windows. :S
Well, I kind of am, in a virtual machine, which brings me to why I've stopped using it - at least on my MacBook Plus:
1. Had an issue with Bing a few days ago, which came back with a vengeance.2. Then noticed a problem connecting to Win10's update as well as the MS Store when within the Win10 VM.
Tells me that something was jamming the DNS to MS IPs either from within or outside of the shared internet connection to the VM. Either that or the sketchy data-eating game my wife constantly plays on her phone (this is always a possibility).
The web site I administer uses Cloudflare as it's content delivery network. As a security measure, Cloudflare requires you to input an authorization token that it emails to the address on record if it doesn't recognize the IP at login. That's a major pain when that token is sent to the web site's 1&1 'info' address that I have to remotely log into to get. Even worse is that 1&1 site is awfully slow. Flushing the works requires rebooting the modem, which gives you a new IP virtually every time, therefore requiring me to have to constantly get new authorization tokens.
Don't mind if the IP resets due to weather-related things or gateway maintenance (like seemed to be occurring early yesterday morning on SDO68), but it's deffo overkill for repeated DNS issues. So, test over - failed. lol
