https://www.costco.com loads, but not costco.com

[dugaduga]

For the last two weeks many website requests have been broken network wide, particularly when calling a website without adding https://www at the beginning; just did a factory default and using the latest alpha; anyone know what could cause this?

Thank you.

 

[Ronald Schwerer]

Sounds like a DNS issue. What DNS service are you using?

 

[ApexRon]

Using your ISP DNS server is usually not a good choice. Use Google (8.8.8.8 and 8.8.4.4) or OpenDNS (208.67.222.222 and 208.67.220.220) instead.

 

[john9527]

Today's browsers are finicky about automatically redirecting to https. Try clearing your browser cache/cookies.

 

[ColinTaylor]

Using your ISP DNS server is usually not a good choice.

I disagree with this. IMHO using your ISP's DNS is usually the preferred choice (at least in First World countries). However, there may be circumstances when that is not true. Switching to a different DNS provider can be useful for testing/verification purposes.

 

[Elmer]

I disagree with this. IMHO using your ISP's DNS is usually the preferred choice (at least in First World countries). However, there may be circumstances when that is not true. Switching to a different DNS provider can be useful for testing/verification purposes.

Some ISPs (maybe all) use their DNS system to harvest data about you, as does google, of course. I've been using quad 9 with dnscrypt as an alternative, and I do get fewer targeted ads. To each their own, but I prefer a few millisecs of delay as an alternative to feeding the marketing beast. Maybe quad 9 sells data too, but it's not their stated mission.

 

[dugaduga]

Thank you for all the responses; Yes I am already using Dnscrypt. Its happening network wide, no matter the browser; dnsmasq shows dnscrypt is responding with the appropriate ip, but i will try switching my dns server and see what happens

 

[dugaduga]

Changing dns servers does not make a difference; im wondering if this is not a dnsmasq issue now; the problem is relatively recent

 

[ColinTaylor]

Do you have any examples other than costco.com?

costco.com and www.costco.com are not the same thing. They return different IP addresses. Also, costco.com redirects to 104.103.112.117 but costco's web server doesn't respond to those requests. So it looks like a bad setup on costco's side.

 

[jsbeddow]

Do you have any examples other than costco.com?

costco.com and www.costco.com are not the same thing. They return different IP addresses. Also, costco.com redirects to 104.103.112.117 but costco's web server doesn't respond to those requests. So it looks like a bad setup on costco's side.

I have also been seeing this behavior for the last 6 months or so (on maybe 5% to 10% of the sites I visit), ever since first setting up Diversion, Skynet and Stubby (yes, I was a fairly early adopter of Stubby). I am not home atm for further examples, but another one at the top of my head has been amazon.fr (French Amazon) that won't load without explicitly adding the www to the beginning.

I will follow this for further ideas and developments...

 

[dugaduga]

Good call @ColinTaylor, I wish I had more to give off hand; there have been a few issues with mobile devices connecting to live TV streaming servers that I've not been able to iron out with diversion/skynet whitelists. Because its mobile I cant tell if its a www issue or not. It's only been happening for a couple of weeks.

Another problem I've had for a long long time is many https sites just wont load, they time out; nothing is reportedly blacklisted and they work in startpage proxy just fine. This is a network wide issue.

Just for the sake of discussion I will mention an even more obscure issue isolated to my PC, I'm unable to access linuxmint.com, offensive-security.com and a number of other websites; I can access them anywhere but one pc; nothing in hosts file or firewall anywhere I can determine is blocking it. This behaviour also survived multiple dist upgrades, including from windows 7 to 10 & a new router.

 

[dugaduga]

@jsbeddow im not having any issue connecting to amazon.fr myself.

 

[jsbeddow]

@jsbeddow im not having any issue connecting to amazon.fr myself.

Thanks. It would appear that this has mysteriously resolved itself on my network as well: tonight amazon.fr seems to load from all devices I tried. I will keep checking to see if other sites are still causing issues, but for the moment I can't find any. Browser/DNS cache problem maybe (but odd that it was happening from multiple devices in the household). Or, perhaps some oddities in the way that Cloudflare was handling some site records for a period of time? IDK....

 

[thelonelycoder]

Using your ISP DNS server is usually not a good choice. Use Google (8.8.8.8 and 8.8.4.4) or OpenDNS (208.67.222.222 and 208.67.220.220) instead.

Usually, your ISP responds quicker and serves the closesd geo-located server available to you.
Living in a well regualted country I don't have to worry about ISP's misusing my data, which for some is a good reason to use a third party DNS.
Someone will still have your data and use it to their advantage, Googles DNS is probably the worst to entrust it with.
Just my opinion on that matter.

 

[Zonkd]

I disagree with this. IMHO using your ISP's DNS is usually the preferred choice (at least in First World countries). However, there may be circumstances when that is not true. Switching to a different DNS provider can be useful for testing/verification purposes.

One example being I have to use my ISP DNS to receive un-metered “data-free” streaming for Spotify and Netflix. So that’s a nuisance.

 

[Zonkd]

Usually, your ISP responds quicker and serves the closesd geo-located server available to you.
Living in a well regualted country I don't have to worry about ISP's misusing my data, which for some is a good reason to use a third party DNS.
Someone will still have your data and use it to their advantage, Googles DNS is probably the worst to entrust it with.
Just my opinion on that matter.

Lucky man. Our ISPs must log dns and browsing history for many years. Now they use it to generate insights and sell to advertisers. Not easy to opt out. Cloudflare has been great and performance is perfect.

 

[sbsnb]

Living in a well regualted country I don't have to worry about ISP's misusing my data.

Why do you trust that the regulations are properly enforced against all DNS providers? I'm genuinely curious.

 

[consorts]

just confirming this happens to me a lot.
i'm googling the website, then clicking on the google provided link
rather than entering in the url name on the browser address line.
costco it just the most common example of why i have to do this.

 

[heysoundude]

Today's browsers are finicky about automatically redirecting to https. Try clearing your browser cache/cookies.

have you tried using brave as your browser?

 

[heysoundude]

Do you have any examples other than costco.com?

costco.com and www.costco.com are not the same thing. They return different IP addresses. Also, costco.com redirects to 104.103.112.117 but costco's web server doesn't respond to those requests. So it looks like a bad setup on costco's side.

I'm guessing you've not had opportunity to use their app to verify that.