19 Oct 10, 03:37PM
The problem with Akimbo is that they [or their host] have incorrectly setup their DNS. (As stated by RandumKiwi)
However to go into detail... All they [the owner or host] have to do is remove:
You can see that the parked page's DNS takes authority over Akimbo's actual resolvers:
Name Server:DNS.PARKPAGE.FOUNDATIONAPI.COM
Name Server:DNS2.PARKPAGE.FOUNDATIONAPI.COM
Name Server:NS2.HOSTINGAS.IN
Name Server:NS1.HOSTINGAS.IN
What happens is that when your browser requests 'akimbo.in' it will query a nameserver from the list. Usually the first nameserver on the list is the only one queried, however if it does not respond it will go down the list until it gets a working response.
If you hit the FOUNDATIONAPI resolver, you will be taken to the parked page. However if you hit HOSTINGAS you will be taken to the correct destination. Most modern browsers cache the DNS resolvers so that they can avoid doing a query on each request, this explains why some people go to the parked page and some go successfully to the site.
tl;dr: remove the bad resolvers from the NS list and you will always hit the correct records.. It is better to fix the problem than to patch it.
However to go into detail... All they [the owner or host] have to do is remove:
- dns.parkpage.foundationapi.com
- dns2.parkpage.foundationapi.com
You can see that the parked page's DNS takes authority over Akimbo's actual resolvers:
Name Server:DNS.PARKPAGE.FOUNDATIONAPI.COM
Name Server:DNS2.PARKPAGE.FOUNDATIONAPI.COM
Name Server:NS2.HOSTINGAS.IN
Name Server:NS1.HOSTINGAS.IN
What happens is that when your browser requests 'akimbo.in' it will query a nameserver from the list. Usually the first nameserver on the list is the only one queried, however if it does not respond it will go down the list until it gets a working response.
If you hit the FOUNDATIONAPI resolver, you will be taken to the parked page. However if you hit HOSTINGAS you will be taken to the correct destination. Most modern browsers cache the DNS resolvers so that they can avoid doing a query on each request, this explains why some people go to the parked page and some go successfully to the site.
tl;dr: remove the bad resolvers from the NS list and you will always hit the correct records.. It is better to fix the problem than to patch it.