Help Tag: DNS

  • What Semi Dedicated Hosting is and how a website migration works

    Text-free visual composition for Semi Dedicated Hosting

    Semi Dedicated Hosting sits between shared hosting and a fully independent server. It provides more resources and a more controlled environment without requiring the customer to handle all administration of an unmanaged server.

    When it makes sense

    • When the website has higher traffic or needs more resources.
    • When you need more isolation than a standard shared plan.
    • When you want provider-managed infrastructure without taking on full server administration.
    • When you host multiple demanding sites or reseller workloads.

    What technical support covers

    Core support covers the infrastructure, the hosting environment and service-related issues. Development work, application debugging, plugin changes or malware cleanup may be handled as a separate service.

    How migration is organized

    A migration requires access to the current hosting or a usable backup from Plesk, cPanel, ISPmanager or another supported panel. The team reviews the backup, moves files and databases and performs checks before DNS records are changed.

    Before changing DNS

    • Preview the new site and verify it loads correctly.
    • Test forms, email sending, database functions and cron jobs.
    • Lower TTL where appropriate.
    • Keep the old hosting available until the transition is complete.
    Helpful note

    Current resources, migration terms and any development charges are defined by the active plan and technical assessment, not by old commercial descriptions.

    Need more help?

    If this guide did not resolve your issue, continue with the easy support team.

    Contact support Ask easy AI
  • How to connect your domain to Wix, Weebly, Squarespace, Tumblr, Shopify, Blogger and WordPress.com

    Text-free visual composition for connecting a domain to external services

    When your domain stays at easy.gr but the website is hosted elsewhere, the connection usually happens through nameserver changes or DNS records. The legacy FAQ had separate short instructions for each platform; this article turns them into one practical reference.

    Wix

    With Wix you can connect an external domain either by changing nameservers or by DNS pointing. The platform typically recommends nameserver connection when you want Wix to handle the main site-side configuration.

    Weebly, Tumblr and Shopify

    • Weebly: root-domain A record to 199.34.228.59.
    • Tumblr: root-domain A record to 66.6.44.4.
    • Shopify: root-domain A record to 23.227.38.32.

    Squarespace

    • Four A records to 198.49.23.144, 198.49.23.145, 198.185.159.144 and 198.185.159.145.
    • A verification CNAME to verify.squarespace.com.
    • A www CNAME to ext-cust.squarespace.com or whatever current value your Squarespace account provides.

    Blogger

    • A records to 216.239.32.21, 216.239.34.21, 216.239.36.21 and 216.239.38.21.
    • A www CNAME to ghs.google.com.
    • An extra verification CNAME using the values shown in your Blogger account.

    WordPress.com

    In the legacy material, the connection used nameservers NS1.WORDPRESS.COM, NS2.WORDPRESS.COM and NS3.WORDPRESS.COM.

    Helpful note

    Exact DNS values and verification records can change on the external provider side. If something does not work, first compare the setup with the current documentation of the platform before assuming there is a registrar or DNS-zone issue.

    Need more help?

    If this guide did not resolve your issue, continue with the easy support team.

    Contact support Ask easy AI
  • How to reduce spam issues and configure SPF, DKIM and DMARC

    Text-free visual composition for spam handling and SPF, DKIM, DMARC setup

    If your messages land in spam or you want to protect your domain from spoofing, the first step is proper email authentication. SPF, DKIM and DMARC help remote mail servers verify that your messages are really sent on behalf of your domain.

    When an email may be considered spam

    An email may be treated as spam when it breaks basic sending policies, is sent in bulk without proper consent or lacks valid sender authentication. Besides the content itself, your domain DNS records play a major role.

    Why messages end up in junk or bulk

    • The recipient applies strict spam filtering and the sender reputation is weak.
    • SPF, DKIM or DMARC records are missing or not configured correctly.
    • The content or sending pattern looks suspiciously similar to bulk mail.
    • The domain or mail server does not yet have stable reputation with major providers.

    How to enable SPF and DKIM

    If you use cPanel, SPF and DKIM can usually be enabled through Email Authentication. SPF declares which servers are allowed to send mail for your domain, while DKIM adds a digital signature to your outgoing messages.

    When DMARC is useful

    DMARC complements SPF and DKIM and lets you define how receivers should handle messages that fail authentication checks. It can also send reports to a chosen email address so you can monitor possible abuse of your domain.

    Helpful note

    After updating SPF, DKIM or DMARC, allow some time for DNS propagation. In most cases 24–72 hours are enough for the new records to stabilize globally.

    What else to check

    If the issue persists, review IP reputation, avoid uncontrolled mass sending and make sure your From, Reply-To and actual sending servers are consistent.

    Need more help?

    If this guide did not resolve your issue, continue with the easy support team.

    Contact support Ask easy AI
  • DNS propagation: why changes are not visible immediately

    Text-free visual composition for DNS propagation and preview

    What propagation is

    DNS resolvers cache answers temporarily. After nameserver or record changes, the old cache must expire before every location sees the update.

    What to verify

    • The new records are correct.
    • The TTL is not unusually high.
    • You are not testing through only one resolver or device.

    Need more help?

    If this guide did not resolve your issue, continue with the easy support team.

    Contact supportAsk easy AI
  • Domain activation and holder verification

    Text-free visual composition for domain activation and ownership verification

    Order completion, Registry activation and website availability are separate stages.

    When a new domain becomes active

    The application is submitted to the relevant Registry after the order is confirmed. Timing depends on the extension, its validation process and whether additional information is required. The status appears in easy control.

    Why the website may not appear immediately

    Even after activation, the domain needs correct nameservers or DNS records and DNS propagation may be required. Domain activation does not automatically create a website or hosting service.

    How to verify the holder

    Review the domain details in your account and, where permitted, through WHOIS or RDAP. Restricted public display of personal data does not mean that the domain has no registered holder.

    Important

    The holder email must remain active because it may be used for approvals and protected actions.

    Need more help?

    If this guide did not resolve your issue, continue with the easy support team.

    Contact support Ask easy AI
  • How to Move Your Website to easy.gr Without Downtime

    Illustration of website migration steps and checklist

    Overview

    Moving hosting doesn't have to cause downtime or stress. With easy.gr you can transfer your site smoothly by following a few clear steps and testing everything before switching your domain. This guide walks you through the process end to end.

    Why move hosting?

    • Slow page load times
    • Frequent server or support issues
    • Lack of security or outdated protections
    • Need for local-language support and reliable technical help

    easy.gr provides improved speed, stability, support and security, including branded SSL options.

    Step-by-step migration

    Step 1 — Contact easy.gr support

    Get in touch with easy.gr and tell them you want to migrate your site. Their team will provide guidance and, if you prefer, can carry out the transfer for you.

    Step 2 — Take a full backup

    Request or download a complete backup of your site files and the database from your current hosting provider. Keep this backup safe until the migration is finished.

    Step 3 — Upload your site to the new server

    Transfer your files and import the database to the easy.gr server via FTP or the control panel. Make sure file permissions and database connection settings are correct.

    Step 4 — Test on a temporary URL

    easy.gr provides a temporary/test URL so you can review the site on the new server and confirm everything works before the domain is changed.

    Step 5 — Update nameservers or DNS records

    Once you’ve verified the site on the new server, change your domain’s nameservers or DNS records to point to easy.gr. DNS changes usually take up to 24 hours to propagate fully.

    Bonus tipsKeep the old hosting active for 1–2 days after switching DNS to ensure no traffic or emails are lost.Update email account settings if your email was hosted with the previous provider.After the migration, verify HTTPS/SSL—especially if you use a branded SSL certificate from easy.gr.

    Final checklist before you finishFull backup taken from the old host (files + database)Files and database uploaded to the easy.gr serverSite tested via temporary URL and functionality verifiedEmail accounts reconfigured if neededNameservers or DNS records updatedHTTPS/SSL confirmed to be workingOld hosting kept active until DNS propagation completes

    Conclusion

    With simple preparation and the support of easy.gr you can migrate your website without downtime. Follow the steps above, test thoroughly on the temporary URL and keep the old hosting briefly until DNS propagation completes for a smooth transition.