DNS still not propogated 2 weeks later

I am caught between my hosting company and my registrar. Each is blaming the other for my site not propogating after 2 weeks. The strange thing is that it has propogated for some places but not others. I've checked web monitoring services such as Alertra and Pingalink and it is clear that there are DNS problems in certain places in the world. The registrar says they have pointed the domain name to the correct nameservers (and every indication i have is that this is true). The hosting company says that "DNS Propogation issue is closely involve with the DOMAIN REGISTRAR. It is DOMAIN REGISTRAR & INDIVIDUAL ISP'S Responsibility to propogate DNS across the globe. Our server is running your domain successfully. There are no issues on the server that prevent your site from viewing to some specific user-base."

I have looked at dnsstuff site to see if I could tell what was going on, but I am a DNS clutz. Can anyone look at the ns info for me and tell me at least who I should be blaming, if not exactly what might be wrong?

The site is asp-hosting-plans.com . The nameservers of my hosting company are Name Server 1: ns1.accuwebhosting.net - 65.61.161.52 and Name Server 2: ns2.accuwebhosting.net - 207.44.240.96.

Any help would be extremely appreciated.

There is nothing wrong that I can see. I find it odd that you have the minimum TTL set in your SOA for a whole day, and that each individual record is set at a 4 hour cache time, but that doesn't explain 2 weeks.

My ISP's dns server, my caching local dns server, and my script were all entirely capable of resolving your domain.

Why is it that you think you have a problem specifically?

Because so many people say they cannot resolve the domain - including places like alertra, pingalink, and webmouse. yet there are other places that do resolve it fine. i can't understand this at all.

I have plugged your domain into alertra and pingalink, and they both appear to work fine. I was not able to determine what webmouse is, so I was not able to test that for myself.

But then, I plugged it in without the www prefix. Maybe they don't like your CNAME? I dunno, I'm too lazy to test that domain too. Everything seems to work fine. But do yourself a favor and ditch the CNAME. CNAME's just make for extra dns queries that don't need to happen.

sorry, i meant watchmouse. anyway, i just got an email from my hosting company that said: This is not a permenant issue. Please note that once YIEPS solves their
problem of routing, your domain will be viewable from all the parts of
the world.

Any idea what YIEPS is? I can find no information on it.

For all I know "YIEPS" means "that bastard".

...once "that bastard" solves...

;-)

LOL - that's about what I figured! Here's the newest message. Maybe this will actually get solved soon.

YIEPS one of the internet backbones is having issues which might be
the case, if your ISP is using YIEPS in order to route to us thats
where you are cutting off. We have talked to them and they are
resolving this issue and everything should be up ASAP!