Why do you have to type in WWW. to See my Domain Name?

[DnPresident]

After changing the C-Name on my domain name, When searching for it in the browser I now have to type in WWW. in front of the name for the search to work. I've done this on another name and had no problems.

The name I'm having the problem with is ~StructuredSettlement~Dot Name and it is very much uncompleted.

Does anyone have any idea what could be the problem?

 

[IAmAllanShore]

Without the www. it is automatically redirecting to a https:// connection - hence, your issue... no?

 

[DnPresident]

Without the www. it is automatically redirecting to a https:// connection - hence, your issue... no?

The url I get is a windows/msn search page: http://search.live.com/results.aspx?FORM=DNSAS&q=structuredsettlement.name

 

[snoop]

You have likely only setup cname for the www. subdomain, set it up for @ and * aswell to point everything.

 

[IAmAllanShore]

The url I get is a windows/msn search page: http://search.live.com/results.aspx?FORM=DNSAS&q=structuredsettlement.name

That's a DNS caching issue, not a cname issue, judging by my seeing a site load, at least.

 

[DnPresident]

Thanks Snoop and IAmAllanShore.........The problem is driving me crazy at the moment..

Godaddy doesn't see anything wrong on their end and I probably won't hear back from the blog host it points to until tomorrow.

I am very inexperienced at these issues at the moment. I have only parked my names over the past 3 years but due to recent events/changes it looks like I have to steer more toward some kind of development that will hopefully lead to links and better placement.

 

[htmlindex]

Not sure about the reason, but the site doesn't resolve for me either. It takes forever to load, then it redirects to Google.

 

[Charley]

That's a DNS caching issue, not a cname issue, judging by my seeing a site load, at least.

Can that be reset ?

 

[DnPresident]

That's a DNS caching issue, not a cname issue, judging by my seeing a site load, at least.

I thought you might be interested in an update: Problem solved

When I changed the C-Name at Godaddy I had to forward the name to it's self for it to work. Strange to me but it worked for the other names, One is in my sig ~TastyWires~

After comparing the ~StructuredSettlement~Dot Name the only difference I could find was that on the forwarding address I had put HTTPS instead of HTTP. I took off the (S) :bingo: and now it works fine. If the site was secured I guess the (S) would have worked fine.