Connection and two reads share one overall budget. A further wait is not started after the budget is spent; a successful individual read does not ensure timely completion.

Connection timeouts prevent silent hangs

A timeout names how long a particular operation may wait. It is not automatically a deadline for the whole request, and it does not prove that the remote operation stopped. Separate connection establishment, individual reads, and the caller’s overall budget before choosing numbers or interpreting a timeout error. ...

August 1, 2027 · 5 min · XB Field Notes
Three dependency boxes show alias, middle and target with independent TTLs of 9, 12 and 20 seconds from one answer. A separate HTTP identity band keeps Host as alias.lab.test plus the temporary port. The arrows are DNS dependencies, not URL redirects.

A CNAME changes DNS resolution while the requested hostname stays the same

A CNAME record associates an alias name with another DNS name. When resolving an address through that alias, a resolver follows the target until it obtains the requested data or encounters a failure. This lets a public hostname remain stable while its DNS dependency changes. It does not redirect a browser to another URL or replace the application’s requested hostname. ...

July 9, 2027 · 6 min · XB Field Notes
DNS answers rotate between A then B and B then A, but one saved application choice sends twelve requests to the selected peer and zero to the other in the article example.

Multiple DNS addresses do not guarantee balanced or healthy traffic

Several A or AAAA records at one name provide an address set. A DNS server may rotate the order it returns, but the receiving resolver and application decide how to use that set. Ordinary address records contain no request-load measurement or application-health result. Their presence alone does not promise equal traffic, automatic failover, or even a particular first address across implementations. ...

July 6, 2027 · 6 min · XB Field Notes