← Back to context Comment by immibis 1 month ago This is a recursive resolver quirk 2 comments immibis Reply zinekeller 1 month ago ... that was perpetuated by BIND.(Yes, there are other recursive resolver implementations, but they look at BIND as the reference implementation and absent any contravention to the RFC or intentional design-level decisions, they would follow BIND's mechanism.) account42 1 month ago It's also the most natural way to structure the answer:Hey, where can I find A.Answer: A is actually BAnswer: Also B can be found at 42
zinekeller 1 month ago ... that was perpetuated by BIND.(Yes, there are other recursive resolver implementations, but they look at BIND as the reference implementation and absent any contravention to the RFC or intentional design-level decisions, they would follow BIND's mechanism.) account42 1 month ago It's also the most natural way to structure the answer:Hey, where can I find A.Answer: A is actually BAnswer: Also B can be found at 42
account42 1 month ago It's also the most natural way to structure the answer:Hey, where can I find A.Answer: A is actually BAnswer: Also B can be found at 42
... that was perpetuated by BIND.
(Yes, there are other recursive resolver implementations, but they look at BIND as the reference implementation and absent any contravention to the RFC or intentional design-level decisions, they would follow BIND's mechanism.)
It's also the most natural way to structure the answer:
Hey, where can I find A.
Answer: A is actually B
Answer: Also B can be found at 42