On Thu, 2003-06-26 at 12:52, Gerald (Jerry) Carter wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 26 Jun 2003, Andrew Bartlett wrote: > > > I was thinking about 'nice' ways to solve this. It looks like we really > > do have a completely different name resolution system for ADS - so why > > not have "ads" as the resolve type - that we now pass as a parameter? > > > > This should mean we never have lookups for netbios domain names in DNS. > > No. Correctly configure the 'name resolve order' and you should not see > netbios lookups via DNS. At this stage, 'name resolve order' is basically > for netbios only. Just set "name resolve order = wins bcast". Done. > No need for another value to confuse things. It works fine as it is. > Just needs docs.
Except that the current default is "name resolve order = lmhosts wins host bcast" which I think it quite useful. I see the 'host' name resolve type for <00> names (which will often have a one-to-one mapping to netbios names) to be quite useful. What I'm worried about is the lookups for _tcp._ldap.DOMAIN, which would ocour when looking for an ADS DC, but which *will not* find the answer. Naturally, this won't occur if the domain is validly in WINS, but this doesn't always happen. Currently, if I understand this correctly, we will do a DNS lookup (which we know will fail) *before* we broadcast. Why do that lookup (which is not a normal 'hosts' lookup) at all? This is a very special case of lookup, why not deal with it as such? Andrew Bartlett -- Andrew Bartlett [EMAIL PROTECTED] Manager, Authentication Subsystems, Samba Team [EMAIL PROTECTED] Student Network Administrator, Hawker College [EMAIL PROTECTED] http://samba.org http://build.samba.org http://hawkerc.net
signature.asc
Description: This is a digitally signed message part
