Even though the domain names are case insensitive, database may contain values which contain uppercase letters.
This is not being handled in PowerDNS Admin interface right now.
Displaying such zone would cause all records to also have zone name in the record (instead of '@').
Stripping fails due to records not being uppercase, while zone is.
If you change and commit those records to PowerDNS it would then append zone name again to the records.
Example zone:
www CNAME Active 3600 example.com
@ A Active 3600 127.0.0.1
When it is in database noted as 'Example.com' instead of 'example.com' it would be displayed like this:
www.example.com CNAME Active 3600 example.com
example.com A Active 3600 127.0.0.1
After adding record and refreshing domain names would get corrupted:
www.example.com.example.com CNAME Active 3600 example.com
example.com.example.com A Active 3600 127.0.0.1
new.example.com A Active 3600 127.0.0.1
This should be easily fixed by first converting zone name to lowercase on stripping.
Even though it is not expected to have zones in uppercase in the database, I think interface should not corrupt the zone if it appears.
Even though the domain names are case insensitive, database may contain values which contain uppercase letters.
This is not being handled in PowerDNS Admin interface right now.
Displaying such zone would cause all records to also have zone name in the record (instead of '@').
Stripping fails due to records not being uppercase, while zone is.
If you change and commit those records to PowerDNS it would then append zone name again to the records.
Example zone:
When it is in database noted as 'Example.com' instead of 'example.com' it would be displayed like this:
After adding record and refreshing domain names would get corrupted:
This should be easily fixed by first converting zone name to lowercase on stripping.
Even though it is not expected to have zones in uppercase in the database, I think interface should not corrupt the zone if it appears.