AWS Apache, PHP and Mysql

 A web server environment, installing Apache, PHP, MySQL, and configuring various settings and files for a specific application (lms01072024). Here's a simplified rundown of what you've done:


1. Setup Apache and PHP:

   - Installed Apache web server (`sudo apt install apache2`).

   - Installed PHP 8.0 and required modules (`sudo apt install php8.0 php8.0-mysqli`).

   - Enabled Apache and PHP modules (`sudo systemctl enable apache2`).

sudo mysql -u root -p lmsdb < /var/www/web/lms01072024/db/capstone.sql

2. Database Setup:

   - Installed MySQL server (`sudo apt install mysql-server`).

   - Secured MySQL installation (`sudo mysql_secure_installation`).

   - Created a MySQL user and imported a database (`mysql -u root -p lmsdb < /var/www/web/lms01072024/db/capstone.sql`).

   - php -m


3. Web Application Setup:

   - Cloned a Git repository (`git clone https://github.com/xxxxx/lms01072024.git`).

   - Modified configuration files, likely for Apache (`sudo nano /etc/apache2/sites-available/yoursite.conf`).


4. Maintenance and Troubleshooting:

   - Restarted or reloaded Apache (`systemctl reload apache2` or `systemctl restart apache2`).

   - Checked Apache error logs (`sudo tail -n 20 /var/log/apache2/error.log`).

   - Cleared Apache error  (sudo truncate -s 0 /var/log/apache2/error.log)

    -



5. Additional Configurations:

   - Created PHP information file (`sudo printf "<?php\nphpinfo();\n?>" > /var/www/web/lms01072024/phpinfo.php`).

 systemctl restart apache2

 systemctl reload apache2


This series of commands and actions essentially outlines the process of setting up a web server environment with Apache, PHP, and MySQL, co


nfiguring it for a specific web application, and performing maintenance and troubleshooting tasks along the way.

To create or manage a DNS SOA (Start of Authority) record with ClouDNS, follow these guidelines based on the information you've provided:

SOA Record Structure

1. Serial Number: 
   - This is a version number for the zone file, and it should be incremented each time the zone file is updated. This ensures that secondary DNS servers know to pull the latest version of the zone.
   - ClouDNS automatically increments this number with each change to your DNS zone.

2. Primary Name Server (NS):
   - This is the hostname of the primary DNS server for the zone.
   - Default: `ns11.cloudns.net`. 
   - If you enter an invalid primary name server, ClouDNS will revert it to `ns11.cloudns.net`.

3. DNS Admin Email:
   - This field contains the email address of the administrator responsible for managing the zone. 
   - The address is written with a dot instead of the "@" symbol (e.g., `support.cloudns.net` instead of `support@cloudns.net`).
   - Default: `support@cloudns.net`.

4. Refresh Rate:
   - The interval in seconds that a secondary DNS server waits before checking with the primary server for updates to the SOA record.
   - Range: 1200 to 43200 seconds.

5. Retry Rate:
   - The time in seconds that a secondary server waits after a failed attempt to refresh the zone file before trying again.
   - Default: 1800 seconds.
   - Range: 180 to 2419200 seconds.

6. Expire Time:
   - The period in seconds that a secondary server will keep attempting to complete a zone transfer before expiring its current zone file. 
   - Default: 1209600 seconds (14 days).

7. Default TTL (Time-to-Live):
   - This value is the minimum TTL applied to all resource records in the zone. It tells other servers how long to cache the data before re-querying.
   - Default: 3600 seconds (1 hour).

 Steps to Manage SOA Records on ClouDNS

1. Automatic Addition:
   - The SOA record is automatically added when you create a new DNS zone in ClouDNS.

2. Customizing SOA Record:
   - If you have a paid ClouDNS plan, you can adjust the SOA parameters:
     - Log in to your ClouDNS account.
     - Access your profile settings by clicking on your email link at the top of the page.
     - In the SOA settings panel, you can customize the values for the DNS admin email, Primary NS, Refresh rate, Retry rate, Expire time, and Default TTL.
     - Click the "Save" button to apply your changes.

3. Setting Default SOA Parameters:
   - For paid accounts, you can set default SOA parameters that will be automatically applied to any new zone you create. This can also be done from the profile settings.

4. Free User Limitation:
   - Free users on ClouDNS cannot manage SOA records manually; they are handled automatically by ClouDNS.

Example SOA Record with ClouDNS Default Values


example.com.    IN  SOA  ns11.cloudns.net.  support.cloudns.net. (
                  2024081501 ; Serial
                  43200      ; Refresh (12 hours)
                  1800       ; Retry (30 minutes)
                  1209600    ; Expire (14 days)
                  3600       ; Minimum TTL (1 hour)
                )


This structure will ensure proper DNS management and synchronization across servers. Adjust the parameters based on your specific needs to optimize DNS performance.

Post a Comment

0 Comments