Vincenzo Gianferrari Pini wrote:
> if I understood well, the behaviour *before* you add the "domain"
> entry in resolv.conf was coherent with what is prescripted in "man
> resolv.conf`"
Yes, I believe so. As I commented, Brian might just want to take a quick
review of the code to see where it is doing this, since this behavior seems
to have surprised even him. :-)
> it should be a James concern to avoid falling in this trick, adding a
> '.' at the end of the whitelist (and blacklist) domain name strings
> before calling lookup, or even better putting a '.' at the end of the
> names available in the stock configuration files, with a warning
> explaining it.
:-) Yes, I had added the trailing '.' to the configuration files, just as
you have described to Norman, in addition to fixing my resolv.conf. Adding
the '.' is fine for those entries because I know that those domain names are
absolute. However ...
As for the lookup code, we should be extremely careful. Just adding '.'
arbitrarily is not the same thing. As you've noted in later e-mail, "an
administrator could want to use names relative to his own domain", and some
might come from sources other than the config file. I am leaning towards
agreeing with Stefano's -1 to change the code. If we were make any change
at all, it might be to adjust our lookup to behave the same way that dig
does (using Name.root), but we should give some serious thought to it before
making any change.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
