Integrate Hashnode with Netlify website - Adding A records

I’m trying to integrate HashNode into my website. To do this, I need to add a new A record but I’m receiving an error that says “link exists, all config must be empty”. Apparently the NETLIFY record needs to be deleted to add this new record, but I don’t know if this will cause issues with my website if this is done. Can anyone assist with how I can add the A record?

hi there, which site is this regarding? we can flip a switch to allow you to edit this manually.

This is for my personal website, Can you advise when I’ll be able to add the A record? Thanks

hi there, we flipped a switch that will allow you to first delete and then add a new A record. Let us know if you need more assistance.

Thanks. What will happen if I delete the record “”? Will that mean that that URL will no longer redirect to my website And if so, would I be able to add it again afterwards?

hi there, once you have deleted the A record, you will be able to add a new one to point to the right place. You should immediately add a new record to avoid downtime.

You can read more on A records here:

I don’t know a lot about HashNode, can you explain a little what it is? I wonder if there is a better way to accomplish what you are trying to do without messing with the A records :thinking:

HashNode is a blogging platform, but they also offer you the ability to host the blogs you write on your own website. So you create the article on HashNode, then it gets published to They need you to add an A record so they can push your article to your website I’m assuming.

Once I’ve added the new A record from HashNode, will I be able to re-add the record I deleted initially?

Hey @jacobcollinsdev,
Are these the instructions you’re following?

or could you please share the ones you’re using?

The setup you describe would mean that your apex domain ( will no longer redirect to your website at One better option may be creating a CNAME record in your Netlify DNS panel for that points to your HashNode blog.

Another option would be to instead proxy to that blog. Then you wouldn’t have to fiddle with DNS so much- you’d just route requests to* to your HashNode blog under the hood. Here are our docs on that:

Let us know what your preference is and we’ll help you get set up!

Hi, the instructions I followed appear when adding the domain on the HashNode dashboard and read as follows:

"CNAME instructions (Please read the details carefully)

Head over to your DNS provider and add a CNAME record where the host name is @ and the corresponding value is . We’ll automatically provision an SSL certificate for you when you visit your blog for the first time. If you are using something like Cloudflare, please bypass it for this domain .

:bulb:It’s not recommended to use CNAME record at root level. If you intend to do so, please make sure your DNS provider supports CNAME flattening. If you are still unable to do so, you can add an A record at the root whose value is . However, you will lose the benefits of our global CDN and edge caching with this approach.

:warning: If you are changing or deleting your domain, be sure to remove the old CNAME/A record from your DNS."

I’m thinking I’ll go with adding a CNAME record for Could you please advise on what the CNAME fields should be filled with?

Great! Could you give this a try in our UI here: Click “Add new record” and then your CNAME will look like this:

The records can take 24 hours to propagate (though they usually don’t take that long) so you may not immediately be able to access your blog via

Thank you, I’ve added the record and set the domain on hashnode to I’ll let you know if I experience any further issues.

Thanks for all your help!

1 Like

Hello jen can you help me.i have set the subdomain in hashnode and set the cname record for the subdomain like this in netlify, but the site ( show ‘not found’ message. The subdomain before is used in one of my site, so i removed it from the site, and create new record. Please note i’ve been waiting for 24 hours also.

Hey @tegvr,
Can you please share the full url of your blog at Hashnode? It will have to be publicly accessible on the internet in order for the DNS record at Netlify to point to it.

Works now :slight_smile: You had some existing NETLIFY and NETLIFYv6 records set for that were pointing to Netlify sites. I deleted them so that your CNAME for that subdomain pointing to your Hashnode blog would take over. Let us know if you need anything else!

thanks for your help.

1 Like