When you cancel your website subscription with Shinybot, we will no longer manage your DNS records. This means any DNS settings previously handled by Shinybot—like your website's address and email routing—will cease to function under their system.

What You Need to Do

  1. Update Your Name Servers (NS Records)

    • Log in to your domain registrar's account: This is the service where you purchased your domain name.
    • Change the Name Servers: Replace Shinybot's Name Servers with those of your new hosting provider or revert to your registrar's default Name Servers. 
    • Save the Changes: Confirm and apply the new settings.

  2. Configure Your DNS Settings

    • Set Up DNS Records: Recreate essential DNS records (A records, CNAME records, etc.) with your new DNS provider to point your domain to the correct web servers.
    • Update Mail Records (MX Records): Ensure your MX records are correctly set up so your email services continue to work without interruption.
    • Check Other Services: If you use additional services like subdomains or third-party apps, update their DNS records accordingly.

Why This Is Important

  • Avoid Service Disruption: Failing to update your DNS settings can lead to your website and email becoming inaccessible.
  • Maintain Email Functionality: Incorrect MX records can result in lost emails or bounced messages.
  • Ensure Smooth Transition: Proper DNS management ensures that all services tied to your domain continue to operate seamlessly after canceling with Shinybot.

Tips:

  • Backup Current DNS Settings: Before making changes, note down all existing DNS records for reference.
  • Allow for Propagation Time: DNS changes can take up to 24-48 hours to propagate fully across the internet.
  • Seek Assistance if Needed: If you're unsure about making these changes, consider reaching out to your new hosting provider or a professional for help.

By promptly updating your Name Servers and DNS settings after canceling your Shinybot subscription, you can ensure that your website, email, and other domain-related services continue to function correctly.