Hello, my domain was recently a victim of transfer hijacking and it's been almost 19 hours since I retrieved it back and changed my DNS settings but it still doesn't seem to respond in certain areas?

I could access it fine for the first few hours, then I couldn't anymore. No-one in Canada can, apparently. One guy from the UK can't either, but everyone from the US is able to get through fine?

When I try to access it, it shows a blank page. When I access a page within the site, it basically goes to a "parked site" kind of a website. (http://www.bollyfm.net/bollyfm/index.html)

Can you guys here confirm if any of you can access it and where you're geographically located?

The domain is: bollyfm.net

Shouldn't 19 hours have been enough for the DNS to start responding properly? The domain has been locked on my insistence so I really don't think it's been hijacked; so that what seems to be the problem?

Any help?

Come on people, anyone?

I believe it can take up to / around 24 hours to propagate everywhere. Check out:

http://www.alertra.com/spotcheck.php

it'll check the dns from many places around the world, if you click on the time you can see what IP it resolved to.

Thanks for the response. It seems to be working everywhere but I just contacted my Registrar and He's puzzled as to why it's not working in some areas.

People in Canada can't access it. I have other domains working fine except this one. I registered a domain 24 hours ago that propagated within 1 hour. This one is not! It's frustrating.

My Registrar is suggesting I look into my dns settings but all my other sites seem to be working fine. Maybe I just need to wait?

Isn't this abnormal though?

When you say they can't access it does it mean it just comes up to a white page etc or does it actually fail and say server not found?

It comes to a white page. On inner pages, it goes to either Page not found or redirects to parked sites.

flushdns and try again, i've had that happen before - some domains are annoying that way

flushdns

wont help if the ISP has cached the results or the nameservers.

simple answer - wait - could be anything upto a week ...

Still nothing. My server support is looking into the DNS settings but frankly there is nothing wrong with them. In fact, I believe the other domains on the server have more DNS irregularities than this one and they all appear fine.

Upon pinging the website, though, it shows an ip different from the other sites hosted on the same server. Could that be a problem?

It started working in Canada almost 24 hours ago but has stopped working from the last 2 hours again. Same here. It was working here last night but has stopped working right now.

So frustrating! Isn't there anyone I can hire to look into this? Can anyone suggest anything else I should try?

any competent server/sys admin should be able to find the issue and at least inform you what state its in
- a simple dig +trace FFS would provide you with most of the details.

I can highly suggest going to amazon/b&n/wherever and buying a copy of dns&bind - it *WILL* help you understand ...

I have no expertise in areas of DNS functionailities so I'm totally clueless and I doubt that would help, but I just heard back from Softlayer and they're saying everything is perfectly okay.

When I ping to bollyfm.net, I get 66.98.145.18 where as my other domains ping to 208.43.1.248

Can anyone here ping from your systems and see where it leads you? There have been times when the website shows the exact page as the one you get when you access 66.98.145.18 through http.

This is so frustrating. I have checked the dns settings myself and everything points to my server ip but upon pinding it leads to 66.98.145.18.

I did a traceroute and this is what I got:

I did a traceroute on bollyfm.net and this is what I got:

Hop T1 T2 T3 Best Graph IP Hostname Dist TTL Ctry Time
1 1 0 * 0.4 ms

174.133.202.225 AS21844
THEPLANET-AS e1.ca.85ae.static.theplanet.com. 255 US Unix: 14:45:16.590
2 0 0 * 0.4 ms [+0ms]

74.55.252.121 AS21844
THEPLANET-AS et4-13.ibr02.hstntx2.theplanet.com. 0 miles [+0] 63 US [Router did not respond]
3 0 0 * 0.4 ms [+0ms]

70.87.253.166 AS21844
THEPLANET-AS et3-1.ibr01.hstntx2.theplanet.com. 0 miles [+0] 63 US [Router did not respond]
4 6 6 * 5.8 ms [+5ms]

70.87.253.49 AS21844
THEPLANET-AS et5-4.ibr03.dllstx3.theplanet.com. 0 miles [+0] 62 US [Router did not respond]
5 6 6 * 5.8 ms [+0ms]

70.87.253.22 AS21844
THEPLANET-AS te9-1.dsr02.dllstx3.theplanet.com. 0 miles [+0] 252 US Unix: 14:45:16.729
6 5 6 * 5.8 ms [+0ms]

70.87.253.25 AS21844
THEPLANET-AS et3-2.ibr04.dllstx3.theplanet.com. 0 miles [+0] 61 US [Router did not respond]
7 6 6 * 6.2 ms [+0ms]

206.223.118.24 AS2914
NTT-COMMUNICATIONS-2914 te1-2.cer01.dal01.dallas-datacenter.com. 0 miles [+0] 251 US Unix: 14:46:07.770
8 6 6 * 6.4 ms [+0ms]

66.228.118.201 AS36351
SOFTLAYER po1.dar01.dal01.dallas-datacenter.com. -1 miles [+0] 0 miles [+0] 250 US [Router did not respond]
9 7 6 * 6.4 ms [+0ms]

66.228.118.214 AS36351
SOFTLAYER po1.fcr04.dal01.dallas-datacenter.com. -1 miles [+0] 0 miles [+0] 249 US [Router did not respond]
10 6 6 * 6.4 ms [+0ms]

208.43.1.248 AS36351
SOFTLAYER
[Reached Destination]braykhna.com. -1 miles [+0] 57 US Unix: 14:45:16.885

Anyone knows what I'm supposed to be doing here? Do you think it's a problem with the server or the domain?