Prefill default name servers on order form

[HostinPK]

At present, clients have to fill the name servers while ordering the domain name and obviously they don't know what to enter there.

So, its a good idea to prefill the name server fields with the default name servers (defined somewhere in Blesta).

 

I am sorry for this post, if someone already has the solution to this issue, can guide me here or point to any URL containing the solution to this issue.

[Franz]

I suggested this over on the feature requests board you should add your vote and comments there https://requests.blesta.com/topic/domain-manager-default-nameservers

[HostinPK]

5 hours ago, Franz said:

I suggested this over on the feature requests board you should add your vote and comments there https://requests.blesta.com/topic/domain-manager-default-nameservers

Thanks. I have voted there

[Panormitis]

Any updates on this?

[Panormitis]

Until this feature is ready, if you are using Domain Manager you could set the correct nameservers beforehand for each TLD and these nameservers will be autofilled during ordering a domain name.

Unfortunately TLDs would have to be edited one by one to set the nameservers, so if you has a lot of TLDs is a pain, but you could use an SQL query on the database to update the TLDs faster:

-- Define your desired nameservers as serialized PHP array
SET @ns_value := 'a:4:{i:0;s:14:"ns1.domain.com";i:1;s:14:"ns2.domain.com";i:2;s:0:"";i:3;s:0:"";}';

-- Update only package_meta entries with key 'ns' and an empty value
UPDATE package_meta
SET value = @ns_value
WHERE `key` = 'ns'
  AND serialized = 1
  AND (value = 'a:0:{}' OR value IS NULL);

Backup the database first, use it at your own risk. Change ns1.domain.com & ns2.domain.com to your actual nameservers and change s:14 to the correct string length of your nameservers (eg. ns1.domain.com is 14 characters long, that's why s:14).

[Paul]

We have plans to add a bulk name server update option, as soon as v5.13 per https://dev.blesta.com/browse/CORE-5337

[Panormitis]

Thanks Paul, it would be a nice feature when completed. For now I managed to do what I needed with my SQL query above.