Streaming live at 10am (PST)

1&1 CNAME alias causes 2 problems


#1

Hello,

My domain name (vauban . co) is registered on 1&1. I did set up a cname alias which works fine, but causes 2 problems :

-The @mydomain emails I did set on 1&1 do not work. Their customer service explained me its because the cname redirection also redirects the emails

-I plugged my domain to Google webmaster tool. Google thinks there is a robot.txt file that blocks him. I tried to put a "neutral" robot.txt instead of nothing ("User-agent: * Disallow:") but it does not change anything

Can you help me ?

Thanks


#2

Hi @Nabuav, could you please email me your read-only link to support[at]webflow.com? More info on read-only links here: http://help.webflow.com/sharing-your-public-webflow-site-link. I can then take a look at your settings and try to resolve the issue from there. smile Thanks!


#3

Hi Nabuav

I looked into your domain, and it looks like you have a CNAME record for vauban.co -> proxy.webflow.com.

It is not recommended to use a CNAME on the root domain (vauban.co as opposed to a subdomain such as www.vauban.co). Because of how DNS works, when you put a CNAME record on a root domain, it overrides any other records you have set on the root domain - such as the MX record which is responsible for email delivery.

There are a number of ways you could solve this, but here is my recommendation:

From this tutorial here: http://help.webflow.com/hosting

Add the DNS A records as described in step 3. You are able to add A records to the root domain (vauban.co) without any of the issues CNAME would cause.

Then modify the CNAME record you already have set. Change it from vauban.co to www.vauban.co.

Then, both vauban.co and www.vauban.co will work and you will be able to recieve your email!


#4

Thanks guys.

I did what @Nathan suggested. I had to input only one ip adress for the root domain, as explained here (http://forum.webflow.com/t/new-domain-help-my-sanity/3393). Is it ok ? (emails & navigation both work fine now)

@thewongiv the google robots problem is still there, I'm sending you the read-only link

Thanks !


#5