The quality to me, which was there in abstract, is a port-53 bound daemon, which uses the client IP network or /32 to specify how it answers.
Server, Resolver, these are distinct classes. I felt split-horizon was the moment of decision logic from "who asked" If anyone has actually bound it to "which interface did I get the question on" thats subtly different, and more side-like. -G On Mon, Mar 19, 2018 at 6:33 PM, Paul Vixie <p...@redbarn.org> wrote: > > > Ted Lemon wrote: >> >> On Mar 19, 2018, at 6:10 PM, George Michaelson <g...@algebras.org >> <mailto:g...@algebras.org>> wrote: >>> >>> "A DNS resolver which looks at the client requesting address, and uses >> >> >> That's a different thing. There's a distinction between a resolver that >> gives different answers, and a set of authoritative servers that give >> different answers. I believe split horizon is referring to the latter, >> not the former. > > > i've done both and referred to both as "split-horizon dns". > > bind9 views does both. > > -- > P Vixie > _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
