mirror of https://github.com/getnamingo/registry.git synced 2025-05-12 09:48:35 +02:00

Pinga 57c9f62052 DNSSEC housekeeping and more automation

2025-03-11 19:18:15 +02:00

54 KiB

Raw Blame History

Configuration Guide

This document provides instructions for configuring Namingo, the domain registry management tool, after installation. It covers configuring the system, adding additional components, and customizing various configuration files for optimal setup.

1. Post-Installation Configuration

This section provides instructions for configuring your system after installing Namingo, including setting up additional components and customizing configuration files.

1.1. Launching WHOIS, RDAP, and DAS Servers

To start the WHOIS, RDAP, and DAS servers, use the following commands:

systemctl start whois
systemctl start rdap
systemctl start das

Ensure each service is properly configured before starting. You can verify the status of each server with:

systemctl status whois
systemctl status rdap
systemctl status das

1.2. Launching EPP Server

Before launching the EPP server, edit /opt/registry/epp/config.php to set the paths to your certificates and configure other options as needed.

To create test certificates (cert.pem and key.pem), execute the following commands:

cd /opt/registry/epp/
openssl genrsa -out key.pem 2048
openssl req -new -x509 -key key.pem -out cert.pem -days 365

Once configured, you can launch the EPP server in the same way as the others:

systemctl start epp

1.3. Optional Control Panel Configuration

Features You May Want to Enable or Customize:

1.3.1. Customizing the Logo and Pages

1.3.1.1. Customizing the Logo: Upload your custom logo as logo.svg to /var/www/cp/public/static/. If logo.svg is not present, the default logo.default.svg will be used automatically.

1.3.1.2. Customizing the Documentation Page: To customize the documentation, copy docs.twig to docs.custom.twig using the command cp /var/www/cp/resources/views/admin/support/docs.twig /var/www/cp/resources/views/admin/support/docs.custom.twig. Edit docs.custom.twig as needed. The system will use docs.custom.twig if it exists; otherwise, it defaults to docs.twig.

1.3.1.3. Customizing the Media Kit Page: To customize the media kit page, copy mediakit.twig to mediakit.custom.twig using cp /var/www/cp/resources/views/admin/support/mediakit.twig /var/www/cp/resources/views/admin/support/mediakit.custom.twig. Edit mediakit.custom.twig to apply your changes. The system will prioritize mediakit.custom.twig over the default file.

1.3.1.4. Customizing the Landing Page: To customize the landing page, copy index.twig to index.custom.twig using cp /var/www/cp/resources/views/index.twig /var/www/cp/resources/views/index.custom.twig. Edit index.custom.twig to apply your changes. The system will prioritize index.custom.twig over the default file.

1.3.2. Changing the Default Language

To change the default language of the control panel, you must edit the /var/www/cp/.env file and replace the language values (LANG/UI_LANG) with your desired settings.

For the LANG variable, the supported values are en_US, uk_UA, es_ES, pt_PT, jp_JP, ar_SA, and fr_FR. For the UI_LANG variable, use us, ua, es, pt, jp, ar, or fr.

To apply your changes, save the file, refresh the control panel, and clear the cache using the following command: php /var/www/cp/bin/clear_cache.php The new language settings will take effect immediately.

1.3.3. WebAuthn Authentication

To enable WebAuthn authentication in the Control Panel, follow these steps:

Edit the environment configuration file located at: /var/www/cp/.env
Find or add the following line:

WEB_AUTHN_ENABLED=true

Save the changes and reload the server (Caddy) using the following command:

sudo systemctl reload caddy

1.3.4. Password Policy Documentation

Default Password Strength

The default password strength requirement is 3.
Password strength is measured on a scale from 0 (weak) to 4 (strong).
To modify the required strength, update the .env file.

Example:

PASSWORD_STRENGTH=4

This will require stronger passwords.

Password Expiration

By default, passwords expire after 90 days.
Users will be required to reset their password after this period.
To change the expiration period, modify the .env file.

Example:

PASSWORD_EXPIRATION_DAYS=180

This will extend the password expiration to 180 days.

How to Apply Changes

Edit the .env file located at /var/www/cp/.env
Save the file and restart Caddy if necessary.

1.3.5. Setting Up Redis Session Storage

To utilize Redis for session storage, you need to install the necessary packages and configure your environment accordingly. Follow these steps to set up Redis session storage:

cd /var/www/cp
composer require pinga/session-redis

After installation, log out of your application if you are currently logged in. This ensures that the session starts afresh with the new configuration.

Clear your browser cookies related to the application. This step is crucial as it removes any existing session cookies that were set using the previous session storage mechanism.

Upon your next login, Redis will be used for storing session data. The new sessions will be created and managed through Redis, providing a more scalable and efficient session management system.

1.4. Setting Up the Automation System

Follow these steps to configure the automation system for your registry:

1.4.1. Configuration

Move to the automation directory with the following command:

cd /opt/registry/automation

Open config.php and adjust all necessary settings to suit your system's requirements. Make sure to review and fine-tune each option for optimal performance.

1.4.2. Configuring the Message Broker

You can easily configure the message broker for email delivery in config.php. It is compatible with SendGrid, Mailgun API, and PHPMailer for those opting to use their own SMTP server. All necessary settings are conveniently located under the mailer_ lines within the file.

For establishing your own mail server, both Mox and Stalwart offer comprehensive solutions. You can install Mox by following its GitHub instructions, or Stalwart by referring to its official site. Once installed, enter the required details in the config.php file to complete the setup.

To run the Message Broker, execute the following commands:

systemctl start msg_producer
systemctl start msg_worker

1.4.3. Setting Up an Audit Trail Database for Namingo

To create an audit trail database for Namingo, start by editing the configuration file located at /opt/registry/automation/audit.json with the correct database details. This includes specifying the database connection parameters such as host, username, and password. Once your configuration is set up, run the command:

/opt/registry/automation/vendor/bin/audit -v audit /opt/registry/automation/audit.json

This will initialize and configure the audit trail functionality. This process ensures that all necessary tables and structures are set up in the registryAudit database, enabling comprehensive auditing of Namingo's operations.

Currently, the audit trail setup for Namingo is supported only with MySQL or MariaDB databases. If you're using PostgreSQL, you'll need to utilize an external tool for audit logging, such as pgAudit, which provides detailed audit logging capabilities tailored for PostgreSQL environments.

1.4.4. Setup Backup

To set up backups in Namingo:

Rename /opt/registry/automation/backup.json.dist and /opt/registry/automation/backup-upload.json.dist to backup.json and backup-upload.json, respectively. Edit both files to include the correct database and other required details. If using SFTP and just username and password, make sure you check backup_upload.php for which values you need to set to null in backup-upload.json.
Enable the backup functionality in cron.php or cron_config.php and make sure you follow the instructions in section 1.4.9. Running the Automation System to activate the automation system on your server.

1.4.5. RDE (Registry data escrow) configuration

1.4.5.1. Generate the Key Pair: Create a configuration file, say key-config, with the following content:

%echo Generating a default key
Key-Type: RSA
Key-Length: 2048
Subkey-Type: RSA
Subkey-Length: 2048
Name-Real: Your Name
Name-Comment: Your Comment
Name-Email: your.email@example.com
Expire-Date: 0
%no-protection
%commit
%echo done

Replace "Your Name", "Your Comment", and "your.email@example.com" with your details.

Use the following command to generate the key:

gpg2 --batch --generate-key key-config

Your GPG key pair will now be generated.

1.4.5.2. Exporting Your Keys:

Public key:

gpg2 --armor --export your.email@example.com > publickey.asc

Replace your-email@example.com with the email address you used when generating the key.

Private key:

gpg2 --armor --export-secret-keys your.email@example.com > privatekey.asc

1.4.5.3. Secure Your Private Key: Always keep your private key secure. Do not share it. If someone gains access to your private key, they can impersonate you in cryptographic operations.

1.4.5.4. Use in RDE deposit generation: Please send the exported publickey.asc to your RDE provider, and also place the path to privatekey.asc in the escrow.php system as required.

1.4.6. Setting Up Exchange Rate Download

To enable exchange rate updates, follow these steps:

Edit config.php, modify the following settings and save the file.

return [
    // Exchange Rate Configuration
    'exchange_rate_api_key' => "", // Your exchangerate.host API key
    'exchange_rate_base_currency' => "USD", // Base currency
    'exchange_rate_currencies' => ["EUR", "GBP", "JPY", "CAD", "AUD"], // Target currencies
];

Enable Exchange Rate Generation

Ensure your cron.php or cron_config.php executes the exchange rate update script by setting exchange_rates to true.

If this is not enabled, you will need to manually edit /var/www/cp/resources/exchange_rates.json to provide exchange rates.

1.4.7. Zone generator custom records

Each TLD can have its own custom records file, located in /opt/registry/automation/. For example, for the TLD example, create the file /opt/registry/automation/example.php.

The content of a custom records file should be:

<?php
return [
    // A record
    [
        'name' => '@',          // The name of the record (e.g., @ for the root domain or a subdomain)
        'type' => 'A',          // Record type (A, AAAA, TXT, etc.)
        'parameters' => ['192.0.2.1'], // Parameters required for the record type
    ],
    // AAAA record
    [
        'name' => 'www',
        'type' => 'AAAA',
        'parameters' => ['2001:db8::1'],
    ],
    // TXT record
    [
        'name' => '@',
        'type' => 'TXT',
        'parameters' => ['"v=spf1 include:example.com ~all"'],
    ],
    // MX record
    [
        'name' => '@',
        'type' => 'MX',
        'parameters' => [10, 'mail.example.com.'], // Priority and mail server
    ],
];

1.4.8. Extra Scheduled Notification Scripts

In /opt/registry/tests/, you will find three notification scripts:

recent-domains.php: Notifies about all domains registered in the last week.
expiring-domains.php: Sends notifications for domains expiring in 30, 7, and 1 days.
balance-notify.php: Alerts registrars with low or zero balance.

Some registries may wish to use these scripts and run them automatically. Each script includes comments at the beginning that explain the recommended cron job schedule.

1.4.9. Running the Automation System

After successfully configuring all the components of the automation system as outlined in the previous sections, you can proceed to initiate the system.
Create the configuration file at /opt/registry/automation/cron_config.php with the specified structure, and adjust the values to suit your requirements. Note: If you are managing a gTLD, all services must be enabled for proper operation.

<?php
return [
    'accounting' => false,  // Enable or disable accounting
    'backup' => false,      // Enable or disable backup
    'backup_upload' => false, // Enable or disable backup upload
    'gtld_mode' => false,   // Enable or disable gTLD mode
    'spec11' => false,      // Enable or disable Spec 11 checks
    'exchange_rates' => false,     // Enable or disable exchange rate download
];

Add the following cron job to the system crontab using crontab -e:

* * * * * /usr/bin/php /opt/registry/automation/cron.php 1>> /dev/null 2>&1

1.5. SFTP Server Setup for ICANN

Install OpenSSH Server

apt update && apt install openssh-server

Configure SSH for SFTP

Edit SSH config:

nano /etc/ssh/sshd_config

Add at the end:

Subsystem sftp internal-sftp

Match Address 192.0.47.240,192.0.32.241,2620:0:2830:241::c613,2620:0:2d0:241::c6a5
    PasswordAuthentication no
    PermitRootLogin no

Match User sftpuser
    ChrootDirectory /home/sftpuser
    ForceCommand internal-sftp
    AllowTcpForwarding no
    X11Forwarding no

Restart SSH:

systemctl restart ssh

Create SFTP User

groupadd sftp_users
useradd -m -G sftp_users -s /usr/sbin/nologin sftpuser

Set Directory Permissions

chown root:root /home/sftpuser
chmod 755 /home/sftpuser
mkdir -p /home/sftpuser/files
chown sftpuser:sftp_users /home/sftpuser/files
chmod 700 /home/sftpuser/files

Whitelist ICANN IPs in UFW

ufw allow OpenSSH
ufw allow from 192.0.47.240 to any port 22
ufw allow from 192.0.32.241 to any port 22
ufw allow from 2620:0:2830:241::c613 to any port 22
ufw allow from 2620:0:2d0:241::c6a5 to any port 22
ufw enable

Generate and Add SSH Key for ICANN

ssh-keygen -t rsa -b 2048 -f icann_sftp_key -C "icann_sftp"

mkdir /home/sftpuser/.ssh
chmod 700 /home/sftpuser/.ssh
nano /home/sftpuser/.ssh/authorized_keys

Paste icann_sftp_key.pub, then set permissions:

sudo chmod 600 /home/sftpuser/.ssh/authorized_keys
sudo chown -R sftpuser:sftp_users /home/sftpuser/.ssh

Update DNS for sftp.namingo.org

Create an A record pointing sftp.namingo.org → <your-server-ip>.

Send ICANN the Following

SFTP Host: sftp://sftp.namingo.org
Port: 22
Username: sftpuser
Public Key: icann_sftp_key.pub
File Path: /files

Test SFTP Access

sftp -i icann_sftp_key sftpuser@sftp.namingo.org

2. DNS Server Setup

2.1. Hidden Master DNS with BIND

2.1.1. Install BIND9 and its utilities:

apt install bind9 bind9-utils bind9-doc

2.1.2. Generate a TSIG key:

Generate a TSIG key which will be used to authenticate DNS updates between the master and slave servers. Note: replace test with your TLD.

cd /etc/bind
tsig-keygen -a HMAC-SHA256 test.key

The output will be in the format that can be directly included in your BIND configuration files. It looks something like this:

key "test.key" {
    algorithm hmac-sha256;
    secret "base64-encoded-secret==";
};

Copy this output for use in the configuration files of both the master and slave DNS servers. (/etc/bind/named.conf.local)

2.1.3. Named Configuration - Please Choose One:

2.1.3a. Unsigned zone (No DNSSEC):

Edit the named.conf.local file:

nano /etc/bind/named.conf.local

Add the following zone definition:

zone "test." {
    type master;
    file "/var/lib/bind/test.zone";
    allow-transfer { key "test.key"; };
    also-notify { <slave-server-IP>; };
};

Replace <slave-server-IP> with the actual IP address of your slave server. Replace test with your TLD.

Use rndc to reload BIND:

systemctl restart bind9

Configure the Zone Writer in Registry Automation and run it manually the first time.

php /opt/registry/automation/write-zone.php

2.1.3b. Signed zone (With DNSSEC):

Edit the named.conf.local file:

nano /etc/bind/named.conf.local

Add the following DNSSEC policy:

dnssec-policy "namingo-policy" {
    keys {
        ksk lifetime P1Y algorithm ed25519;
        zsk lifetime P2M algorithm ed25519;
    };
    max-zone-ttl 86400;
    dnskey-ttl 3600;
    zone-propagation-delay 3600;
    parent-propagation-delay 7200;
    parent-ds-ttl 86400;
};

Then, add the zone definition:

zone "test." {
    type master;
    file "/var/lib/bind/test.zone";
    dnssec-policy "namingo-policy";
    key-directory "/var/lib/bind";
    inline-signing yes;
    allow-transfer { key "test.key"; };
    also-notify { <slave-server-IP>; };
};

Replace <slave-server-IP> with the actual IP address of your slave server. Replace test with your TLD.

Finally, set correct permissions and restart BIND9 to apply changes:

chown -R bind:bind /var/lib/bind
systemctl restart bind9

Configure the Zone Writer in Registry Automation and run it manually the first time.

php /opt/registry/automation/write-zone.php

NB! Enable DNSSEC in the TLD management page from the control panel. Mode must be BIND9. Then upload the DS record to IANA or the parent registry from the Control Panel TLD page.

**Optional: Configure BIND with PKCS#11 support

apt install softhsm2 opensc libengine-pkcs11-openssl

Edit /etc/bind/named.conf.options and add the following:

options {
    // Existing options...
    dnssec-policy "hsm-policy";
};

dnssec-policy "hsm-policy" {
    keys {
        ksk key-directory "pkcs11:token=YourTokenLabel" lifetime P1Y algorithm ecdsap256sha256;
        zsk key-directory "pkcs11:token=YourTokenLabel" lifetime P2M algorithm ecdsap256sha256;
    };
    max-zone-ttl 86400;
    dnskey-ttl 3600;
    zone-propagation-delay 3600;
    parent-propagation-delay 7200;
    parent-ds-ttl 86400;
};

Replace YourTokenLabel with your actual HSM token label.

BIND will automatically generate keys within the device when configured correctly:

rndc loadkeys your.tld

You can verify the keys with tools provided by your HSM vendor or via standard PKCS#11 utilities:

softhsm2-util --show-slots

2.1.3c. Signed zone (DNSSEC with OpenDNSSEC):

Using DNSSEC with :

Edit the named.conf.local file:

nano /etc/bind/named.conf.local

Add the following zone definition:

zone "test." {
    type master;
    file "/var/lib/bind/test.zone.signed";
    allow-transfer { key "test.key"; };
    also-notify { <slave-server-IP>; };
};

Replace <slave-server-IP> with the actual IP address of your slave server. Replace test with your TLD.

Install OpenDNSSEC:

apt install opendnssec opendnssec-enforcer-sqlite3 opendnssec-signer softhsm2
mkdir -p /var/lib/softhsm/tokens
chown -R opendnssec:opendnssec /var/lib/softhsm/tokens
softhsm2-util --init-token --slot 0 --label OpenDNSSEC --pin 1234 --so-pin 1234

Update files in /etc/opendnssec to match your registry policy. As minimum, please enable at least Signer Threads in /etc/opendnssec/conf.xml, but we recommend to fully review all the files. Then run the following commands:

chown -R opendnssec:opendnssec /etc/opendnssec
ods-enforcer-db-setup
ods-enforcer policy import
rm /etc/opendnssec/prevent-startup
chown opendnssec:opendnssec /var/lib/bind/test.zone
chmod 644 /var/lib/bind/test.zone
ods-enforcer zone add -z test -p default -i /var/lib/bind/test.zone
ods-control start

Edit again the named.conf.local file:

nano /etc/bind/named.conf.local

Replace the value for file with the following filename:

...
    file "/var/lib/opendnssec/signed/test.zone.signed";
...
};

Use rndc to reload BIND:

systemctl restart bind9

Configure the Zone Writer in Registry Automation and run it manually the first time.

php /opt/registry/automation/write-zone.php

2.1.4. Logging:

Place the contents below at /etc/bind/named.conf.default-logging and include the file in /etc/bind/named.conf:

logging {
    // General logs (startup, shutdown, errors)
    channel "misc" {
        file "/var/log/named/misc.log" versions 10 size 10m;
        print-time YES;
        print-severity YES;
        print-category YES;
    };

    // Query logs (log every DNS query)
    channel "query" {
        file "/var/log/named/query.log" versions 20 size 5m;
        print-time YES;
        print-severity NO;
        print-category NO;
    };

    // Lame server logs (misconfigured DNS servers)
    channel "lame" {
        file "/var/log/named/lamers.log" versions 3 size 5m;
        print-time YES;
        print-severity YES;
        severity info;
    };

    // Security logs (e.g., unauthorized query attempts)
    channel "security" {
        file "/var/log/named/security.log" versions 5 size 10m;
        print-time YES;
        print-severity YES;
        severity dynamic;
    };

    // DNS updates (useful for dynamic zones)
    channel "update" {
        file "/var/log/named/update.log" versions 3 size 5m;
        print-time YES;
        print-severity YES;
    };

    // Resolver logs (useful for debugging recursive queries)
    channel "resolver" {
        file "/var/log/named/resolver.log" versions 5 size 5m;
        print-time YES;
        print-severity YES;
    };

    // Zone transfer logs (incoming & outgoing transfers)
    channel "xfer" {
        file "/var/log/named/xfer.log" versions 5 size 5m;
        print-time YES;
        print-severity YES;
    };

    // Assign categories to log files
    category "default" { "misc"; };
    category "queries" { "query"; };
    category "lame-servers" { "lame"; };
    category "security" { "security"; };
    category "update" { "update"; };
    category "resolver" { "resolver"; };
    category "xfer-in" { "xfer"; };
    category "xfer-out" { "xfer"; };
};

2.1.5. Check BIND9 Configuration:

named-checkconf
named-checkzone test /var/lib/bind/test.zone

2.1.6. Restart BIND9 Service:

systemctl restart bind9

2.1.7. Verify Zone Loading:

Check the BIND9 logs to ensure that the .test zone is loaded without errors:

grep named /var/log/syslog

2.2. Hidden Master DNS with Knot DNS and DNSSEC

2.2.1. Install Knot DNS and its utilities:

apt install knot knot-dnsutils

2.2.2. Generate a TSIG key:

Generate a TSIG key which will be used to authenticate DNS updates between the master and slave servers. Note: replace test with your TLD.

cd /etc/knot
knotc conf-gen-key test.key hmac-sha256

The output will be in the format that can be directly included in your configuration files. It looks something like this:

key:
  - id: "test.key"
    algorithm: hmac-sha256
    secret: "base64-encoded-secret=="

Copy this output for use in the configuration files of both the master and slave DNS servers. (/etc/knot/knot.conf)

2.2.3. Configure DNSSEC Policy:

Add the DNSSEC policy to /etc/knot/knot.conf:

nano /etc/knot/knot.conf

Add the following DNSSEC policy:

policy:
  - id: "namingo-policy"
    description: "Default DNSSEC policy for TLD"
    algorithm: ed25519
    ksk-lifetime: 1y
    zsk-lifetime: 2m
    max-zone-ttl: 86400
    rrsig-lifetime: 14d
    rrsig-refresh: 7d
    dnskey-ttl: 3600

2.2.4. Add your zone:

Add the zone to /etc/knot/knot.conf:

zone:
  - domain: "test."
    file: "/etc/knot/zones/test.zone"
    dnssec-policy: "namingo-policy"
    key-directory: "/etc/knot/keys"
    storage: "/etc/knot/zones"
    notify: <slave-server-IP>
    acl:
      - id: "test.key"
        address: <slave-server-IP>
        key: "test.key"

Replace <slave-server-IP> with the actual IP address of your slave server. Replace test with your TLD.

Generate the necessary DNSSEC keys for your zone using keymgr:

keymgr policy:generate test.

This will create the required keys in /etc/knot/keys. Ensure the directory permissions are secure:

chown -R knot:knot /etc/knot/keys
chmod -R 700 /etc/knot/keys

Reload Knot DNS and enable DNSSEC signing for the zone:

knotc reload
knotc signzone test.

Generate the DS record for the parent zone using keymgr:

keymgr ds test.

Configure the Zone Writer in Registry Automation and run it manually the first time.

php /opt/registry/automation/write-zone.php

NB! Enable DNSSEC in the TLD management page from the control panel. Mode must be KnotDNS. Then upload the DS record to IANA or the parent registry from the Control Panel TLD page.

2.3. Regular DNS Server Setup

Before editing the configuration files, you need to copy the TSIG key from your hidden master server. The TSIG key configuration should look like this:

key "test.key" {
    algorithm hmac-sha256;
    secret "base64-encoded-secret==";
};

2.3.1. Installation of BIND9

apt update
apt install bind9 bind9-utils bind9-doc

2.3.2. Add the TSIG key to the BIND Configuration

Create a directory to store zone files:

mkdir /var/cache/bind/zones

Edit the named.conf.local file:

nano /etc/bind/named.conf.local

First, define the TSIG key at the top of the file:

key "test.key" {
    algorithm hmac-sha256;
    secret "base64-encoded-secret=="; // Replace with your actual base64-encoded key
};

Then, add the slave zone configuration:

zone "test." {
    type slave;
    file "/var/cache/bind/zones/test.zone";
    masters { 192.0.2.1 key "test.key"; }; // IP of the hidden master and TSIG key reference
    allow-query { any; }; // Allow queries from all IPs
    allow-transfer { none; }; // Disable zone transfers (AXFR) to others
};

Make sure to replace 192.0.2.1 with the IP address of your hidden master server and base64-encoded-secret== with the actual secret from your TSIG key.

2.3.3. Adjusting Permissions and Ownership

Ensure BIND has permission to write to the zone file and that the files are owned by the BIND user:

chown bind:bind /var/cache/bind/zones
chmod 755 /var/cache/bind/zones

2.3.4. Logging:

Place the contents below at /etc/bind/named.conf.default-logging and include the file in /etc/bind/named.conf:

logging {
    // General logs (startup, shutdown, errors)
    channel "misc" {
        file "/var/log/named/misc.log" versions 10 size 10m;
        print-time YES;
        print-severity YES;
        print-category YES;
    };

    // Query logs (log every DNS query)
    channel "query" {
        file "/var/log/named/query.log" versions 20 size 5m;
        print-time YES;
        print-severity NO;
        print-category NO;
    };

    // Lame server logs (misconfigured DNS servers)
    channel "lame" {
        file "/var/log/named/lamers.log" versions 3 size 5m;
        print-time YES;
        print-severity YES;
        severity info;
    };

    // Security logs (e.g., unauthorized query attempts)
    channel "security" {
        file "/var/log/named/security.log" versions 5 size 10m;
        print-time YES;
        print-severity YES;
        severity dynamic;
    };

    // DNS updates (useful for dynamic zones)
    channel "update" {
        file "/var/log/named/update.log" versions 3 size 5m;
        print-time YES;
        print-severity YES;
    };

    // Resolver logs (useful for debugging recursive queries)
    channel "resolver" {
        file "/var/log/named/resolver.log" versions 5 size 5m;
        print-time YES;
        print-severity YES;
    };

    // Zone transfer logs (incoming & outgoing transfers)
    channel "xfer" {
        file "/var/log/named/xfer.log" versions 5 size 5m;
        print-time YES;
        print-severity YES;
    };

    // Assign categories to log files
    category "default" { "misc"; };
    category "queries" { "query"; };
    category "lame-servers" { "lame"; };
    category "security" { "security"; };
    category "update" { "update"; };
    category "resolver" { "resolver"; };
    category "xfer-in" { "xfer"; };
    category "xfer-out" { "xfer"; };
};

2.3.5. Restart BIND9 Service

After making these changes, restart the BIND9 service to apply them:

systemctl restart bind9

2.3.6. Verify Configuration and Zone Transfer

named-checkconf
grep 'transfer of "test."' /var/log/syslog

3. Recommended Components and Integrations

This section outlines recommended components to enhance the functionality and reliability of your Namingo setup.

3.1. Setup Monitoring

3.1.1. Option 1: Prometheus

apt update
apt install prometheus prometheus-node-exporter prometheus-mysqld-exporter prometheus-blackbox-exporter prometheus-redis-exporter

Edit the Prometheus configuration file: /etc/prometheus/prometheus.yml and replace the rule_files: and scrape_configs: sections with with the following, while editing the hostnames with your own:

rule_files:
  - "/etc/prometheus/alert.rules"

scrape_configs:
  - job_name: 'prometheus'
    static_configs:
      - targets: ['localhost:9090']

  - job_name: 'node'
    static_configs:
      - targets: ['localhost:9100']

  - job_name: 'mariadb'
    metrics_path: /metrics
    static_configs:
      - targets: ['localhost:9104']

  - job_name: 'epp_server'
    metrics_path: /probe
    params:
      module: [tcp_connect]
    static_configs:
      - targets: ['epp.namingo.org:700']
    relabel_configs:
      - source_labels: [__address__]
        target_label: __param_target
      - source_labels: [__param_target]
        target_label: instance
      - target_label: __address__
        replacement: localhost:9115  # Blackbox Exporter

  - job_name: 'whois_server'
    metrics_path: /probe
    params:
      module: [tcp_connect]
    static_configs:
      - targets: ['whois.namingo.org:43']
    relabel_configs:
      - source_labels: [__address__]
        target_label: __param_target
      - source_labels: [__param_target]
        target_label: instance
      - target_label: __address__
        replacement: localhost:9115  # Blackbox Exporter

  - job_name: 'das_server'
    metrics_path: /probe
    params:
      module: [tcp_connect]
    static_configs:
      - targets: ['das.namingo.org:1043']
    relabel_configs:
      - source_labels: [__address__]
        target_label: __param_target
      - source_labels: [__param_target]
        target_label: instance
      - target_label: __address__
        replacement: localhost:9115  # Blackbox Exporter

  - job_name: 'rdap_server'
    metrics_path: /probe
    params:
      module: [tcp_connect]
    static_configs:
      - targets: ['localhost:7500']
    relabel_configs:
      - source_labels: [__address__]
        target_label: __param_target
      - source_labels: [__param_target]
        target_label: instance
      - target_label: __address__
        replacement: localhost:9115  # Blackbox Exporter

  - job_name: 'control_panel'
    static_configs:
      - targets: ['localhost:2019']
      
  - job_name: 'redis'
    static_configs:
      - targets: ['localhost:9121']

Set ownership for the configuration file:

chown prometheus:prometheus /etc/prometheus/prometheus.yml

Review the Node Exporter service file:

nano /lib/systemd/system/prometheus-node-exporter.service

Edit the MySQL Exporter configuration, modify the ExecStart line to explicitly use the MariaDB config file:

nano /lib/systemd/system/prometheus-mysqld-exporter.service

ExecStart=/usr/bin/prometheus-mysqld-exporter --config.my-cnf=/etc/mysql/exporter.cnf --web.listen-address=:9104
Restart=always

Create the MySQL user:

CREATE USER 'exporter'@'localhost' IDENTIFIED BY 'yourpassword';
GRANT PROCESS, REPLICATION CLIENT, SELECT ON *.* TO 'exporter'@'localhost';
FLUSH PRIVILEGES;

Create a MariaDB config file:

nano /etc/mysql/exporter.cnf

Add the following content (replace yourpassword with your real password):

[client]
user=exporter
password=yourpassword
host=localhost

To prevent other users from reading the credentials:

chmod 600 /etc/mysql/exporter.cnf
chown prometheus:prometheus /etc/mysql/exporter.cnf

Add the following on top of the /etc/caddy/Caddyfile file, before any other blocks:

{
    servers {
        metrics
    }
}

Create alerts for all services:

nano /etc/prometheus/alert.rules

Paste the following:

groups:
  - name: all_services
    rules:

      # Alert if Prometheus itself is down
      - alert: PrometheusDown
        expr: up{job="prometheus"} == 0
        for: 1m
        labels:
          severity: critical
        annotations:
          summary: "Prometheus is down"
          description: "Prometheus instance on port 9090 is unreachable for 1 minute."

      # Alert if Node Exporter (System Metrics) is down
      - alert: NodeExporterDown
        expr: up{job="node"} == 0
        for: 1m
        labels:
          severity: critical
        annotations:
          summary: "Node Exporter is down"
          description: "The system monitoring agent on port 9100 is unreachable for 1 minute."

      # Alert if MariaDB Exporter is down
      - alert: MariaDBDown
        expr: up{job="mariadb"} == 0
        for: 1m
        labels:
          severity: critical
        annotations:
          summary: "MariaDB is down"
          description: "The MariaDB exporter on port 9104 is unreachable for 1 minute."

      # Alert if EPP Server is down
      - alert: EPPServerDown
        expr: probe_success{job="epp_server"} == 0
        for: 1m
        labels:
          severity: critical
        annotations:
          summary: "EPP Server is down"
          description: "The EPP server on port 700 is unreachable for 1 minute."

      # Alert if WHOIS Server is down
      - alert: WhoisServerDown
        expr: probe_success{job="whois_server"} == 0
        for: 1m
        labels:
          severity: warning
        annotations:
          summary: "WHOIS Server is down"
          description: "The WHOIS server on port 43 is unreachable for 1 minute."

      # Alert if DAS Server is down
      - alert: DASSserverDown
        expr: probe_success{job="das_server"} == 0
        for: 1m
        labels:
          severity: warning
        annotations:
          summary: "DAS Server is down"
          description: "The DAS server on port 1043 is unreachable for 1 minute."

      # Alert if RDAP Server is down
      - alert: RDAPServerDown
        expr: probe_success{job="rdap_server"} == 0
        for: 1m
        labels:
          severity: critical
        annotations:
          summary: "RDAP Server is down"
          description: "The RDAP server on port 7500 is unreachable for 1 minute."

      # Alert if Control Panel is down
      - alert: ControlPanelDown
        expr: up{job="control_panel"} == 0
        for: 1m
        labels:
          severity: critical
        annotations:
          summary: "Control Panel is down"
          description: "The Caddy control panel monitoring endpoint is unreachable for 1 minute."

      # Alert if Redis Exporter is down
      - alert: RedisDown
        expr: up{job="redis"} == 0
        for: 1m
        labels:
          severity: critical
        annotations:
          summary: "Redis is down"
          description: "Redis exporter on port 9121 is unreachable for 1 minute."

Enable and start all services:

systemctl restart caddy
systemctl daemon-reload

systemctl enable prometheus-node-exporter
systemctl start prometheus-node-exporter

systemctl enable prometheus-mysqld-exporter
systemctl start prometheus-mysqld-exporter

systemctl enable prometheus-blackbox-exporter
systemctl start prometheus-blackbox-exporter

systemctl enable prometheus-redis-exporter
systemctl start prometheus-redis-exporter

systemctl enable prometheus
systemctl start prometheus

Open Prometheus in your browser: http://your-server-ip:9090

Check Status > Targets to ensure all targets are up.

Optional: Install Grafana

apt-get install -y adduser libfontconfig1 musl
wget https://dl.grafana.com/oss/release/grafana_11.5.1_amd64.deb
dpkg -i grafana_11.5.1_amd64.deb
systemctl daemon-reload
systemctl enable grafana-server
systemctl start grafana-server

Open Grafana in your browser: http://your-server-ip:3000

Add Prometheus as a Data Source

Click Configuration (gear icon) → Data Sources → Add Data Source.
Select Prometheus.
Set URL to: http://localhost:9090
Click Save & Test. It should return "Data source is working".

Import Ready-Made Dashboards

Go to Grafana UI → Dashboards → Import.
Paste the Dashboard ID from Grafana.com, for example:

Prometheus Node Exporter Full: 1860
Redis Exporter: 763
MySQL/MariaDB: 7362
Blackbox Exporter (TCP Probes for EPP, WHOIS, DAS, RDAP): 7587 or 13659
Prometheus Self-Monitoring: 3662
Caddy Web Server Monitoring: 13460

Click Load, select Prometheus as the data source, and click Import.

Set Up Alerts in Grafana

If you want notifications via email, Slack, Telegram, or other tools, you can configure Alerting in Grafana.

Go to "Alerting" → "Contact Points" → "Add Contact Point".
Choose a notification method (Slack, email, etc.).
Create alert rules (e.g., "Alert if Redis is down for 1 minute").

3.1.2. Option 2: Netdata

wget https://my-netdata.io/kickstart.sh -O install.sh && chmod +x install.sh && ./install.sh

Open Netdata in your browser: http://your-server-ip:19999

3.2. Recommended Help Desk Solutions

To enhance your customer support experience with Namingo, consider using one of these open-source help desk solutions:

Solution	License	Key Features
FreeScout	AGPL-3.0	Lightweight, email-based help desk with ticketing and multi-channel support.
Chatwoot	MIT	Omnichannel support platform for email, WhatsApp, social media, and live chat.

Note: These solutions are independent of Namingo. FreeScout is licensed under AGPL-3.0, while Chatwoot uses MIT. If using FreeScout, ensure compliance with AGPL-3.0 licensing.

3.3. Scaling Your Database with ProxySQL

To enhance the scalability and performance of your database, consider integrating ProxySQL into your architecture. ProxySQL is a high-performance, open-source proxy designed for MySQL, MariaDB, and other database systems, providing features like query caching, load balancing, query routing, and failover support. By acting as an intermediary between your application and the database, ProxySQL enables efficient distribution of queries across multiple database nodes, reducing latency and improving overall reliability, making it an excellent choice for scaling your database infrastructure.

4. Security Hardening

4.1. Create the namingo user

adduser namingo
usermod -aG sudo namingo

4.2. Set Up Services

su namingo
sudo nano /etc/systemd/system/{whois.service,epp.service,rdap.service}

Modify:

[Service]
User=namingo
Group=namingo

Reload and restart:

sudo chown -R namingo:namingo /opt/registry /etc/caddy
sudo systemctl daemon-reload
sudo systemctl restart whois epp rdap

4.3. SSH Hardening

Disable Root Login:

sudo nano /etc/ssh/sshd_config

Set:

PermitRootLogin no

Change SSH Port:

Port 2222

Use Key-Based Authentication:

Generate a key pair:

ssh-keygen -t rsa -b 4096

Add your public key to the namingo user:

su - namingo
mkdir -p ~/.ssh
chmod 700 ~/.ssh
echo "your-public-key" > ~/.ssh/authorized_keys
chmod 600 ~/.ssh/authorized_keys

Firewall Setup:

sudo ufw allow 2222/tcp       # New SSH Port
sudo ufw enable

Restart SSH:

sudo systemctl restart ssh

4.4. Other Server Hardening

sudo apt update && sudo apt upgrade -y
sudo systemctl list-units --type=service --state=running
sudo systemctl disable <service> # Disable unnecessary ones
sudo apt install fail2ban
sudo systemctl enable fail2ban --now
sudo apt install unattended-upgrades
sudo dpkg-reconfigure --priority=low unattended-upgrades

Configure Swap (if necessary):

sudo fallocate -l 1G /swapfile
sudo chmod 600 /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile
echo '/swapfile none swap sw 0 0' | sudo tee -a /etc/fstab

4.5. Adminer Security settings

To enhance the security of your Adminer installation, we recommend the following settings for Caddy, Apache2, and Nginx:

Rename Adminer File: Change adminer.php to dbtool.php to make it less predictable.
Restrict Access by IP: Only allow access from specific IP addresses.

Below are example configurations for each web server:

Caddy

# Adminer Configuration
route /dbtool.php* {
    root * /usr/share/adminer
    php_fastcgi unix//run/php/php8.2-fpm.sock

    # Define the allowed IP address
    @allowed {
        remote_ip your.ip.address.here
    }

    # Route for allowed IP addresses
    handle @allowed {
        file_server
    }

    # Respond with 403 for any IP address not allowed
    respond "Access Denied" 403
}

Apache .htaccess

<Files "dbtool.php">
    Order Deny,Allow
    Deny from all
    Allow from your.ip.address.here
</Files>

Nginx

location /dbtool.php {
    allow your.ip.address.here;
    deny all;
}

5. In-Depth Configuration File Overview

In this section, we provide a detailed overview of each configuration file used in the Namingo domain registry platform. Understanding these files is essential for customizing and optimizing your system according to your specific needs. We will walk you through the purpose of each file, key settings, and recommended configurations to ensure smooth operation and integration with other components of your setup.

Automation Configuration (`/opt/registry/automation/config.php`)

This configuration file is essential for setting up the automation scripts for the registry tool.

<?php

return [
    // Database Configuration
    'db_type' => 'mysql', // Type of the database (e.g., 'mysql', 'pgsql')
    'db_host' => 'localhost', // Database server host
    'db_port' => 3306, // Database server port
    'db_database' => 'registry', // Name of the database
    'db_username' => 'your_username', // Database username
    'db_password' => 'your_password', // Database password
    
    // Escrow Configuration
    'escrow_deposit_path' => '/opt/escrow', // Path for escrow deposits
    'escrow_deleteXML' => false, // Whether to delete XML files after processing
    'escrow_RDEupload' => false, // Enable/disable RDE upload
    'escrow_BRDAupload' => false, // Enable/disable BRDA upload
    'escrow_BRDAday' => 'Tuesday', // Day for BRDA uploads
    'escrow_keyPath' => '/opt/escrow/escrowKey.asc', // Path to the escrow key
    'escrow_keyPath_brda' => '/opt/escrow/icann-brda-gpg.pub', // Path to the BRDA escrow key
    'escrow_privateKey' => '/opt/escrow/privatekey.asc', // Path to the private key for escrow
    'escrow_sftp_host' => 'your.sftp.server.com', // Host for escrow SFTP server
    'escrow_sftp_username' => 'your_username', // Username for escrow SFTP server
    'escrow_sftp_password' => 'your_password', // Password for escrow SFTP server
    'escrow_sftp_remotepath' => '/path/on/sftp/server/', // Remote path on the escrow SFTP server
    'brda_sftp_host' => 'your.sftp.server.com', // Host for BRDA SFTP server
    'brda_sftp_username' => 'your_username', // Username for BRDA SFTP server
    'brda_sftp_password' => 'your_password', // Password for BRDA SFTP server
    'brda_sftp_remotepath' => '/path/on/sftp/server/', // Remote path on the BRDA SFTP server
    'escrow_report_url' => 'https://ry-api.icann.org/report/', // URL for escrow reporting
    'escrow_report_username' => 'your_username', // Username for escrow reporting
    'escrow_report_password' => 'your_password', // Password for escrow reporting
    'roid' => 'XX', // ROID value in escrow

    // Reporting Configuration
    'reporting_path' => '/opt/reporting', // Path for reporting
    'reporting_upload' => false, // Enable/disable reporting upload
    'reporting_username' => 'your_username', // Username for reporting
    'reporting_password' => 'your_password', // Password for reporting
    
    // Zone Writer Configuration
    'dns_server' => 'bind', // DNS server type (e.g., 'bind', 'nsd')
    'ns' => [
        'ns1' => 'ns1.namingo.org', // Primary name server
        'ns2' => 'ns2.namingo.org', // Secondary name server
        // ... more name servers as needed ...
    ],
    'dns_soa' => 'hostmaster.example.com', // SOA email address
    'dns_serial' => 1, // change to 2 for YYYYMMDDXX format, and 3 for Cloudflare-like serial
    'zone_mode' => 'default', // How the BIND zone is generated, 'nice' is also available

    // URS Configuration
    'urs_imap_host' => '{your_imap_server:993/imap/ssl}INBOX', // IMAP host for URS
    'urs_imap_username' => 'your_username', // IMAP username for URS
    'urs_imap_password' => 'your_password', // IMAP password for URS
    
    // Message Broker Configuration
    'mailer' => 'phpmailer', // Mailer type ('phpmailer', 'sendgrid', 'mailgun')
    'mailer_api_key' => 'YOUR_API_KEY', // API key for sendgrid/mailgun
    'mailer_domain' => 'example.com', // Domain for sendgrid/mailgun
    'mailer_from' => 'from@example.com', // From email address for mailer
    'mailer_smtp_host' => 'smtp.example.com', // SMTP host for mailer
    'mailer_smtp_username' => 'your_email@example.com', // SMTP username for mailer
    'mailer_smtp_password' => 'your_password', // SMTP password for mailer
    'mailer_smtp_port' => 587, // SMTP port for mailer
    
    'mailer_sms' => 'twilio', // SMS provider ('twilio', 'telesign', 'plivo', 'vonage', 'clickatell')
    'mailer_sms_account' => 'YOUR_ACCOUNT_SID/USERNAME', // Account SID/username for SMS
    'mailer_sms_auth' => 'YOUR_AUTH_TOKEN/PASSWORD', // Auth token/password for SMS
    
    // TMCH Configuration
    'tmch_path' => '/tmp/', // Path for TMCH files
    'tmch_smdrl_user' => 'your_username', // Username for TMCH SMDRL
    'tmch_smdrl_pass' => 'your_password', // Password for TMCH SMDRL
    'tmch_dnl_user' => 'your_username', // Username for TMCH DNL
    'tmch_dnl_pass' => 'your_password', // Password for TMCH DNL
    
    // LORDN Configuration
    'lordn_user' => 'your_username', // Username for LORDN
    'lordn_pass' => 'your_password', // Password for LORDN
    
    // Minimum Data Set
    'minimum_data' => false,

    // Domain lifecycle settings
    'autoRenewEnabled' => false,

    // Lifecycle periods (in days)
    'gracePeriodDays' => 30,
    'autoRenewPeriodDays' => 45,
    'addPeriodDays' => 5,
    'renewPeriodDays' => 5,
    'transferPeriodDays' => 5,
    'redemptionPeriodDays' => 30,
    'pendingDeletePeriodDays' => 5,

    // Lifecycle phases (enable/disable)
    'enableAutoRenew' => false,
    'enableGracePeriod' => true,
    'enableRedemptionPeriod' => true,
    'enablePendingDelete' => true,

    // Drop settings
    'dropStrategy' => 'random', // Options: 'fixed', 'random'
    'dropTime' => '02:00:00',    // Time of day to perform drops if 'fixed' strategy is used
    
    // IANA Email for Submission Logs
    'iana_email' => 'admin@example.com', // Email address to be used for IANA submission

    // Registry Admin Email
    'admin_email' => 'admin@example.com', // Receives system notifications

    // Exchange Rate Configuration
    'exchange_rate_api_key' => "", // Your exchangerate.host API key
    'exchange_rate_base_currency' => "USD",
    'exchange_rate_currencies' => ["EUR", "GBP", "JPY", "CAD", "AUD"], // Configurable list
];

Control Panel Configuration (`/var/www/cp/.env`)

This file configures the environment for the control panel of Namingo.

APP_NAME='CP'
APP_ENV=public
APP_URL=https://cp.example.com
APP_DOMAIN=example.com
APP_ROOT=/var/www/cp
MINIMUM_DATA=false

LANG=en_US
UI_LANG=us

DB_DRIVER=mysql # Type of the database (e.g., 'mysql', 'pgsql')
DB_HOST=localhost # Database server host
DB_DATABASE=registry # Name of the database
DB_USERNAME=root # Database username
DB_PASSWORD= # Database password
DB_PORT=3306 # Database server port

# Mailer settings (Driver = smtp, utopia or msg [for local message broker]; Api Provder = sendgrid or mailgun)
MAIL_DRIVER=smtp
MAIL_HOST=smtp.mailtrap.io
MAIL_PORT=2525
MAIL_USERNAME=username
MAIL_PASSWORD=password
MAIL_ENCRYPTION=tls
MAIL_FROM_ADDRESS='example@domain.com'
MAIL_FROM_NAME='Example'
MAIL_API_KEY='test-api-key'
MAIL_API_PROVIDER='sendgrid'

STRIPE_SECRET_KEY='stripe-secret-key'
STRIPE_PUBLISHABLE_KEY='stripe-publishable-key'

ADYEN_API_KEY='adyen-api-key'
ADYEN_MERCHANT_ID='adyen-merchant-id'
ADYEN_THEME_ID='adyen-theme-id'
ADYEN_BASE_URI='https://checkout-test.adyen.com/v70/'
ADYEN_BASIC_AUTH_USER='adyen-basic-auth-user'
ADYEN_BASIC_AUTH_PASS='adyen-basic-auth-pass'
ADYEN_HMAC_KEY='adyen-hmac-key'

NOW_API_KEY='now-api-key'

NICKY_API_KEY='nicky-api-key'

TEST_TLDS=.test,.com.test

DAS Server Configuration (`/opt/registry/das/config.php`)

Configurations for the Domain Availability Service (DAS) server.

<?php

return [
    'db_type' => 'mysql', // Type of the database (e.g., 'mysql', 'pgsql')
    'db_host' => 'localhost', // Database server host
    'db_port' => 3306, // Database server port
    'db_database' => 'registry', // Name of the database
    'db_username' => 'your_username', // Database username
    'db_password' => 'your_password' // Database password
    'das_ipv4' => '0.0.0.0',
    'das_ipv6' => '::', // Set to false if no IPv6 support
    'rately' => false, // Enable rate limit
    'limit' => 1000, // Request limit per period below
    'period' => 60, // 60 Seconds
];

EPP Server Configuration (`/opt/registry/epp/config.php`)

Settings for the Extensible Provisioning Protocol (EPP) server.

<?php

return [
    'db_type' => 'mysql', // Type of the database (e.g., 'mysql', 'pgsql')
    'db_host' => 'localhost', // Database server host
    'db_port' => 3306, // Database server port
    'db_database' => 'registry', // Name of the database
    'db_username' => 'your_username', // Database username
    'db_password' => 'your_password', // Database password
    'epp_host' => '0.0.0.0', // IP that the server will bind to, leave as is if no specific need
    'epp_port' => 700, // Port that the server will use
    'epp_pid' => '/var/run/epp.pid', // PID file of the server (do not change)
    'epp_greeting' => 'Namingo EPP Server 1.0', // EPP server prefix
    'epp_prefix' => 'namingo', // EPP server prefix
    'ssl_cert' => '', // Path to the SSL certificate that will be used by the server
    'ssl_key' => '', // Path to the SSL keyfile that will be used by the server
    'test_tlds' => '.test,.com.test', // Test TLDs for debugging purposes
    'rately' => false, // Enable rate limit
    'limit' => 1000, // Request limit per period below
    'period' => 60, // 60 Seconds
    'minimum_data' => false, // Set to true to enable minimum data set support
];

RDAP Server Configuration (`/opt/registry/rdap/config.php`)

Configuration for the Registration Data Access Protocol (RDAP) server.

<?php

return [
    'db_type' => 'mysql', // Type of the database (e.g., 'mysql', 'pgsql')
    'db_host' => 'localhost', // Database server host
    'db_port' => 3306, // Database server port
    'db_database' => 'registry', // Name of the database
    'db_username' => 'your_username', // Database username
    'db_password' => 'your_password', // Database password
    'roid' => 'XX', // Registry Object ID
    'minimum_data' => false, // Set to true to enable minimum data set support
    'registry_url' => 'https://example.com/rdap-terms', // URL of registry website
    'rdap_url' => 'https://rdap.example.com', // URL of RDAP server
    'rately' => false, // Enable rate limit
    'limit' => 1000, // Request limit per period below
    'period' => 60, // 60 Seconds
];

WHOIS Server Configuration (`/opt/registry/whois/port43/config.php`)

Settings for the WHOIS server running on port 43.

<?php

return [
    'db_type' => 'mysql', // Type of the database (e.g., 'mysql', 'pgsql')
    'db_host' => 'localhost', // Database server host
    'db_port' => 3306, // Database server port
    'db_database' => 'registry', // Name of the database
    'db_username' => 'your_username', // Database username
    'db_password' => 'your_password', // Database password
    'whois_ipv4' => '0.0.0.0',
    'whois_ipv6' => '::', // Set to false if no IPv6 support
    'privacy' => false, // Toggle for privacy mode
    'minimum_data' => false, // Set to true to enable minimum data set support
    'roid' => 'XX', // Registry Object ID
    'rately' => false, // Enable rate limit
    'limit' => 1000, // Request limit per period below
    'period' => 60, // 60 Seconds
];

In conclusion, this detailed configuration guide aims to streamline the setup process of the Namingo system for users of all expertise levels. The guide meticulously details each configuration file, providing clear explanations and guidance for customization to suit your specific needs. This approach ensures that you can configure Namingo with confidence, optimizing it for your registry management requirements. We are committed to making the configuration process as straightforward as possible, and we welcome any questions or requests for further assistance. Your successful deployment and efficient management of Namingo is our top priority.

After finalizing the configuration of Namingo, the next step is to consult the Initial Operation Guide. This guide provides comprehensive details on configuring your registry, adding registrars, and much more, to ensure a smooth start with your system.

54 KiB Raw Blame History

Configuration Guide

1. Post-Installation Configuration

1.1. Launching WHOIS, RDAP, and DAS Servers

1.2. Launching EPP Server

1.3. Optional Control Panel Configuration

1.3.1. Customizing the Logo and Pages

1.3.2. Changing the Default Language

1.3.3. WebAuthn Authentication

1.3.4. Password Policy Documentation

1.3.5. Setting Up Redis Session Storage

1.4. Setting Up the Automation System

1.4.1. Configuration

1.4.2. Configuring the Message Broker

1.4.3. Setting Up an Audit Trail Database for Namingo

1.4.4. Setup Backup

1.4.5. RDE (Registry data escrow) configuration

1.4.6. Setting Up Exchange Rate Download

1.4.7. Zone generator custom records

1.4.8. Extra Scheduled Notification Scripts

1.4.9. Running the Automation System

1.5. SFTP Server Setup for ICANN

2. DNS Server Setup

2.1. Hidden Master DNS with BIND

2.1.1. Install BIND9 and its utilities:

2.1.2. Generate a TSIG key:

2.1.3. Named Configuration - Please Choose One:

2.1.3a. Unsigned zone (No DNSSEC):

2.1.3b. Signed zone (With DNSSEC):

2.1.3c. Signed zone (DNSSEC with OpenDNSSEC):

2.1.4. Logging:

2.1.5. Check BIND9 Configuration:

2.1.6. Restart BIND9 Service:

2.1.7. Verify Zone Loading:

2.2. Hidden Master DNS with Knot DNS and DNSSEC

2.2.1. Install Knot DNS and its utilities:

2.2.2. Generate a TSIG key:

2.2.3. Configure DNSSEC Policy:

2.2.4. Add your zone:

2.3. Regular DNS Server Setup

2.3.1. Installation of BIND9

2.3.2. Add the TSIG key to the BIND Configuration

2.3.3. Adjusting Permissions and Ownership

2.3.4. Logging:

2.3.5. Restart BIND9 Service

2.3.6. Verify Configuration and Zone Transfer

3. Recommended Components and Integrations

3.1. Setup Monitoring

3.1.1. Option 1: Prometheus

3.1.2. Option 2: Netdata

3.2. Recommended Help Desk Solutions

3.3. Scaling Your Database with ProxySQL

4. Security Hardening

4.1. Create the namingo user

4.2. Set Up Services

4.3. SSH Hardening

4.4. Other Server Hardening

4.5. Adminer Security settings

Caddy

Apache .htaccess

Nginx

5. In-Depth Configuration File Overview

Automation Configuration (/opt/registry/automation/config.php)

Control Panel Configuration (/var/www/cp/.env)

DAS Server Configuration (/opt/registry/das/config.php)

EPP Server Configuration (/opt/registry/epp/config.php)

RDAP Server Configuration (/opt/registry/rdap/config.php)

WHOIS Server Configuration (/opt/registry/whois/port43/config.php)

54 KiB

Raw Blame History

Automation Configuration (`/opt/registry/automation/config.php`)

Control Panel Configuration (`/var/www/cp/.env`)

DAS Server Configuration (`/opt/registry/das/config.php`)

EPP Server Configuration (`/opt/registry/epp/config.php`)

RDAP Server Configuration (`/opt/registry/rdap/config.php`)

WHOIS Server Configuration (`/opt/registry/whois/port43/config.php`)