You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are bulk change options for replacing a technical contact with another and a nameserver with another, but registrars also need sometimes bulk add option for example to add a nameserver to the list of domains in addition to the ones already there. To enable this we should introduce csv based bulk change similarly to existing bulk transfer option.
Registrar specifies in the csv the domain and list of nameservers together with ip addresses (required in case of glue records). Running the bulk change process will replace all the existing nameservers on each domain with the ones specified in the csv.
Web portal must inform user of requirements to the csv file - which columns, in what order need ro be present, column headings (yes/no), etc. The info should be present in the bulk change view.
Required validations:
the domain must belong to the registrar (registrars cannot change anything for the domains that they are not current registrars of)
nameservers' fqdn and ip addresses must be valid in format
other domain data must be valid (associated contacts)
there are no blocking prohibitions (server/clientUpdateProhibited) or pending operations (ie pendingUpdate, seleteCandidate)
glue records must have at least one IP address specified
Input:
CSV file with two columns - domain name, nameserver (jsonb with nameserver fqdn and ip addresses if required (needed only for glue records)
output:
number of successful updates
list of domainnames that update failed - possibly with respective error message
The text was updated successfully, but these errors were encountered:
There are bulk change options for replacing a technical contact with another and a nameserver with another, but registrars also need sometimes bulk add option for example to add a nameserver to the list of domains in addition to the ones already there. To enable this we should introduce csv based bulk change similarly to existing bulk transfer option.
Registrar specifies in the csv the domain and list of nameservers together with ip addresses (required in case of glue records). Running the bulk change process will replace all the existing nameservers on each domain with the ones specified in the csv.
Web portal must inform user of requirements to the csv file - which columns, in what order need ro be present, column headings (yes/no), etc. The info should be present in the bulk change view.
Required validations:
Input:
CSV file with two columns - domain name, nameserver (jsonb with nameserver fqdn and ip addresses if required (needed only for glue records)
output:
The text was updated successfully, but these errors were encountered: