> > You can ignore the option and talk to the DNS server of your > preference. You can also choose to listen for the option only from one > or more trusted sources. > > > > I'm really unclear about this "trusted sources" thing, though. Is > that "trust only if you're on a trusted network"? Because I think the > problem basically is that there's no sDHCP, right?
E.g. by definition. Implement this only if you are a CPE or if you are 3GPP handset and then only for this class of interface. Or such. Those two scenarios are my main focus. Not believe what CoffeeShopFreeAP tells. > > Of course there could be multiple search list from different > interfaces. In such case you could prioritize the search lists by some > means and start walking through the suffixes when resolving bare name. > > > > This is all a little hand-wavy. "Some means" sounds like the road to > user-surprise-perdition. Bare names are already a bugbear, and I > don't think we want to make them even more surprising. I say some because I have not considered domain search list conflict resolution problem before this thread. Well, if the host is openly multihomed and somewhere comes name "server", you could append it with all suffixes you know of and try resolve then all in parallel, connect in order of successful resolution:) .. if you don't know any difference between your interfaces. Teemu _______________________________________________ DNSOP mailing list [email protected] https://www.ietf.org/mailman/listinfo/dnsop
