Thomas Pike

DNS UI doesn't handle any authentication[1] (yet), so you need to handle it in Apache. For example using [AuthUserFile](https://httpd.apache.org/docs/2.4/mod/mod_authn_file.html) with a user file that you generate yourself with `htpasswd`. Example...

Also since you would have no users in the database yet, you'd need to manually create one (via SQL commands) that matches a username in the `htpasswd` file.

Great news! Thanks for this

I believe it's hardcoded here: https://github.com/operasoftware/dns-ui/blob/5be6deb7ce92ddd17ab9a126bbfc256bc23d8aa1/templates/zone.php#L40 it should be very easy to edit, though there is no configuration setting for it.

Yes, I agree this needs improvement. The original design assumption was that it would be convenient to remove all quoting and escaping from TXT records when displaying them in the...

Agreed, that's probably the best strategy. While I'm not usually a huge fan of "magic" behaviour that changes based on the input, I think it's sane in this case to...

Thanks, that certainly needs fixing too.

I would guess that the problem is that you haven't set up authentication in Apache (the `Not logged in` message would imply that you are currently able to access the...

Thank you for your kind words. [Using `CGIPassAuth on`](https://stackoverflow.com/a/33254772) or [this workaround](https://stackoverflow.com/a/17490827) might be relevant solutions to getting Apache authentication information to PHP when using FastCGI.

This doesn't look like an error related to DNS UI itself, but instead seems to be related to your SSL setup in Apache. See https://www.digicert.com/ssl-support/apache-fix-common-ssl-errors.htm#SSLRecordLength