plans: the resolver asks whoever it meets first, and the picker that would choose is dead code #2153
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
jaylouisw/packetforge!2153
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "plan/1119-1237"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Forward plan only, no code. Measured on
2eeb3051with three labs built onTopology/Simulator.Findings
ip name-serverorder is ignored: a client listing 10.9.0.2 then 10.9.0.5 was answered by 10.9.0.5, becauseresolveName()scanstopo.devices.values()(simulator.js:294-305).ok: true.labandsub.labon one box,www.sub.labwas answered fromlab(10.0.0.30) althoughsub.labis authoritative (10.0.0.31) — zones are consulted in config order.planQuery()(dns.js:532-557) and the step-driven answer cache (dns.js:446-492) are exported, unit-tested, and called by nothing but their own tests.simulator.js:137,:228-260,:137-156;resolveNameis at:292-370.Seven steps: docs pointers/broadcast claim (S),
bestZone()longest-apex in dns.js (S), use planQuery + bestZone in the resolver (M), reachability filter (M), wire the cache ontoposo API requests share it (M),show ip dns cache/clear ip dns cache(S, needs Jay's approval), docs §5.7 to Modelled (S).Closes no open issue: the queue is #2146 (refusal advice, #2147/#2151 in flight) and #130 (device request). New suite
test/dns-selection.test.jsreproduces all three probes.