Suzanne — Mon, 31 Mar 2003 15:45:56 +0000

And frankly, if you've got anything going with coastlandtech, you need to stop. Get on the horn and get that straightened around PRONTO!

Suzanne — Mon, 31 Mar 2003 15:42:08 +0000

Quote: (We are moving our website to a new server this week. Please be patient if you find some broken links.)

is that on the new or old server?

If the host is doing everything correctly, check to see if other people can see the right thing or not. If so, then contact your ISP and tell them they have to update, dammit. If not, then you'll have to contact the old host and have them delete their name records for you. Make sure the new host has the domain names correctly in place (double check).

Suzanne — Mon, 31 Mar 2003 15:38:18 +0000

you're with coastlandtech??

fifeclub — Mon, 31 Mar 2003 15:04:32 +0000

So since my last post I've had ongoing conversations with both my host and GoDaddy customer support. Basically each says that everything looks fine, confirms that the name servers are setup properly to the new host. Furthermore, my host says it's got to be something with my registrar and my registrar says to contact my host.

It looks like I'm just screwed. I seem own a domain that I can't use (unless I continue hosting it with my unreliable, overpriced old hosting compnay).

----------------------------

Here's what GoDaddy wrote:
(FYI: Acunett is my new host, CLicknet Solutions is my old host, and coastlandtech.com is mentioned but I haven't got a clue who they are or how they're involved.)

Quote:
I've done several differant dns lookups on both your accounts and they are both currently being refered to the NS1D.ACUNETT.COM and NS2D.ACUNETT.COM name servers. All queries for your domains hit those name servers and then bring up the websites. I'm not sure if I understand what the problem is that your are trying to fix.

The results for the last ns lookup brought up these details.
Server: DNS server ns4.coastlandtech.com

Non-authoritative answer:
PattySussman.com nameserver = ns1d.acunett.com
PattySussman.com nameserver = ns2d.acunett.com

Authoritative answers can be found from:
PattySussman.com nameserver = ns1d.acunett.com
PattySussman.com nameserver = ns2d.acunett.com
ns1d.acunett.com internet address = 64.191.17.37
ns2d.acunett.com internet address = 64.191.17.38

and

Server: DNS server ns4.coastlandtech.com

Non-authoritative answer:
MikeSussman.com nameserver = ns1d.acunett.com
MikeSussman.com nameserver = ns2d.acunett.com

Authoritative answers can be found from:
MikeSussman.com nameserver = ns1d.acunett.com
MikeSussman.com nameserver = ns2d.acunett.com
ns1d.acunett.com internet address = 64.191.17.37
ns2d.acunett.com internet address = 64.191.17.38

So the current host must have a record for both domains and directs to the displayed sites. If you are still not satisfied that the name servers have been updated, please reply with a more precisely stated question. Let us know if we can help you in any other way. You may also wish to read through some of the frequently asked questions on our Support Forum:

Quote:
It appears that your domain has propagated. I believe that the issue with your domain resides with your hosting provider. I would suggest contacting them for further assistance. Thank you for your email.

Any suggestions? Thanks.
-Mike

fifeclub — Fri, 28 Mar 2003 18:08:07 +0000

Actually, not yet.
There's not too much I could screw up on the registrar side. As for setting up the parked domain, It seemed rather simple, but even if I did something wrong, the old site from the old host shouldn't load because the old nameservers were removed, right? If it was wrong on my host's side wouldn't I just get a 404? Or not?

Suzanne — Fri, 28 Mar 2003 17:37:45 +0000

Have you informed the host?