Articles

DNS propagation is the informal name for the interval when resolvers still return different answers after a record changes. DNS does not broadcast a new value to every server at once. Recursive resolvers fetch answers when needed and may retain them in a cache for the permitted lifetime.

DNS, the Domain Name System, is a distributed naming system that helps applications locate network resources. A website name can resolve to IPv4 or IPv6 addresses, while other records direct email or identify authoritative name servers. A domain name does not have to point to just one server.

DNSSEC adds digital signatures to DNS data. A validating resolver can detect a forged response or a broken chain of trust. It protects the origin and integrity of records, but does not encrypt DNS queries or automatically make a website trustworthy.

Encryption transforms readable information into ciphertext that can be recovered with the right key. Its purpose is to keep data confidential during transfer or storage. Hashing and checksums solve different problems: their output is not decrypted to recover the original message. Confusing these operations can lead to a false sense of security.

Internet Protocol (IP) carries packets between networks using IP addresses. Today, IPv4 uses 32-bit addresses and IPv6 uses 128-bit addresses. IP provides addressing and routing, but does not by itself promise that every packet arrives, arrives in order or has protected contents. Other protocols and applications add the services they need.

localhost normally refers to the machine from which a request is made. Its familiar addresses are IPv4 127.0.0.1 and IPv6 ::1. Traffic to them is handled inside that machine’s network stack rather than travelling through the home router to the Internet. A localhost test therefore answers a narrow question: does the service work locally?

MTU is the largest network packet size an interface or link can carry without splitting it at that layer. A common Ethernet MTU is 1500 bytes, but tunnels and other links may allow less. A connection must work within the limits of the path it actually takes.

NAT, or Network Address Translation, changes packet addresses at a network boundary. In a home network, a router commonly lets several privately addressed IPv4 devices use one external IPv4 address. It often changes port numbers as well so that it can distinguish multiple simultaneous connections.

A normal DNS lookup obtains an address from a name. Reverse DNS asks a different question: given an IP address, which name is recorded in its dedicated reverse zone? The answer comes from a PTR record. It is useful in network and mail operations, but it does not establish a person’s identity or site ownership.

Spam is unwanted bulk communication, most commonly email but also messages through social networks, messengers and comments. It can be advertising, fraud or a delivery channel for malware. The fact that a message is unsolicited does not prove that it is dangerous, but its links, attachments and requests deserve careful handling.

WHOIS is the traditional way to look up registration information for a domain or an Internet number resource. For generic top-level domains, RDAP is now the primary source of registration data. A result may show a registrar, dates, status codes and nameservers. Personal details about the registrant are often withheld.

When an address starts with 169.254, check how the host identifies its local network, neighbours and route to other networks. IPv4 depends on the address, prefix length and gateway; IPv6 also depends on address scope and Neighbor Discovery. One wrong value can leave local communication working while breaking access beyond the subnet.

When email delivery fails, examine the recipient domain, MX/DNS, SMTP connection, server response, authentication policy and later filtering separately. An SMTP acceptance does not guarantee Inbox placement, and the absence of an immediate bounce does not prove long-term mailbox availability.

A single Mbps number cannot explain why an Internet connection is slow. Throughput, latency, jitter and packet loss describe different properties, while Wi-Fi, Ethernet, competing devices, VPNs, routing and the test server all affect results. High throughput can coexist with poor latency under load.

To find why a port is closed, examine the transport or network path. Separate the local socket, IP delivery, TCP or UDP behaviour, firewall filtering and NAT. A successful ping does not prove a TCP port is reachable, and an open port does not prove the application protocol is healthy.

Ethernet and Wi‑Fi can reach the same Internet service but behave differently on the local link. Wi‑Fi shares radio airtime and depends on signal and interference, while wired Ethernet usually provides a more stable local connection.