Currently DNS is just an input field:
In practice this is another field which allows entering multiple comma-spaced values. These values can be either an IP address (v4 or v6) or a domain/subdomain.
I think it would make sense for this input to reflect the actual structure of our DNS config. A user can provide two types of data:
Both of these are optional and both of these can be specified multiple times (more than one IP, more than one domain). The order of multiple values of the same type does have significance.
In the future we'll also probably implement properly handling routing domains and search domains so each domain element will be marked as one or both of these.
Currently DNS is just an input field:
In practice this is another field which allows entering multiple comma-spaced values. These values can be either an IP address (v4 or v6) or a domain/subdomain.
I think it would make sense for this input to reflect the actual structure of our DNS config. A user can provide two types of data:
Both of these are optional and both of these can be specified multiple times (more than one IP, more than one domain). The order of multiple values of the same type does have significance.
In the future we'll also probably implement properly handling routing domains and search domains so each domain element will be marked as one or both of these.