more validation for NS and SRV records; fix display of long records
Signed-off-by: Michael Kaufmann (d00p) <d00p@froxlor.org>
This commit is contained in:
@@ -1999,6 +1999,9 @@ $lng['error']['dns_mx_needdom'] = 'The MX content value must be a valid domain-n
|
||||
$lng['error']['dns_mx_noalias'] = 'The MX-content value cannot be an CNAME entry.';
|
||||
$lng['error']['dns_cname_invaliddom'] = 'Invalid domain-name for CNAME record';
|
||||
$lng['error']['dns_cname_nomorerr'] = 'There already exists a resource-record with the same record-name. It cannot be used as CNAME.';
|
||||
$lng['error']['dns_ns_invaliddom'] = 'Invalid domain-name for NS record';
|
||||
$lng['error']['dns_srv_prioempty'] = 'Invalid SRV priority given';
|
||||
$lng['error']['dns_srv_invalidcontent'] = 'Invalid SRV content, must contain of fields weight, port and target, e.g.: 5 5060 sipserver.example.com.';
|
||||
$lng['error']['dns_srv_needdom'] = 'The SRV target value must be a valid domain-name';
|
||||
$lng['error']['dns_srv_noalias'] = 'The SRV-target value cannot be an CNAME entry.';
|
||||
$lng['error']['dns_duplicate_entry'] = 'Record already exists';
|
||||
|
||||
Reference in New Issue
Block a user