Hi Snidely, On Wednesday 18 September 2019 10:49:31 Snidely Whiplash wrote: > On Tue, Sep 17, 2019 at 7:28 AM Baron <baron@xxxxxxxxxxxxxxx> wrote: > > Unbelievable ! I did as you suggested and everything is now back > > to normal, > > I don't think "lan" would be valid in the search directive, only a > domain. I only put nameserver directives in my resolv.conf files, I > don't particularly want that behaviour, at least not unless I > actually had a domain that directive could catch. See, what > happened to you is, you typed an improperly formatted address (not > a fully qualified domain) so your resolver was trying to append > .lan to your http://localhost. Actually I didn't put it there ! It was automatically generated by "Network Manager" ! I had absolutely no idea until you pointed it out. Surely that has to be a bug or at least an error ! Again thank you for your insight. -- Best Regards: Baron --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-users-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
