How to Publish a Domain with the Plesk panel

To publish a domain with the Plesk panel, first verify which DNS servers the domain uses and confirm the server address in your Plesk account. Then add the domain from the Websites & Domains section, create DNS records in the correct place, upload the files to the selected document root, and reopen the same address to check the new records. Because DNS authority varies by provider, a change made in one panel may not be sufficient for every setup.

Access and prerequisites for Plesk panel setup

This process can be completed with site-administrator access to a shared hosting account or with a Plesk account on a server managed by an administrator. Before starting, you should have access to the domain registrar, your Plesk subscription details, and the site's files and database information. If you are not the server administrator, the IP address, PHP version, database-creation permission, and responsibility for DNS management may depend on the provider.

Before making changes, record the existing DNS records and the domain settings in Plesk. In particular, record the A, AAAA, www, and MX records used for mail separately to support a safe rollback. If you only want to move the website, do not change mail records arbitrarily; web routing and email routing do not serve the same function.

Adding the domain to the Plesk panel and selecting the document root

1. Open the domain-addition screen. In Plesk, open the option for adding a new domain from Websites & Domains or the corresponding domain-management section. Enter the domain without www at the beginning and specify the site's document root, meaning the folder from which the web files will be read. As a result, the domain should appear in the subscription list; if it does not, correct your account permissions or the domain spelling before moving on to DNS.
2. Verify the hosting type and basic settings. Make sure the domain uses a hosting type that serves a website and that you have not accidentally selected only forwarding or DNS hosting. If Plesk's default page opens, the domain may have reached the server, but your site's files may not yet be in the selected document root. Noting this distinction before uploading files will help you interpret the next error correctly.
3. Determine where DNS is authoritative. If the domain's nameserver records point to the Plesk server, manage the DNS records in Plesk's DNS Settings screen. If the nameservers point to an external DNS provider, create the A and, where necessary, AAAA records in that provider's interface; a record change made in Plesk may not be published externally. The A record should point to the server's IPv4 address, while an AAAA record should be used only when the server actually has the correct working IPv6 address.
4. Check the www address separately. Confirm that the records for the root domain and the www subdomain are consistent. If the provider supports it, you can use a CNAME for www that points to the main domain; if you use a different A record, it should point to the same server. If the domain-query screen shows multiple conflicting A records or an old AAAA record, do not delete a record before verifying which service it belongs to; correct only the old record under your control.
5. Upload the files to the correct document root. Using Plesk File Manager or your chosen deployment method, place the main entry file in the folder you selected. If the domain returns a 404 error, first check whether the file is actually in this document root and whether the application requires a subfolder. If the home page loads but CSS and images cannot be found, check the application's relative URLs and domain settings; changing all file permissions at once is not a safe fix.
6. Repeat the same request and examine the new evidence. After changing DNS, reopen the same domain and URL you used in the previous attempt. Note the test time and look for new lines from that time in the access and error log screens for the relevant domain in Plesk. If the new entry shows a 404 and the document root, correct the path setting; if it shows a 403 and directory access, inspect the main entry file, the application rule, and access settings belonging to the account owner. If no new entry is created after the change, the request most likely is not reaching this server; check the DNS response and nameserver authority again first.

Interpreting the result: DNS or a Plesk panel setting?

If the domain does not open at all or a page from another server appears, evaluate the DNS result first. If the A record does not point to the correct IP or no change was made at the external DNS provider, changing the document root in Plesk will not solve the problem; correct the record in the authoritative DNS interface. If the domain reaches the correct server and Plesk's default page appears, the DNS stage is largely complete; you should then examine the file location, hosting type, or application's entry file.

Suppose exampledomain.tld opens directly, but www.exampledomain.tld returns a 404. In this case, instead of changing the main domain's document root, query the www record first. If www points to another IP, direct the record to the correct server; if it reaches the correct server but is defined in Plesk as a separate subdomain, check its document root and hosting settings. If both addresses reach the same server but only www returns an error, this distinction enables a targeted correction.

Safe rollback if the problem continues

Do not change multiple settings at the same time. If you do not get the expected result after updating a DNS record, first compare the new time-stamped log entry with the DNS response; do not randomly change the PHP version, permissions, or server settings. If the domain was previously connected to a working service, restore the old record you noted to temporarily return to the previous state, then make another attempt with a single variable changed. Because DNS caches may continue to show old responses for a while, account for the fact that the rollback may not appear immediately across all networks either.

If you use Plesk on a VDS that you manage yourself and want full control over panel access, DNS authority, or log inspection, you can review the Turkey VDS server plans page to evaluate suitable environments. As the first next step, record the domain's authoritative nameserver and its A/AAAA records; then verify in Plesk that the selected document root actually contains the site's entry file.