Configuring Network Services Using the same network topology that you have setup
ID: 3752363 • Letter: C
Question
Configuring Network Services Using the same network topology that you have setup in Task 1, perform the following additional activities [15 marks]:
1.DHCP: Configure DHCP on the server and show that the client PC has successfully received an IP Address and other network parameters (default router, netmask, DNS) using DHCP;
2.WEB Server: Configure a WEB server on the dedicated machine, with URL as www.YOUR NAME.csu.edu.au
3.DNS: Configure a DNS Server on the server device and demonstrate that forward and reverse DNS are working from the client PC; test DNS Server by browsing www.YOUR NAME.csu.edu.au from client PC, DNS must resolve this URL to IP address of WEB Server
4.Firewall: Configure traffic filtering on the router to block TCP traffic only between one of the client PC and WEB Servers, and provide evidence of such traffic filtering. A series of screenshots with commentary on each of the required tasks is to be submitted. T
he submission must include a comprehensive explanation of each task and all the commands used along with the output (or final result) in report format. it should be in packet tracer and packet tracer file should be embbeded with the word file. setting up network shoud be in cisco packet tracer. in the url type the baljinder name.
Explanation / Answer
Webserver configuration:
On the off chance that you have a straightforward html site then these are the four stages associated with completing your activity.
Make a machine
You can begin with any famous cloud benefit like AWS or DigitalOcean. Making a machine is a trifling procedure. This machine is your committed server and we will call this a hub. Select 'Ubuntu' as your working framework in the event that your are new to the cloud world. Ubuntu is a broadly utilized server working framework and you will get enough help on discussions and the web in the event that you stall out in the following stages.
Login | ssh into the machine and introduce a web server and ftp
For your hub to serve your site you require a bit of programming which is ordered as a web server. The most well known web server applications utilized today are apache and nginx. Expecting your site is plain html then it doesn't make a difference which one you pick however introduce just a single of those. Ftp server will be utilized to duplicate your site code from neighborhood machine to your hub in the cloud.
$ sudo adept get introduce apache2 vsftpd
Duplicate your code to the machine.
For your hub to serve your site, the web server must know where the site code is. The default area where apache2 will search for is/var/www/html. In the event that you drop your html here you are finished. Since we have ftp running on the hub, we simply require a customer on our nearby machine to interface with the hub and exchange our records. Filezilla is a well known ftp customer. You will likewise discover ftp modules for your most loved program. After you have exchanged your substance, the site ought to be open with the IP address of your hub.
Design your DNS to point to this machine.
At long last you should outline area name to this machines IP address. This should be possible by including an 'A' record to your area.
Configure a DNS Server Profile
Step1: Name the DNS server profile, select the virtual framework to which it applies, and determine the essential and optional DNS server addresses.
Select Device > Server Profiles > DNS and snap Add.
Enter a Name for the DNS server profile.
Select the Location (virtual framework) to which the profile applies.
For Inheritance Source, starting from the drop, select None if the DNS server addresses are not acquired. Something else, determine the DNS server from which the profile ought to acquire settings. In the event that you pick a DNS server, click Check legacy source status to see that data.
Determine the IP address of the Primary DNS server, or leave as acquired in the event that you picked an Inheritance Source.
Remember that on the off chance that you indicate a FQDN rather than an IP address, the DNS for that FQDN is settled in Device > Virtual Systems > DNS Proxy.
Indicate the IP address of the Secondary DNS server, or leave as acquired in the event that you picked an Inheritance Source.
Step2:Configure the administration course that the firewall consequently utilizes, in light of whether the objective DNS Server has an IP address family kind of IPv4 or IPv6.
Snap Service Route IPv4 to empower the resulting interface and IPv4 deliver to be utilized as the administration course, if the objective DNS address is an IPv4 address.
Indicate the Source Interface to choose the DNS server's source IP address that the administration course will utilize. The firewall figures out which virtual switch is relegated that interface, and afterward completes a course query in the virtual switch directing table to achieve the goal organize (in view of the Primary DNS address).
Determine the IPv4 Source Address from which bundles heading off to the DNS server are sourced.
Snap Service Route IPv6 to empower the ensuing interface and IPv6 deliver to be utilized as the administration course, if the objective DNS address is an IPv6 address.
Determine the Source Interface to choose the DNS server's source IP address that the administration course will utilize. The firewall figures out which virtual switch is relegated that interface, and after that completes a course query in the virtual switch steering table to achieve the goal arrange (in view of the Primary DNS address).
Determine the IPv6 Source Address from which parcels heading off to the DNS server are sourced.
step3: Click OK.
Spare the arrangement.
Snap OK and Commit.