Comprehensive Study Notes on DNS, HTTP, and DHCP Server Configuration in Packet Tracer

Network Topology and IPv4 Addressing Architecture

  • Simulation Objective and Scope:

    • Expansion of an existing local network simulation by adding two dedicated server nodes: a Domain Name System (DNS) server and a Hypertext Transfer Protocol / Hypertext Transfer Protocol Secure (HTTP/HTTPS) web server.

    • Integration of these services with an existing Dynamic Host Configuration Protocol (DHCP) server infrastructure to automate client configuration and provide localized name resolution and web hosting.

  • Static Infrastructure IPv4 Addressing Scheme:

    • Default Gateway (Router Interface): Statically assigned to 192.168.10.1192.168.10.1.

    • DHCP Server: Statically assigned to 192.168.10.2192.168.10.2.

    • DNS Server: Statically assigned to 192.168.10.3192.168.10.3.

    • HTTP/HTTPS Web Server: Statically assigned to 192.168.10.4192.168.10.4.

    • Reserved Infrastructure Range: Addresses 192.168.10.1192.168.10.1 through 192.168.10.10192.168.10.10 are reserved for network equipment, routers, and dedicated servers.

  • Dynamic Client IPv4 Address Pool:

    • Pool Start IP Address: Starts at 192.168.10.11192.168.10.11.

    • Pool End IP Address: Extends up to 192.168.10.254192.168.10.254.

    • Total Leasable Dynamic Addresses: Exactly 244244 host addresses are allocated for DHCP client distribution.

  • Transition from Public to Localized Resolvers:

    • Replaces external public DNS resolvers (such as Google Public DNS at 8.8.8.88.8.8.8) with an internally hosted private DNS server (192.168.10.3192.168.10.3).

    • Ensures all internal domain requests resolve locally within the private subnet without requiring external internet routing.

DHCP Server Configuration and Advertisement

  • Service Parameters and Pool Definition:

    • DHCP Service Status: Enabled (switched to ON).

    • Default Gateway Parameter: Configured to advertise 192.168.10.1192.168.10.1 to all clients.

    • DNS Server Parameter: Configured to advertise 192.168.10.3192.168.10.3 to all clients.

    • Start IP Address: Configured to begin dynamic assignments at 192.168.10.11192.168.10.11.

    • Subnet Mask: Configured as a Class C standard mask of 255.255.255.0255.255.255.0.

    • Maximum Number of Users / Leases: Fixed at 244244.

  • Synchronization Between Interface and Service Settings:

    • The general settings and FastEthernet interface of the DHCP server must be consistently configured with the static IP 192.168.10.2192.168.10.2, subnet mask 255.255.255.0255.255.255.0, and default gateway 192.168.10.1192.168.10.1.

    • Any mismatch between the server interface IP and the advertised DHCP pool subnet prevents clients from obtaining valid network leases.

  • Client Lease Propagation and Refresh Mechanism:

    • Client end-devices must execute a DHCP request, lease renewal, or hard refresh to obtain the newly advertised DNS server IP (192.168.10.3192.168.10.3).

    • Clients sequentially receive leases starting from 192.168.10.11192.168.10.11, 192.168.10.12192.168.10.12, up through subsequent available addresses.

DNS Server Configuration and Name Resolution Mechanism

  • Operational Theory of Domain Name Systems:

    • Network communication across lower OSI layers relies strictly on numeric IPv4/IPv6 addresses.

    • The DNS server operates as a translation service that maps alphanumeric, user-friendly domain names to their underlying numerical IP addresses and vice versa.

  • DNS Server Interface Configuration:

    • Static IP Address: 192.168.10.3192.168.10.3.

    • Subnet Mask: 255.255.255.0255.255.255.0.

    • Default Gateway: 192.168.10.1192.168.10.1.

    • DNS Server Field: Set to itself (192.168.10.3192.168.10.3).

  • DNS Resource Record Entry:

    • Service State: Switched to ON.

    • Record Type: A Record (Address record mapping a fully qualified domain name to an IPv4 address).

    • Domain Name Entry: myschool.carsu.edu.ph (referenced phonetically in configuration trials as myschool.carso.edu.ph or myschool.carcer.edu.ph).

    • Mapped IP Address: 192.168.10.4192.168.10.4 (the static IP address of the dedicated HTTP web server).

    • Commit Step: The record is added to the active DNS database and saved.

HTTP/HTTPS Web Server Setup and Content Customization

  • Web Server Network Settings:

    • Static IP Address: 192.168.10.4192.168.10.4.

    • Subnet Mask: 255.255.255.0255.255.255.0.

    • Default Gateway: 192.168.10.1192.168.10.1.

    • DNS Server Setting: Configured to point to 192.168.10.3192.168.10.3.

  • Web Service Management:

    • Both HTTP and HTTPS services are enabled (ON) within the server management tab.

    • Web hosting is implemented by modifying the primary hypertext file: index.html.

  • Custom Portal Content Specification:

    • The default Cisco Packet Tracer template text inside index.html is edited and replaced with custom institutional branding:

    • Institution Title: Caraga State University.

    • Subtitle / Header Note: Opening doors to new opportunities.

    • Portal Section: MySchool.

    • Quick Links Navigation Menu:

      • MySchool

      • MyGrades

      • MyClearance

      • Enrollment

      • MySchedule

    • The modified index.html is saved to ensure immediate rendering upon inbound client HTTP GET requests.

End-to-End Client Testing and Cross-Subnet Verification

  • Diagnostic Connectivity Testing Procedure:

    • ICMP Ping Verification: From client desktop Command Prompts, ping commands verify Layer 3 reachability to:

    • Router Default Gateway: ping 192.168.10.1192.168.10.1.

    • Dedicated DNS Server: ping 192.168.10.3192.168.10.3.

    • Dedicated HTTP Server: ping 192.168.10.4192.168.10.4.

    • Direct IP Web Verification: Typing 192.168.10.4192.168.10.4 directly into the client web browser verifies that the web server renders pages independently of DNS operational status, isolating HTTP connectivity issues from DNS resolution issues.

    • Hostname Resolution Web Verification: Typing the fully qualified domain name myschool.carsu.edu.ph (or myschool.carso.edu.ph) into the browser URL bar triggers a DNS request to 192.168.10.3192.168.10.3, resolves to 192.168.10.4192.168.10.4, and returns the customized Caraga State University web portal.

  • Wireless Integration and Mobile Client Testing:

    • Wireless Access Point: Connected to the central distribution switch using the network identifier Golden Paddlers (Golden Paddlers access point).

    • Mobile Client: A wireless smartphone connects via the Golden Paddlers access point and acquires network settings dynamically via DHCP.

    • Browser Validation: The smartphone launches its built-in browser, inputs myschool.carsu.edu.ph / myschool.carso.edu.ph, and validates that the internal university portal renders consistently across all media types (wired Ethernet and wireless 802.11).

Questions, Troubleshooting, and In-Class Dialogue

  • Dialogue: Subnet Range Discrepancy:

    • Student Remark: Pointed out an addressing inconsistency during setup: "Sir, one login, sir. It's not that ten sir."

    • Clarification: Previous configurations utilized a 192.168.1.x network range, whereas the current simulation topology has been reconfigured and standardized to the 192.168.10.x subnet. All static entries (router default gateway at 192.168.10.1192.168.10.1, server general settings, and DHCP pool scopes starting at 192.168.10.11192.168.10.11) must align to 192.168.10.0/24192.168.10.0/24 to maintain reachability.

  • Troubleshooting: Stale DHCP Settings on Clients:

    • If a client fails to load the web page using the domain name, verify whether the client received the updated DNS advertisement (192.168.10.3192.168.10.3).

    • Resolve by toggling the client network interface from DHCP to Static and back to DHCP, forcing a renewal and cache clearing.

Future Network Enhancements: Security and Segmentation

  • VLANs and Inter-VLAN Routing:

    • Partitioning client subnets into Virtual Local Area Networks (VLANs) to isolate administrative, student, and server traffic.

    • Deploying router sub-interfaces (Router-on-a-Stick) or Layer 3 Core Switches to route traffic across disparate subnets.

  • Access Restriction and Filtering:

    • IP Address Filtering: Configuring Access Control Lists (ACLs) on the router or core switch to restrict access to the web server, allowing authorized IP ranges to reach the portal while blocking others.

    • MAC Address Filtering: Enforcing Layer 2 hardware filtering on wireless access points (such as the Golden Paddlers access point) and switches to restrict unauthorized physical devices from connecting to the local area network.