UKC

How do I upgrade to multi domain hosting?

If you currently have a hosting plan which was setup before the Multi-domain feature was offered contact the Helpdesk for a free upgrade.

The “Add Domain” and “Resource Management” features will be added to your account within 24 hours thus enabling Multi-domain features..

It is not possible to merge existing separate hosting accounts into a Multi-domain hosting plan. However, at the time your accounts are up for renewal, if you find they are not using many resources you could allow your package to expire and add then add domain to your Multi-domain account.

If your hosting plan is currently on our Ensim server range, then you might want to consider upgrading to our Plesk server range – the upgrade is free, see Upgrading to Plesk from Ensim FAQ entry.

How to Add Another Domain to Plesk Hosting

Plesk multi-domain hosting

Use Add Domain in Plesk, then point the domain to the assigned hosting service

Adding a domain to Plesk creates hosting space but does not register the name or change its DNS. Confirm that the hosting plan has an available website allowance, add the domain, then connect it using the nameservers or DNS values from the welcome email.

Open My HostingSee the steps
STARTConfirm the serviceUse the account-specific route
PROTECTRecord current settingsAvoid accidental disruption
CHECKTest the resultKeep the exact error if it fails

How do you add a second domain in Plesk?

Follow the sequence and stop before any step that does not match the service shown in your UKC account.

  1. 1
    Check the domain and plan

    Register the domain if needed and confirm the Plesk subscription has capacity for another website, database, storage and mailbox use.

  2. 2
    Add the domain in Plesk

    Open Websites and Domains, choose Add Domain and enter the complete name. Select a new site rather than an alias when it needs separate content.

  3. 3
    Create or upload the website

    Use Sitejet, WordPress Toolkit, the application installer or Files. Keep the site private or on a temporary route until it is ready.

  4. 4
    Connect DNS and secure it

    Apply the exact assigned nameservers or records, wait for DNS to resolve, then issue Let’s Encrypt SSL and test both root and www addresses.

What should you decide before adding the domain?

The right Plesk object depends on whether the name needs a separate website, points to an existing site or is only used for mail.

Separate website

Choose Add Domain and give it its own document root, site content and SSL certificate.

Domain alias

Use an alias when another name should display or redirect to the same hosted website. Avoid creating duplicate indexable content.

Subdomain

Use a subdomain for a section such as shop.example.co.uk. It remains part of the parent domain and needs its own DNS and certificate coverage.

Email only

A domain can be added for mail without a public website, but DNS MX, SPF, DKIM and webmail records must be correct.

CheckRequired result
Hosting allowanceAn available website slot and sufficient resources
DNSDomain resolves to the assigned UKC server
SSLCertificate covers every public hostname
BackupsNew site included in the chosen backup routine

Common questions

Does Add Domain register the name?

No. Registration and hosting are separate. Register or transfer the name independently.

Which nameservers should I use?

Use the exact pair in the hosting welcome email. Do not use the parked-domain nameservers for a Plesk-hosted zone.

Why is Add Domain unavailable?

The plan may have reached its website limit or the account may not permit that object. Check the subscription allowance.

Can I move an existing site into the new domain?

Yes, but copy files and databases, update application URLs, test privately and keep a rollback before changing live DNS.

Ready to add the site?

Open the correct Plesk subscription and check its capacity

Add the domain first, prepare the content, and connect DNS only when the replacement is ready.

Open My HostingAsk UKC Support
nn

How do I access mySql databases from a remote client?

It is possible to configure a database user in your Plesk control panel so that you may access your mySQL databases remotely – ie. directly from your home or office PC network.

By default, all remote access to mySQL is blocked by the firewall, this prevents your databases being hacked externally. Remote access can only be granted to a static IP address. If you have a dynamic IP address you need to contact your internet provider and request a static IP address, some providers charge for this service.

To enable remote access to a mySQL database

  1. Create a database (if not done so already)
  2. Create a database user that will be used for remote access
  3. Advise the Helpdesk of your Static IP address
  4. Allow 24 hours for the firewall to be updated
  5. Once enabled you will be able to connect using port 3306

That’s all there is to it! If you have any problems simply contact the Helpdesk for further assistance,

How do I park my domain name?

To make use of the domain parking features your domain name needs to have the nameservers set to point to the parking server.

The domain nameservers or the parking server are:

  • ns.microlite1.com
  • ns2.microlite1.com

Once parked, your domain can be used with all parking services such as:

  • unlimited email forwarding
  • web forwarding using 301 and 302 redirects
  • framed web forwarding
  • homepage builder

See: How to change your domain nameservers for further instructions.

Why DNS and Nameserver Changes Take Time

DNS changes and caching

DNS changes can be correct immediately at the source while older answers remain cached elsewhere

This delay is usually caching, not data travelling between servers. Recursive DNS services remember previous answers for their time to live, or TTL. Nameserver changes also update delegation at the registry and can leave different networks seeing old and new answers for a period.

Check My DomainCheck the change
TTLControls cache lifetimeOld answers may remain
SOURCEAuthoritative DNSWhere records originate
VIEWResolvers cache answersNetworks update at different times

Why do different people see different results?

Cached record

A resolver may keep an old A, MX or CNAME answer until its earlier TTL expires.

Nameserver delegation

A nameserver change updates the parent registry or TLD delegation as well as the zone served by the new provider.

Local device cache

Browsers, operating systems and routers can temporarily remember a response after the wider resolver has changed.

Incomplete new zone

A genuine configuration error can resemble propagation. Missing email or verification records will not repair themselves with time.

How do I check whether the change is working?

  1. 1
    Confirm the authoritative nameservers

    Check which nameservers the registry currently delegates the domain to.

  2. 2
    Query the intended record

    Check the authoritative answer for the exact host and record type you changed.

  3. 3
    Compare public resolvers

    Different results indicate caching. The same wrong result everywhere usually points to the source configuration.

  4. 4
    Test the actual service

    Open the site over HTTPS and test incoming and outgoing email rather than relying on a single DNS checker.

How can I reduce disruption before a planned change?

BeforeAction
Record inventoryCopy the complete working zone, especially MX, SPF, DKIM and verification records
Lower TTLReduce relevant TTL values in advance where the current DNS provider permits it
Prepare new serviceConfigure the destination website, certificate and mail handling before switching traffic
Keep old serviceLeave it available while caches may still direct visitors or mail there

DNS timing questions

How long does propagation take?

It depends on the previous TTL, resolver behaviour and whether nameserver delegation changed. Check the authoritative answer and the old TTL instead of relying on one universal time estimate.

Will clearing my browser cache help?

It may remove a local copy but cannot clear a record held by your network resolver. Testing through another resolver or connection helps separate the two.

Can email arrive at both old and new servers?

During an MX change, different senders may temporarily use different cached answers. Keep both services able to accept mail during the transition where possible.

Check the source first

Confirm nameservers and the authoritative record

Once the source is correct, cached answers can expire naturally. If the source is wrong, update it rather than waiting.

Open Domain Tools
Categories DNS