After Plesk 6 came Plesk 7, then Plesks 8, 9, 10, 11, and 12. When the most recent iteration of the latter version (Plesk 12.5) was to be upgraded, the next name in the series was sure to be Plesk 13, right? Well, with the obvious negative and unlucky connotations of the number 13 (I’m looking at you, Judas) Plesk decided it was time to ditch their previous naming conventions.

They considered a route similar to Ubuntu 12, Ubuntu 14, and Windows Server 2008/2012/2016, where the release version is correlative to the year of release. However, with a projected release date of Q4 2016 they considered that within a few months ‘Plesk 16’ would be outdated even whilst still fairly new. So they briefly settled on ‘Plesk 17’. But eventually, they decided that the incremental numbering system was old-fashioned and confusing – particularly when skipping four and a half numbers for little discernible reason.

PHP skipped the number six and went straight from version 5.6 to 7. Microsoft called the third version of their gaming console ‘Xbox One’ – a backwards turn by three hundred and fifty-nine digits. After Rocky, Rocky II, Rocky III, Rocky IV and Rocky V came… Rocky Balboa.

At some point just adding another one to a release version doesn’t hold the appropriate weight. Sometimes the upgrade is so revolutionary that it needs a revolutionary new name altogether (although, maybe not-so-much in the case of Rocky Balboa).

And thus…

Plesk Onyx

An onyx stone is traditionally supposed to protect one from harm, build physical strength and absorb light – giving properties of invisibility. This, as it turns out, is a good metaphor for Plesk Onyx itself. Plesk Onyx gives the user’s servers security and performance, and it does so almost invisibly in the background.

Additional security features include a default Security Advisor extension, improved backups, greater SSL protection with Let’s Encrypt, and one-click or automatic system updates. Plesk Onyx heals itself, solving technical issues without the need for support.

For extra performance, Plesk Onyx allows management of all Plesk servers from one control panel. The Log Browser tool has been improved for quicker, simpler monitoring and debugging, and support for Git, Windows Server 2016, Ruby and Docker.

A server control panel like Plesk Onyx helps web developers, designers and sysadmins manage their servers. Plesk Onyx makes it easier and quicker to manage multiple servers from the same control panel. Plesk Multi Server allows for centralised account management across multiple Plesk instances. Individual accounts can be created for admins and users, allowing control of the server from across the business.

Plesk Onyx is now available on all Windows, Ubuntu, Debian and CentOS operating systems on GIWS Cloud Servers.

The post Plesk Onyx server management appeared first on GIWS Blog.

Domain resolution is also called domain pointing, server settings, domain configuration, reverse IP registration, and so on. To put it simply, the easy-to-remember domain name is resolved into IP. The service is completed by the DNS server, which resolves the domain name to an IP address, and then binds a subdirectory to the domain name on the host of this IP address.

The address on the Internet is a digital IP address, and the main purpose of domain resolution is to facilitate memory.

How Domain Resolution Works

After registering a domain name with a domain registrar, how can I see the content of my website? In a professional term, it is called “domain name resolution”.

The domain name is a set of address conversion systems specially established for the convenience of memory. To access a server on the Internet, it must ultimately be achieved through an IP address. Domain name resolution is the process of converting a domain name into an IP address. One domain name corresponds to one IP address, and one IP address can correspond to multiple domain names; therefore, multiple domain names can be resolved to one IP address at the same time. Domain name resolution needs to be completed by a dedicated domain name resolution server (DNS).

Domain Resolution Process

For example, if a domain name is abc.com, if you want to visit the website, it must be resolved. First, resolve to a fixed IP of a WEB server: 211.214.1.XXX through a dedicated DNS server from the domain registrar. Then, the domain name is received through the WEB server, and the domain name abc.com is mapped to this server. Finally, enter the domain name abc.com to access the website content. This realizes the whole process of domain name resolution.

People are used to remembering domain names, but machines only recognize each other’s IP addresses. There is a correspondence between domain names and IP addresses, and the conversion between them is called domain name resolution. Domain name resolution needs to be completed by a dedicated domain resolution server, and the whole process is automatic.

Computers on the Internet are located by IP addresses. Given an IP address, you can find a certain host on the Internet. And because IP addresses are difficult to remember, domain names were invented to replace IP addresses. However, the host to be accessed cannot be found directly through the domain name. A process of looking up the IP address from the domain name is added in the middle. This process is domain name resolution. After the domain name is registered, the registrar provides free static resolution services for the domain name. General domain name registrars do not provide dynamic resolution services. If you need to use dynamic resolution service, you need to pay for it.

Domain Resolution Types

• A record Resolution
  Select “A” for the record type; fill in the record value with the host IP address provided by the hosting provider; MX priority does not need to be set; TTL can be set to the default 3600.
• CNAME Record Resolution
  The CNAME resolution setting method is basically the same as the A record. Modify the record type to “CNAME” and fill in the server host address for the record value.
• MX Record Resolution

MX Record Resolution is used for mailbox resolution. Select MX for the record type; fill in the server IP address or alias address for the record value; set the default TTL to 3600; when there are multiple MX records, the priority should be set to different data.

Domain Resolution Operation

• Configure DNS
  After the domain name application is successful, domain resolution is required first. Click DNS resolution management, then add IP, add alias and mail MX record.
• Modify DNS
  • Condition: The primary and secondary DNS servers to be changed must be registered and legal DNS server names, otherwise the modification will fail.
  • Modification method: Perform domain name change DNS operation through the corresponding domain name registration company.
• Resolution effective time
  The resolution of the generic top-level domain name takes effect within 2 hours, and the resolution of the national top-level domain name takes effect within 24 hours.

The post What Is Domain Resolution and How It Works appeared first on GIWS Blog.