On 04/10/2018 09:29 PM, Ken Moffat wrote:
On Tue, Apr 10, 2018 at 09:07:47PM -0700, Terry Coats wrote:
My provider's dns was slow so I haven't used them in quite a while.
lfs SVN-20180323 running unbound /etc/resolv.conf is
I asked because I had read your mail as suggesting you were not
On Tue, Apr 10, 2018 at 09:07:47PM -0700, Terry Coats wrote:
>
> My provider's dns was slow so I haven't used them in quite a while.
> lfs SVN-20180323 running unbound /etc/resolv.conf is
I asked because I had read your mail as suggesting you were not
using google on the svn (unbound) build.
>
On 04/10/2018 08:34 PM, Ken Moffat wrote:
Because of unbound problems I stopped using it on lfs 8.0 and use a static
config of 192.168.1.140 for my address and use google dns servers listed in
/etc/resolv.conf.
I'll do this also for lfs SVN-20180323, just haven't got around to it yet.
I am
On Tue, Apr 10, 2018 at 07:44:14PM -0700, Terry Coats wrote:
> I don't know if this is the proper place for this problem but since I'm
> experiencing it from my lfs systems I'd like to mention it.
>
> My problem is when I use one of my lfs systems with unbound it screws up my
> network upsteam,
I don't know if this is the proper place for this problem but since I'm
experiencing it from my lfs systems I'd like to mention it.
My problem is when I use one of my lfs systems with unbound it screws up
my network upsteam, probably at my wireless router. What's happening is
if I use my lfs
