If a domain is specified to use Komorebihost's Cloudflare DNS nameservers service at the time of registration or transfer, activation and basic configuration are completely automatic. The DNS zone will be created, and a basic record set will be configured, potentially based on user-defined customizations.
Our default nameservers are:
jill.ns.cloudflare.com
eric.ns.cloudflare.com
Sometimes, if the above nameservers are not working, use:
aida.ns.cloudflare.com
owen.ns.cloudflare.com
If a domain was registered or transferred to us without initially requesting the use of our DNS servers, and the user wants to activate our DNS service later, they will need to create the corresponding "DNS zone" beforehand. To do this:
1. Inside the standard Control Panel area, select the menu option Domains → Manage DNS.
2. Locate the DNS service row for the domain you want to activate with our DNS servers and click on Add New Zone.
*(Note: DNS services are listed alphabetically, so you may need to scroll through the list to find the relevant domain.)*
The system will prompt you for the following details:
Zone Name: Enter the domain name without "www".
IP Address: Leave this field blank.
Select Record Set: If you have multiple Record Sets, choose which one to apply; otherwise, the default will be applied.
To conclude, click on Add Zone.
At this point, the basic zone will have been created. You can access it and modify it as necessary after logging into the DirectAdmin control panel:
1. Select Account Manager → DNS Management.
After creating the DNS zone, you can go to the domain management page and set up our default nameservers. This can be done immediately after creating the zone or at a later time, depending on your needs. Keep in mind that modifying authoritative nameservers is never an operation with immediate effect. Depending on the domain extension, propagation times vary due to technical registry processes and internet propagation delays (from a few minutes up to 24 hours). Examples include:
Registry nic.it (.it domains): Updates parent nameservers every 2 hours; adopting new nameservers may take up to two hours from the request, followed by propagation times. If nameserver checks fail, nic.it will retry for 7 days before declaring failure.
Registry register.si (.si domains): Updates parent nameservers once a day.
Registry Verisign (.com, .net, .org, .us domains): Updates parent nameservers every 5 minutes and does not perform checks.
