Link a subdomain hosted at Dreamhost?

Hi,

Thanks for this great service. I added integration with my GitHub Jekyll blog repo and it’s building to Netlify nicely!

Next step is I would like my blog address, which is a subdomain, to point to Netlify.

Currently I have a CNAME under gingerbeardman.com with name blog and value gingerbeardman.github.io. at my Dreamhost control panel.

The requirement to change to Netlify DNS servers has me worried/confused.

What do I need to change? Any help appreciated.

  • we need to know your netlify site name

Netlify site name: https://keen-bhaskara-f5872f.netlify.app

  • DNS issues? Tell us the custom domain, tell us the error message! We can’t help if we don’t know your domain.

Desired URL: https://blog.gingerbeardman.com

My hosting control panel is at Dreamhost.

@gingerbeardman Welcome to the Netlify community.

If I understand correctly, all you need to do is change the CNAME entry from GitHub to your Netlify subdomain. You do not need to use Netlify name servers … there is no requirement that you do this.

I thought it might be as simple as that. I did try, but it didn’t seem to work so I reverted.

I can try again I suppose?

Do I need to activate anything on netlify?

I ask because for GitHub Pages as well as the CNAME I had to activate a couple of things on my GitHub repo, so the link was both ways.

hi gingerbeardman, can you try again and then tell us what domain this is regarding, so we can check your settings?

Earlier I made the following changes:

  1. CNAME at my domain now has value keen-bhaskara-f5872f.netlify.app.
  2. Custom Domains in Netlify account now contains blog.gingerbeardman.com

Waited for subdomain DNS change to propagate.

Seems to have worked, though I need to look at why the https:// is raising an error with my browser.

Site settings > Domain management > DNS verification was successful

So I just have to wait for Let’s Encrypt SSL/TLS certificate to generate.

Cheers!

1 Like

I’ve had a report from somebody unable to access my site. It times out for them. DNS showing as 95% propogated.

Looking at blog.gingerbeardman.com via nslookup it returns two IPv6 addresses and then two IPv4 addresses; Manually setting blog.gingerbeardman.com to resolve to either of the two returned IPv4 addresses via the hosts file instead of the OS chosing IPv6 over IPv4 makes it possible to load the site. So it seems as if IPv6 might be the culprit here (at least on my end, however other IPv6 websites work flawlessly)

Is there anything I can do about this?

@gingerbeardman Both DNS and propagation seem good, but there might be local caching or DNS issues still for some. I doubt it has anything to do with IPv4 vs IPv6, simply because I’ve never seen that behavior before.

If it loads in GTMetrix and other “external” services, and if it loads as expected in private / incognito windows, there’s not much you can do except wait for the rest of the Internet to catch up.

1 Like