Is this a DNS issue or something else?

[Kain]

I use my ISP's DNS because my Internet is the fastest with it. However, I've noticed some websites don't load correctly in Chrome with this DNS. With my ISP's DNS and Edge, the websites load correctly. Is this a Chrome issue or a DNS issue? If I change my DNS to Google's Public DNS, Chrome starts loading everything correctly but my Internet is a bit slower.

Here is an example of how GameSpot loads with Chrome when on my ISP's DNS:

[DigitalDemon]

DNS for sure. The main gamespot website is hosted in Florida, but it's css file is hosted on static.gamespot.com which in the Netherlands via Akamai. Your ISP's DNS either can't resolve or has marked this ip as spam or something.

IMO I would switch to cloudflare DNS of 1.1.1.1 and 1.0.0.1 anyway, as it's the future of DNS.

[0091/2]

Originally Posted by DigitalDemon

DNS for sure. The main gamespot website is hosted in Florida, but it's css file is hosted on static.gamespot.com which in the Netherlands via Akamai. Your ISP's DNS either can't resolve or has marked this ip as spam or something.

IMO I would switch to cloudflare DNS of 1.1.1.1 and 1.0.0.1 anyway, as it's the future of DNS.

Would you recommend it over OpenDNS? What Pros does cloudflare have verse OpenDNS?

[DigitalDemon]

Originally Posted by 0091/2

Would you recommend it over OpenDNS? What Pros does cloudflare have verse OpenDNS?

At the moment, I would recommend Cloudflare DNS over every other DNS provider available.

1. Speed - Cloudflare has a vastly superior distributed recursive server network. On average, it is the fastest resolver in 75% of the world.
2. Security/Privacy - Cloudflare supports DNS over TLS and HTTPS, making your entire connection encrypted, not just the query text. Cloudflare also holds a special agreement with browsers like Firefox, which require Cloudflare to collect the bare minimum of data. Cloudflare also only keeps logs for 24hrs in memory, nothing to disk, and is audited by a 3rd party. OpenDNS is owned by Cisco, and keeps all data. With the amount of behind-the-scenes data scraper and aggregator companies, it's no longer wise to think that meaningless data is meaningless.
3. Ease of use - While Google DNS is quite easy to remember, there is nothing easier than 1.1.1.1 and 1.0.0.1. I have no idea what opendns' addresses are.

Now opendns is not bad, the customizable filters are nice. Though injecting your own ads on unresolvables feels too middle man to me. Plus, simple tools like adblock origin can block at the browser level, or you can build your own piehole for local caching as well as whole network block listing, if not already supported by your router.

[NWR_Midnight]

I have no knowledge of how DNS works other than it translates the web site’s name into an actual numeric Internet address, but I don't understand how it can be a DNS issue if it works fine with Edge, but not Chrome. If it was a DNS issue, wouldn't it effect BOTH browsers and not just Chrome, since it would be sending the exact same web address translation to both browsers?

[0091/2]

Originally Posted by DigitalDemon

At the moment, I would recommend Cloudflare DNS over every other DNS provider available.

1. Speed - Cloudflare has a vastly superior distributed recursive server network. On average, it is the fastest resolver in 75% of the world.
2. Security/Privacy - Cloudflare supports DNS over TLS and HTTPS, making your entire connection encrypted, not just the query text. Cloudflare also holds a special agreement with browsers like Firefox, which require Cloudflare to collect the bare minimum of data. Cloudflare also only keeps logs for 24hrs in memory, nothing to disk, and is audited by a 3rd party. OpenDNS is owned by Cisco, and keeps all data. With the amount of behind-the-scenes data scraper and aggregator companies, it's no longer wise to think that meaningless data is meaningless.
3. Ease of use - While Google DNS is quite easy to remember, there is nothing easier than 1.1.1.1 and 1.0.0.1. I have no idea what opendns' addresses are.

Now opendns is not bad, the customizable filters are nice. Though injecting your own ads on unresolvables feels too middle man to me. Plus, simple tools like adblock origin can block at the browser level, or you can build your own piehole for local caching as well as whole network block listing, if not already supported by your router.

I'm currently using it with DNScrypt on my router. Is this the best way to use it on a router? I'm guessing if setup in WAN or LAN DNS the lookup will be unencrypted. Would it be redundant to setup to use over TLS or Https?
How do you set it up to use DNS over TLS and HTTPS? Is this something I need to set up for every client?

[DigitalDemon]

Originally Posted by NWR_Midnight

I have no knowledge of how DNS works other than it translates the web site’s name into an actual numeric Internet address, but I don't understand how it can be a DNS issue if it works fine with Edge, but not Chrome. If it was a DNS issue, wouldn't it effect BOTH browsers and not just Chrome, since it would be sending the exact same web address translation to both browsers?

Whoops, didn't notice he used his ISP dns on chrome, just edge. In this case, there is most likely a problem with his dns cache in chrome.

Originally Posted by 0091/2

I'm currently using it with DNScrypt on my router. Is this the best way to use it on a router? I'm guessing if setup in WAN or LAN DNS the lookup will be unencrypted. Would it be redundant to setup to use over TLS or Https?
How do you set it up to use DNS over TLS and HTTPS? Is this something I need to set up for every client?

DNS encryption via the router will be the best way to go as requests from all devices on the network that use the router for DNS will be protected. I say will be, since DNS over TLS or HTTPS isn't currently supported in just about any router. DNScrypt and DNSSEC are quite capable, but TLS and HTTPS is the endgame, as it will hide that you are even making a DNS query.

Setting up DNS over TLS or HTTPS through the browser is a relatively new thing, but I think Firefox 62 now supports it via manual configuration. This will also not be redundant, as this will bypass your router being the DNS, but for the time being until your router supports it, this will have to be configured on every capable client.