Dl-protect hs: DNS blocked or temporary outage?
Solved
graffx
Posted messages
120
Registration date
Status
Contributeur
Last intervention
-
Markss -
Markss -
Hello,
Actually, it's all in the title.
Since last night, www.dl-protect.com is unavailable with a French IP.
First, are you experiencing the same problem as me on all my browsers?
Next, do you have any information? It’s so fresh that I can't find any info anywhere.
So if you find an answer....
The obvious question is: Temporary outage due to the site’s DNS, or site blocked by the French government? As a result, thousands of sites using only this system are also down for their visitors.
Thanks in advance ;)
Configuration: Windows 7 / Firefox 25.0
--
Happy birthday to meeeee....and crap.
Actually, it's all in the title.
Since last night, www.dl-protect.com is unavailable with a French IP.
First, are you experiencing the same problem as me on all my browsers?
Next, do you have any information? It’s so fresh that I can't find any info anywhere.
So if you find an answer....
The obvious question is: Temporary outage due to the site’s DNS, or site blocked by the French government? As a result, thousands of sites using only this system are also down for their visitors.
Thanks in advance ;)
Configuration: Windows 7 / Firefox 25.0
--
Happy birthday to meeeee....and crap.
30 réponses
- 1
- 2
Suivant
The DNS (Domain Name System) is simply a service that converts a URL into an IP address. So when you search for www.google.fr, you are actually going to 173.194.x.x.
If the issue were related to the DNS, you would just need to enter the IP address of DL-PROTECT to access it. However, that is not the case.
So the DNS is not the cause.
No need to do a Flush DNS, etc.
If some people still have access while others do not, it is not directly related to the operator but rather to chance. The information about the site's blocking is launched from point A and travels to point Z, propagating across all branches of the tree. Therefore, some will be affected long after others.
ISPs launch the blocking information successively, but not at the same time, which also explains why one ISP could still have access while others could not.
All this is assuming it is indeed a blockage; but what is strange is that even performing the request from a proxy in Phoenix does not yield results. So either it's blocked, or it’s DL-PROTECT that’s failing.
In either case, random manipulations are not necessarily helpful. So please stop suggesting pointless tweaks without even testing them, thanks.
I will look for a solution and will repost if I find something.
If the issue were related to the DNS, you would just need to enter the IP address of DL-PROTECT to access it. However, that is not the case.
So the DNS is not the cause.
No need to do a Flush DNS, etc.
If some people still have access while others do not, it is not directly related to the operator but rather to chance. The information about the site's blocking is launched from point A and travels to point Z, propagating across all branches of the tree. Therefore, some will be affected long after others.
ISPs launch the blocking information successively, but not at the same time, which also explains why one ISP could still have access while others could not.
All this is assuming it is indeed a blockage; but what is strange is that even performing the request from a proxy in Phoenix does not yield results. So either it's blocked, or it’s DL-PROTECT that’s failing.
In either case, random manipulations are not necessarily helpful. So please stop suggesting pointless tweaks without even testing them, thanks.
I will look for a solution and will repost if I find something.
- 1
- 2
Suivant
copy the unreachable URL from ZT onto the Chrome page that opens with surf.exe
It works. @+