Jump to content

Godaddy CNAME Not Working


The Little Guy

Recommended Posts

I am using godaddy to do a CNAME, when I do it, nothing happens. When I load the page it says "The domain is parked FREE, courtesy of godaddy.com"

 

but the CNAME says: stats.weblyize.com

 

What am I doing wrong (its been about 24 hours)?

 

here is the zone file godaddy gave me:

 

CLEEP.US.	3600	IN	SOA	ns29.domaincontrol.com.	dns.jomax.net (
			2012022901
			28800
			7200
			604800
			3600
			)

; CNAME Records
www	3600	IN	CNAME	stats.weblyize.com
e	3600	IN	CNAME	email.secureserver.net
pda	3600	IN	CNAME	mobilemail-v01.prod.mesa1.secureserver.net
webmail	3600	IN	CNAME	webmail.secureserver.net
mobilemail	3600	IN	CNAME	mobilemail-v01.prod.mesa1.secureserver.net
email	3600	IN	CNAME	email.secureserver.net
imap	3600	IN	CNAME	imap.secureserver.net
mail	3600	IN	CNAME	pop.secureserver.net
pop	3600	IN	CNAME	pop.secureserver.net
smtp	3600	IN	CNAME	smtp.secureserver.net
ftp	3600	IN	CNAME	@
files	3600	IN	CNAME	login.secureserver.net
fax	3600	IN	CNAME	login.secureserver.net
calendar	3600	IN	CNAME	login.secureserver.net

; NS Records
@	3600	IN	NS	ns29.domaincontrol.com
@	3600	IN	NS	ns30.domaincontrol.com

Link to comment
Share on other sites

Right now, www.cleep.us "works" (does not show the GoDaddy page) for me.

 

How would stats.weblyize.com know if it should host it? From what I was told it should have to know...

A CNAME says "this website can be accessed at whatever server [iP address] hosts X". So right now your DNS says

www.cleep.us can be accessed at the same server that hosts stats.weblyize.com.

The browser then has to look up where that server is (I get 24.179.144.72).

 

Next the browser starts sending HTTP requests. It'll send a request for "www.cleep.us" to 24.179.144.72. If that server does not know how to host "www.cleep.us" then it'll probably (a) complain that it doesn't know how to host that website, or (b) show whatever it considers to be the "default" website. In this situation it does the latter, which is the most common choice.

 

So, what are you trying to do? What do you mean "it should have to know"?

Link to comment
Share on other sites

Mmm I don't know if this will help at all because I'm definitely no expert on the subject... but most of the CNAMEs I've worked with are usually the full address followed by a period:

my.domain.com.CNAME another.domain.com.

 

In your case it should look something like this, no?

cleep.us.	3600	IN	CNAME	stats.weblyize.com
www.cleep.us.	3600	IN	CNAME	stats.weblyize.com

Link to comment
Share on other sites

Mmm I don't know if this will help at all because I'm definitely no expert on the subject... but most of the CNAMEs I've worked with are usually the full address followed by a period:

my.domain.com.CNAME another.domain.com.

 

In your case it should look something like this, no?

cleep.us.	3600	IN	CNAME	stats.weblyize.com
www.cleep.us.	3600	IN	CNAME	stats.weblyize.com

 

And to answer your question on why it doesn't work - it's because there is no entry for just your normal domain

Link to comment
Share on other sites

Mmm I don't know if this will help at all because I'm definitely no expert on the subject... but most of the CNAMEs I've worked with are usually the full address followed by a period:

my.domain.com.CNAME another.domain.com.

 

The zone file has an origin (base domain name) to it, in this case it is CLEEP.US.  When you don't end an entry with a period, that entry is pre-fixed to the origin and that is used as the full domain. So:

www   3600 IN CNAME blah.com

 

will be interpreted by the dns server as www.CLEEP.US. and

bleh.blah 3600 IN A 1.2.3.4

would be bleh.blah.CLEEP.US.

 

If you end an entry in a period then it is considered a fully qualified domain and not prefixed, so you have to include everything.

 

My understanding is, however, that the domain specified as the CNAME should have a period after it, as in:

 

www	3600	IN	CNAME	stats.weblyize.com.

 

Link to comment
Share on other sites

Mmmm.. you know I didn't say this earlier but... ewwww GoDaddy. :P

I was going to. Wanted to say "well your first problem is using GoDaddy" but I held my tongue. But now that the question's answered:

 

Well Little Guy, your first problem is using GoDaddy...

Link to comment
Share on other sites

My main beefs with them:

  • They provide little to no flexibility with most of their services
  • Their prices have always seemed high to me for the level of quality it is
  • Their UI is absolutely horrendous and takes 10x longer to navigate through to do the smallest of tasks
  • They supported SOPA
  • They've tried on many attempts to call me to market more items (they also send a higher than required amount of emails, which can be tricky to opt-out of)

 

Yes, for first-timers or those that have a lot of clients already on GoDaddy and don't want to move, sure I can understand that. But personally, I moved everything away from them as soon as I realized how much I hated it.

Link to comment
Share on other sites

  • 2 weeks later...

Mmmm.. you know I didn't say this earlier but... ewwww GoDaddy. :P

I was going to. Wanted to say "well your first problem is using GoDaddy" but I held my tongue. But now that the question's answered:

 

Well Little Guy, your first problem is using GoDaddy...

I was planning to use godaddy, has just seen this topic..

Which vendor do you recommend?

Link to comment
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.