Experiment 10 — DNS Queries and HTTP/HTTPS Requests

Manual pages: 89–91 | Tools: Command Prompt, Chrome DevTools; optional Postman

AIM

To test DNS queries and HTTP/HTTPS requests and study domain-name resolution and client–server request/response behavior.

PART A — DNS EXECUTION

Open Windows Command Prompt (Win + R → cmd).
Run nslookup google.com. Note DNS server, domain and returned IP addresses.
If dig is installed, run dig google.com and dig +short google.com (the second prints concise answers). dig is not included with Windows by default; lack of dig is not a network failure.

PART B — HTTP/HTTPS EXECUTION

Chrome → open https://example.com → press F12 → Network tab.
Ensure red recording dot is enabled; refresh the page. Click the example.com/Document request.
Inspect Headers (Request URL, GET, Status Code), Response (HTML), Timing (timings); optional Doc / Fetch-XHR filters.
Optional Postman practice, matching experiment title: new GET https://example.com → Send → examine status and HTML body. The manual's detailed procedural section specifically uses browser DevTools, not a complete Postman walkthrough.

COMMANDS

See WINDOWS_COMMANDS.txt.

EXPECTED OUTPUT

nslookup google.com => domain resolves to one or more IP addresses
Chrome Network: GET https://example.com/ -> HTTP 200 OK (if reachable)
Response: HTML document; Timing: request phases

RESULT

Thus, DNS resolution with nslookup/dig and HTTP/HTTPS request inspection using browser developer tools were demonstrated.

VIVA

DNS resolves domain names to IP addresses; GET fetches a resource.
HTTPS uses TLS to protect transport.
HTTP 200: request succeeded; 404: resource not found; 500: server error.