How to Recover Your Custom Domain Blog on Hashnode

Software Engineer | Developer Advocate | Technical Writer | Content Creator
Search for a command to run...

Software Engineer | Developer Advocate | Technical Writer | Content Creator
Boss
In this series, I'll discuss numerous bugs that I experienced when developing and delivering an application, as well as how I was able to resolve them.
Hello it's a Fix 😪 Let's solve it! On your computer, go to Windows Credential Manager. On Windows, you can do this by pressing the Windows Key and typing 'credential.' Replace the old password with the new one in the git entry under Windows Crede...
Step-by-Step Solidity Guide for Beginners: Building Your First Token

Prioritizing Depth Instead of Going with Trends

Cross-chain messaging allows seamless communication and interaction between different blockchain ecosystems, from Ethereum Virtual Machine (EVM)-based chains to Cosmos-based chains. Axelar has long been the best way to connect EVM and Cosmos chains v...

You have millions of unique images in your gallery, each representing a piece of private or personal data stored on your phone. After an incident, you lost your device, but it was returned to you after many months, with claims that the images hadn't ...

Marking a Year of Contributions to Axelar: Pioneering the Future of Interoperability

Hi everyone! Yeah, it's a bug fix.
I woke up to a message in my DM on Twitter, as shown below saying my blog is not responding.
I was taken aback and investigated what had occurred; after about 5 hours, I was still trying to fix it with no success.
After troubleshooting, I realized the error was coming from CNAME mapped to my domain as suggested by Hasnode.

In the image above:
The first highlighted section represents the CNAME that was added earlier to my custom DNS, which stops working all of a sudden.
The second section is the A Record that I replaced with the CNAME on my custom DNS.
All you have to do now is go to your hosting platform and erase the CNAME record you added; don't worry, we'll recreate it later.
Add the A Record, point it to the IP address shown in the image above.
Your Blog should be live ✌️
It may take up to 24 hours for DNS changes to propagate fully. But it's usually pretty quick. You can check the progress by using a service like this
Visit this URL https://toolbox.googleapps.com/apps/checkmx/
It takes a couple of hours to resolve this issue; I hope you will fix it in less than 5 minutes.
Kindly Like and share with others. 😊
I'd love to connect with you at Twitter | LinkedIn | GitHub
See you in my next blog article. Take care!!!