Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Registrar: csv based bulkchange #993

Open
vohmar opened this issue Sep 21, 2018 · 0 comments
Open

Registrar: csv based bulkchange #993

vohmar opened this issue Sep 21, 2018 · 0 comments

Comments

@vohmar
Copy link
Contributor

vohmar commented Sep 21, 2018

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant