Installation And Configuration Of DNS, Web And FTP Servers On Virtual Machines Using Ubuntu And CentOS

Installation And Configuration Of DNS, Web And FTP Servers On Virtual Machines Using Ubuntu And CentOS Part 1: Virtual Machine One – DNS & SSH Server The first Virtual Machine should be installed and have the BIND (DNS) server installed on it. While you do not own any address space/ name space your name server should manage the following domains: The name server should answer queries for this domain. In addition to the saffioti.org.au zone, a zone should be set up for the reverse zone – the reverse zone would be whatever the address range is of your virtual machine. You should do some research on how Bind handles reverse zones. For networking assignment help visit Myassignmenthelp.com Part 2: Virtual Machine Two The second Virtual Machine is to have the LAMP software package installed. LAMP is a standard bundle in the Ubuntu Server platform. Once complete set up this Virtual Machine to host a website using the Apache Web Server. The Virtual Machine should have a statically assigned address which matches that specified in the A record for host www. Test your Apache Server Virtual Machine by using a web browser on another host and trying to browse the website www.saffioti.org.au.

Finally harden this host so that only services being used can be accessed by other machines. You will need to use IPTables. Part 3: Remote File Access Once you have set up the web server (in part 2) and tested it, install any FTP server. The FTP server would allow users to upload/ download files to the web server. Configure the server appropriately and then test from another host. You will need to make changes to your firewall configuration. In addition to this add a CNAME for ftp on the name server pointing to server2. Document the entire process and challenges you experienced. Part 4: Making DNS Robust You are to also install bind on Virtual Machine Two and make it a secondary for the above domain. You can install this service from a package or configure from source. Part 5: Simple Web Services In Virtual Machine Two you set up a web server for the DNS namesaffioti.org.au.The server is implemented using the HTTP protocol listening on port 80. Your challenge is to make the same site accessible using the HTTPS protocol. To do this set up SSL with a self signed certificate for the site. In this assignment, two virtual machine running Ubuntu and CentOS were installed and configured on a VMware Workstation Player. The first machine was installed with a BIND, to provide DNS & SSH

services, while the second one was installed with a Web Server. The name server on virtual machine 1 was configured to manage the domain saffioti.org.au. A zone was also set up for the reverse zone and hardened by use of firewall rules, which allowed access to the services. The virtual machine running Ubuntu OS was the web server, where LAMP was installed. The Apache Web Server in the LAMP software was used to host a website. Additionally, an FTP server was configured on the same virtual machine. Part 1: Virtual Machine One – DNS & SSH Server This virtual machine was installed with CentOs, and a BIND (DNS) installed and configured on it. The name server was configured to manage the domain; org.au Step 1: Install Bind sudo yum install bind bind-utils Step 2: Configure DNS The namde.conf file was edited as shown below. nano -w /etc/named.conf Step 3: Configure bind zone nano -w /var/named/saffioti.org.au.zone Restart the Service, then enable it to start automatically at boot time;

the following commands were used; service named restart chkconfig named on Part 2: Virtual Machine Two: Server2 Ubuntu Operating system was installed on this virtual machine, and used as a web server. To enable it server as a web server, LAMP was installed. By definition LAMP is a stack of open source software tools, that are normally installed together to facilitate hosting of dynamic websites and web applications. LAMP translates to Linux, Apache, MySQL, PHP. The three software are installed on Linux along each other to facilitate web hosting. In this exercise, the software were installed in a series of steps as outlined below. step 1: Install Apache To install Apache, the following commands were used; sudo apt-get update: this command is used to update the list of packages and their version. The command only gets and updates information about the packages but does not install the updates. sudo apt-get install apache2: the command installs apache web server. To confirm that the Apache Web server was successfully installed, the default apache page was accessed from a web browser;

Step 2: Install MySQL MySQL database was installed using the command; sudo apt install mysql-server Step 3. Install PHP For PhP to work, a number of packages had to be installed as outlined below. sudo apt install php-pear php-fpm php-dev php-zip php-curl php- xmlrpc php-gd php-mysql php-mbstring php-xml libapache2-mod- php Hardening the Web Server To harden the web server, which makes it more secure, by only allowing access to the web hosting services, the firewall was configured using IPTables. The process is as outline below. Step 1: Install the Persistent Firewall Service For the firewall service to run on the machine, it was necessary to install the iptables-persistent package. The packages allows the rules set to be persisted and be applied automatically at boot time. The following command was used to install the package sudo apt-get install iptables-persistent Step 2: edit the iptables for IPv4

sudo nano /etc/iptables/rules.v4 The same was done for IPTables for IPv6 with the command; sudo nano /etc/iptables/rules.v6 To test for errors in the modified files, the following two commands were used; sudo iptables-restore -t /etc/iptables/rules.v4 sudo ip6tables-restore -t /etc/iptables/rules.v6 No error was reported, meaning the iptables files were okay. The next command was used to activate the rules. For IT assignment help visit myassignmenthelp.com Part 2: Virtual Machine Two - LAMP Server Difficulties Encountered Major difficulties were encountered trying to harden the web server. The iptables-persistent service was not running and attempts to start it failed with the error; \"Failed to start iptables-persistent.service: Unit iptables- persistent.service not found\" After an hour of headache and Googling, I finally found a command to start the service. sudo service netfilter-persistent start

I realized that the failure to start was a problem with some versions of Ubuntu; the above configurations seemed not to work and I had to do the following steps to harden the server with a firewall using IPTables. Step1; resetting the firewall sudo service netfilter-persistent flush After flushing, I verified that the rules were removed. Create Protocols The next step was to crete specific chain of protocols that the web server will accept; UDP, TCP and ICMP sudo iptables -N UDP sudo iptables -N TCP sudo iptables -N ICMP Since SSH traffic uses TCP protocol, I had to add an exception for SSH on the firewall. SSH traffic uses port 22. The following command was used to create the exception. sudo iptables -A TCP -p tcp --dport 22 -j ACCEPT General Purpose Accept/Deny Rules

To facilitate filtering of traffic, some general purpose rules were created to accept of drop packets. For a start traffic for an already established connection was accepted; this was implemented by the command. sudo iptables -A INPUT -m conntrack --ctstate ESTABLISHED,RELATED -j ACCEPT The firewall rule for filtering makes use of conntrack package, which enables internal tracking, allowing the iptables have the context to facilitate evaluation of packets. Allow Loopback traffic To allow traffic from the loopback interface, the following command was executed Deny all invalid Packets Packets that are invalid such as those that address a non-existing port has to be denied. This was implemented using the command. sudo iptables -A INPUT -m conntrack --ctstate INVALID -j DROP Jump Rule for Protocol-Specific Chain To allow traffic reach the desired protocols, some jump rules were created. The rules will filter the traffic and only allow the genuine and valid traffic. For example TCP traffic will be filtered to only allow SYN packets, since SYN is the only valid traffic for TCP type connection.

The following commands were executed to allow the rules to be create; sudo iptables -A INPUT -p udp -m conntrack --ctstate NEW -j UDP sudo iptables -A INPUT -p tcp --syn -m conntrack --ctstate NEW -j TCP sudo iptables -A INPUT -p icmp -m conntrack --ctstate NEW -j ICMP Finally, a rule was created to reject all other traffic hitting the server. The commands below was used to create the rules; sudo iptables -A INPUT -p udp -j REJECT --reject-with icmp-port- unreachable sudo iptables -A INPUT -p tcp -j REJECT --reject-with tcp-reset sudo iptables -A INPUT -j REJECT --reject-with icmp-proto- unreachable sudo iptables -P INPUT DROP sudo iptables -P FORWARD DROP sudo ip6tables -P INPUT DROP sudo ip6tables -P FORWARD DROP sudo ip6tables -P OUTPUT DROP sudo service iptables-persistent save The final state of the iptables is as shown below;

Part 3: Remote File Access This part will install and configure FTP service on Ubuntu [server2] Step 1 — Install vsftpd The following command was used to install vsftpd sudo apt-get install vsftpd Step 2: Configure firewall rules to allow FTP service This configuration will open port 20 and port 21 which are used by the FTP service; for this server the firewall rules were set using iptables. For that reason we need to add a rule in the iptables to allow FTP traffic. The following commands were used; iptables -A INPUT -p tcp -m tcp --dport 21 -j ACCEPT The iptables after adding port 21 and 22. Step 3 — Prepare User Directory First add a test user; sudo adduser saffioti Then create a directory for the user and assign rights; sudo mkdir /home/ saffioti /ftp sudo chown nobody:nogroup /home/ saffioti /ftp sudo chmod a-w /home/ saffioti /ftp

Next we create directory for uploading files into and change the rights; sudo mkdir /home/saffioti/ftp/files sudo chown saffioti:saffioti /home/saffioti/ftp/files Step 4 — Configuring FTP Access To configure access to FTP we edit the file; sudo nano /etc/vsftpd.conf Step 5 — Test FTP Access Testing with anonymous connection Part 4: Making DNS Robust Installing a bind on server2, to make it the secondary DNS server. Installing BIND: apt-get install bind9 Configurations for BIND nano /etc/bind/named.conf.local Then configure the zones file named; saffioti.org.au Define a reverse DNS lookup nano /etc/bind/zones/rev.3.2.1.in- addr.arpa Testing the DNS confirmed it was up and running Part 5: Simple Web Services Step 1: Generate the self signed certificate

Then we sign the certificates followed by modification of Apache's default ssl configuration file Finally we edit the file /etc/apache2/sites-available/default-ssl.conf Original Source: https://myassignmenthelp.com/free- samples/infs5907-managing-security-and-ethics-in- cyberspace/when-implementing-the-virtual-machines.html