Page 113 of the DSE IT knowledge center, with source-backed guidance and practical next steps.
Production-minded guidance for endpoints, servers, updates, cloud services, administration, and supportable operations.
During Exchange, adjacent OSPF routers describe their link-state databases; missing or newer LSAs populate the link-state request list. A router sends Link State Requests until the request list is empty, then a Loading adjacency advances to Full.
Read the checklist
Endpoint-independent UDP mapping reuses one external mapping for the same internal address and port across every external destination, and a NAT must provide that behavior.
Read the explainer
A NAT must translate a TCP RST that matches an existing mapping and should retain the associated session state for four minutes unless another packet arrives.
Read the guide
The configurable address-selection policy table supplies destination precedence and labels that favor source and destination prefixes with matching labels.
Read the playbook
The /127 recommendation applies only to point-to-point links with exactly two routers and no attached hosts; router-to-host and mixed links are outside its scope.
Read the briefing
A validating BGP speaker must determine egress origin-validation state from the effective origin AS after outbound configuration and policy have been applied.
Read the checklist
Before processing an IPv4 packet, a router must validate minimum lengths, checksum, version, header length, and total length; failures are discarded and should be logged.
Read the explainer
TCP establishes a connection through a three-way handshake, including simultaneous opens in which both peers transition through SYN-SENT and SYN-RECEIVED before ESTABLISHED.
Read the guide
A host must verify the IPv4 header checksum on every received datagram and silently discard a datagram with a bad checksum. A host must generate and validate UDP checksums, enable checksum generation by default, and silently discard a received nonzero checksum that is invalid.
Read the playbook
The Windows DNSSEC Key Master generates and manages cryptographic keys for a signed zone. Only one DNS server can be Key Master for a specific zone at a time, and it must be an authoritative primary capable of online signing.
Read the briefing