You would need knowledge in these kinds of the stuff shown below to be able to proceed also if you use the internet please send references

Sections, one for each subject area:

Section 1: DNS Deployment

Section 2: HTTP Deployment

Section 3: NFS Deployment

Section 4: MySQL Deployment

 

 

 

DNS Deployment

1. DNS setup and configuration

(a) Discuss setup and configuration of DNS servers step by step required for the company

described in the company brief report In general, discuss zone distribution among primary and secondary servers and subdomains. Provide example configurations as part of the discussion to highlight your points 

 

(b) Discuss the consequences of not limiting zone transfers between primary and secondary

servers. (Make sure you discuss the DNS packet types involved - research required! ).

 

 

2. SOA (Start of Authority) record and $ORIGIN directive.

 (a) Discuss components of an SOA record and how the options affect the communications

between servers, and servers and clients. Provide an example configuration of

SoA record and discuss how caching, waiting times and updating frequencies are set on

your example configuration.

 

 (b) Discuss how the $ORIGIN directive simplifies the creation of zone files and how it can

be used in creating a sub-domain. 

 

 

 

 

 

HTTP Deployment 

1. Web server setup and configuration

 (a) Setup and configure a web server on Linux using any tool other than Apache. Provide

screenshots of your configuration and discuss advantages and disadvantages of this server

configuration to the Apache web server configuration.

 

 (b) In the context of running Apache in a load-balanced environment discuss the concept of

virtual websites and how they function in detail. 

 

 

 

NFS Deployment 

1. NFS setup and configuration.

(a) Discuss setup and configuration of NFS servers step by step required for the company

described in the company brief report. Discuss how rDNS can be used

(configured and employed) as a security mechanism to limit access the shared content

repository 

 

(b) Discuss the rDNS validation process when using a regex defined domain name export

 

 

 

 

MySQL Deployment 

1. MySQL setup and configuration.

 (a) What accounts and security settings are required to install a MySQL database with a

PHPMyAdmin interface in a secure manner? 

 

(b) What is the most appropriate way to create/configure a database and user account for a

system and why? 

4.2 Admin zone - (tech) The admin (tech) zone is used by the technical staff to manage the infrastructure of the organisation. All equipment that the company places on the network is added to this domain so that it can be uniquely access by the technical staff who manage the equipment. The domain has regularly additions made to it, but the mappings of devices to their allocated addresses are rarely changed. Howeber. the company does not want want any mappings cached on the network. The domain name allocated is the asset number given by the finance department and the zone name. Asset numbers start with an A and are followed by an 8 digit number. e.g. A12345678.tech.co.uk Machines that are to run a network service are assigned an alias to make their name easier to remember. This name used to access the service (database, mail etc.). When equipment is updated or replaced by a new asset the asset number-based domain name will change but the service access name will be the same. 4.3 Staff sub-domain zone- (staff.unn) The staff.unn zone is used to map staff in the company to desktop machines. All the machines use sharing of some sort for the staff to make documents available usually via universal naming convention (UNC) or uniform resource locator (URL). Therefore, each member of staff is allocated a domain name based on their name (e.g. William Smith will be given ws, so their full domain name will be ws.staff.unn.co.uk). If more than one member of staff has the same initials a number will be appended to the name e.g. ws1. All staff movements, should there be any, take place monthly and the domain zone distribution needs to cater for this. END