Problem with cname


#1

I created a cname to point to unbouncepages.com and i am getting a 404 error page not found. I am able to create cnames that successfully point to other websites. any ideas?


#2

Hi there! What domain name did you point to unbouncepages.com? Also, did you publish a page?


#3

Ah! I was looking for the same problem and did not publish haha. Definitely a newbie error. I’m gonna try that now :slight_smile:


#4

Hi, I think I have hit a wall with this one, I have published and tried a few tests but no joy so far:

I host with Justhost, who have to make the CNAME for you. (They dont let you do any ‘advanced’ stuff)

I asked them to set it up from the instructions from my landing page:

http://convert.logosredrawn.co.uk/con…

At the minute it’s showing a 404 error page & convert.logosredrawn.co.uk just redirects to the Unbounce home page.

They have sent this email to confirm the redirect is working:

The new links already resolve as requested:
http://www.convert.logosredrawn.co.uk/
http://convert.logosredrawn.co.uk/

$ ping convert.logosredrawn.co.uk
PING unbouncepages.com (204.236.129.38) 56(84) bytes of data.
64 bytes from ec2-204-236-129-38.us-west-1.compute.amazonaws.com (204.236.129.38): icmp_seq=1 ttl=43 time=206 ms
64 bytes from ec2-204-236-129-38.us-west-1.compute.amazonaws.com (204.236.129.38): icmp_seq=2 ttl=43 time=206 ms

$ ping www.convert.logosredrawn.co.uk
PING unbouncepages.com (204.236.129.38) 56(84) bytes of data.
64 bytes from ec2-204-236-129-38.us-west-1.compute.amazonaws.com (204.236.129.38): icmp_seq=1 ttl=43 time=206 ms
64 bytes from ec2-204-236-129-38.us-west-1.compute.amazonaws.com (204.236.129.38): icmp_seq=2 ttl=43 time=206 ms

$ ping unbouncepages.com
PING unbouncepages.com (204.236.129.38) 56(84) bytes of data.
64 bytes from ec2-204-236-129-38.us-west-1.compute.amazonaws.com (204.236.129.38): icmp_seq=1 ttl=43 time=206 ms
64 bytes from ec2-204-236-129-38.us-west-1.compute.amazonaws.com (204.236.129.38): icmp_seq=2 ttl=43 time=206 ms

Any ideas?


#5

Update: Fixed it… the www. was missing from the custom domain and now it seems to work just fine so far


#6

Glad that’s working for you!