Mats Dufberg
Mats Dufberg
> These files shows examples of how to configure nginx and Apache. They serve no function in themselves and should not be included in the zip nor uploaded to a...
First I created a zip file using the following steps that I think are valid (I have proposed updates to RELEASE.md): * Checked out the branch matching the PR. *...
> Also remember that since you build the release yourself, make sure the PUBLIC_API_URL in your .env matches your intended proxy path before building the release. When I built the...
I created a `.env` file and then ran the commands to create the zip file. But the `.env` file is not included. Where is it specified what will be included...
And then I created it in the base directory where the GUI is installed, but when I restarted apache it still says ``` [Wed Oct 15 11:16:31.113571 2025] [core:warn] [pid...
This PR is based on develop branch before the last release. I suggest that it is rebased on latest master or develop branch.
@MichaelTimbert, can you please handle the conflicts?
Zonemaster could send a query to get the NSEC or NSEC3 record of the apex of the zone, and then check that all listed record types in the NSEC/NSEC3 record...
@tgreenx, no, it does not. It is a different issue, and I think it should be a different test case. It can, however, be hard to test.
I guess that this only applies for off-line signed zones. If on-line signing is used then signature expiration should not be a problem. I do not know of any fail-safe...