If you are encountering this peculiar problem where only a few websites load and other don't, you're not alone.
This problem is faced by many users, and even though a lot of people attempt to fix using useless YouTube videos (100% working? My a******!!) and how-to guides.
First, let us see what this problem is about.
~ Some websites load perfectly fine (eg. google sites) while others don't. You can be pretty sure how pissed off I was when I sat down to complete my morning paid surveys and they failed to load, while my annoying friends had no problem pestering me with "Good morning!" messages on Whatsapp, even though both my phone and computer uses the same internet connection.
Why this happens:
~ As far as I've gathered, this type of problem occurs when you're assigned a faulty DNS. (What is DNS?). Usually, ISPs (like BSNL which I'm using) has a very bad service record; they hardly maintain their servers, so if one breaks down, they just switch subscribers to another good one, no matter its capacity. Its much like what the electricity guys do in rural areas; they connect 1000 lines to a transformer which can only support 500.
As a result, the DNS server suffers an overload. And we all know, overloading is bad. Very bad!!
Let me explain it to you in detail.
Suppose you were assigned DNS: 218.248.255.167/168 (primary/secondary) and you were really rocking it! But then these servers failed and the lazy government-salaried IT guys switched your connection to 218.248.233.9/10 with a capacity of 100 connections.
The only problem is that another 1000 users are already using 218.248.233.9/10 and so, due to being assigned to an overloaded DNS server, you're getting the error message on your browser.
Why some websites work:
~ Google is very rich so it has its own public DNS which you'll be familiar with if you're a tech savvy: 0.0.0.0/.4. Whenever you connect to a google website, eg. google.com, your primary DNS server doesn't have much work to do besides further relay your request to google's DNS servers.
Think of it like Bluedart delivering a parcel to Delhi or Mumbai. Bluedart already has a good knowledge all of all the galis and slums, the gunda-elakas and the raiz-elakas, so delivering a parcel to Delhi or Mumbai is a piece of cake for them.
In our case, Bluedart is your primary DNS server and Delhi is google's DNS. Even an overloaded DNS server can get you google.com because it easy.
But suppose you're sending something to Chundi gaon in the remotest part of UP, obviously Bluedart is going to have problems locating an address in a place its not very familiar with. Hence, instead of going beyond their call of duty (which they are supposed to do), they just return the parcel back to you and say "This address can't be reached, sorry. And no refunds; our delivery guys spent your money on petrol searching for this Chundi gaon of yours. Toodles!"
Why the usual fix don't work:
~ Some tech gurus will tell you to just switch your primary DNS to google's zeroes and four, and that did work for a long time, and maybe its still working for some ISPs.
But, again, some ISPs like our BSNL, which has a super-lazy government-salaried IT department, thought that "if we let these village idiots set their own DNS servers, God knows what they'll end up doing. Let's think of a way how we can stop that."
So BSNL now has a big moderator, which cancels any changes you make to your DNS settings, be it on your computer's IPV4 connection, or your modem's interface. Nope, it won't work.
So what to do?
~ I'll tell you how I managed to complete my surveys. I completed them during mid-day when most of those 1000 users using the same DNS as mine were taking their afternoon nap after lunch. During that time, my DNS server was getting hit with less requests and could easily handle the traffic.
So my advice, go away now and come back when no one else would even think of opening their computers and bombarding their DNSes with requests. Late at night (post 3 o' clock) or mid-afternoon (after 2 pm but before evening 4, because internet traffic is highest in the evening with everyone returning from work and opening their computers).
~ Another fix is to increases the frequency with which you send requests to he server. For eg, go to the website. If it doesn't load, don' hit F5 instantly. Wait for 10 seconds. Then reload. Chances are the website will load now. Its just like how the traffic police untangles a traffic jam. Slowly, steadily, one car at a time.
Eventually, after a week or so, you will be reverted back to your original DNS. Maybe those IT guys are not so lazy after all. If you're not a late night bloomer/ don't wanna miss your afternoon nap or you are impatient, then you will have to wait. Wait until your DNS is fixed. All good things to those who wait.
~ Kenji
The Doctor Blake Team.
This problem is faced by many users, and even though a lot of people attempt to fix using useless YouTube videos (100% working? My a******!!) and how-to guides.
First, let us see what this problem is about.
Why this happens:
~ As far as I've gathered, this type of problem occurs when you're assigned a faulty DNS. (What is DNS?). Usually, ISPs (like BSNL which I'm using) has a very bad service record; they hardly maintain their servers, so if one breaks down, they just switch subscribers to another good one, no matter its capacity. Its much like what the electricity guys do in rural areas; they connect 1000 lines to a transformer which can only support 500.
As a result, the DNS server suffers an overload. And we all know, overloading is bad. Very bad!!
Let me explain it to you in detail.
Suppose you were assigned DNS: 218.248.255.167/168 (primary/secondary) and you were really rocking it! But then these servers failed and the lazy government-salaried IT guys switched your connection to 218.248.233.9/10 with a capacity of 100 connections.
The only problem is that another 1000 users are already using 218.248.233.9/10 and so, due to being assigned to an overloaded DNS server, you're getting the error message on your browser.
Why some websites work:
~ Google is very rich so it has its own public DNS which you'll be familiar with if you're a tech savvy: 0.0.0.0/.4. Whenever you connect to a google website, eg. google.com, your primary DNS server doesn't have much work to do besides further relay your request to google's DNS servers.
Think of it like Bluedart delivering a parcel to Delhi or Mumbai. Bluedart already has a good knowledge all of all the galis and slums, the gunda-elakas and the raiz-elakas, so delivering a parcel to Delhi or Mumbai is a piece of cake for them.
In our case, Bluedart is your primary DNS server and Delhi is google's DNS. Even an overloaded DNS server can get you google.com because it easy.
But suppose you're sending something to Chundi gaon in the remotest part of UP, obviously Bluedart is going to have problems locating an address in a place its not very familiar with. Hence, instead of going beyond their call of duty (which they are supposed to do), they just return the parcel back to you and say "This address can't be reached, sorry. And no refunds; our delivery guys spent your money on petrol searching for this Chundi gaon of yours. Toodles!"
Why the usual fix don't work:
~ Some tech gurus will tell you to just switch your primary DNS to google's zeroes and four, and that did work for a long time, and maybe its still working for some ISPs.
But, again, some ISPs like our BSNL, which has a super-lazy government-salaried IT department, thought that "if we let these village idiots set their own DNS servers, God knows what they'll end up doing. Let's think of a way how we can stop that."
So BSNL now has a big moderator, which cancels any changes you make to your DNS settings, be it on your computer's IPV4 connection, or your modem's interface. Nope, it won't work.
So what to do?
~ I'll tell you how I managed to complete my surveys. I completed them during mid-day when most of those 1000 users using the same DNS as mine were taking their afternoon nap after lunch. During that time, my DNS server was getting hit with less requests and could easily handle the traffic.
So my advice, go away now and come back when no one else would even think of opening their computers and bombarding their DNSes with requests. Late at night (post 3 o' clock) or mid-afternoon (after 2 pm but before evening 4, because internet traffic is highest in the evening with everyone returning from work and opening their computers).
~ Another fix is to increases the frequency with which you send requests to he server. For eg, go to the website. If it doesn't load, don' hit F5 instantly. Wait for 10 seconds. Then reload. Chances are the website will load now. Its just like how the traffic police untangles a traffic jam. Slowly, steadily, one car at a time.
Eventually, after a week or so, you will be reverted back to your original DNS. Maybe those IT guys are not so lazy after all. If you're not a late night bloomer/ don't wanna miss your afternoon nap or you are impatient, then you will have to wait. Wait until your DNS is fixed. All good things to those who wait.
~ Kenji
The Doctor Blake Team.
No comments:
Post a Comment