On Sat, Aug 26, 2023 at 04:24:25PM -0500, o1bigtenor via Dng wrote:
> On Sat, Aug 26, 2023 at 3:36 PM Steve Litt <slitt@???> wrote:
> >
> > o1bigtenor via Dng said on Sat, 26 Aug 2023 08:36:26 -0500
> >
> > >Greetings
> > >
> > >I am now quite desperate!!
> > >Have had about 3 (maybe its 4 already) times in the last 6 weeks where
> > >I have DNS issues.
> > >Have a terrible ISP on fixed wireless that is very clear that they
> > >have NO assistance for *nix users - - - - and mz googly is always
> > >their friend.
> >
> > What's mz googly?
>
> A euphemism for google.
> >
> > >(Running devuan daedalus on my main system (haven't yet moved to
> > >excalibur but that's going to happen RSN.)
> > >Issue this time:
> > >
> > >after wakeup go to computer - - - not able to access the web
> > >check router - - - WAN is accessible
> > >ping 8.8.8.8 destination unreachable
> >
> > if ping 8.8.8.8 fails, that particular symptom has nothing to do with
> > DNS.
> >
> > >ping router - - (WTF) destination unreachable
> >
> > OK, if you can't get to the router you can't get to 8.8.8.8, so that's
> > consistant.
> >
> > >power cycle the router
> >
> >
> >
> > >can now ping 8.8.8.8 but not mz googly.ca
> >
> > Serious business, if you want help, you need to define your terms. I
> > pinged googly.ca and got back:
> >
> > [slitt@mydesk ~]$ ping googly.ca
> > ping: googly.ca: No address associated with hostname
> > [slitt@mydesk ~]$
> >
> > I have no idea what mz googly is, and I shouldn't have to rtfm the
> > phrase just to help you. I doubt I'm the only one.
> >
> > I did, however, take the time to ping and browse and traceroute to
> > googly.com, and found out it's my local nginx server on 127.0.0.1.
> >
> > >have wireless access to the web (this is the weird part imo)
> > >I call tech support - - - they tell me to just clear the DNS cache on
> > >my puter sadly - - - this is something I do not know how to do (!!!)
> > >looking on the web - - - I can't find anything for sysV init systems
> > > (can for systemd but that's it!! - - - argh!)
> > >
> > >Is there someone out there that can help me with either the command(s)
> > >or the process so I don't have to reboot my system to clear my DNS
> > >issues - - - please?
> > >
> > >TIA
> >
> The following is an excellent answer to a question I didn't ask.
>
> > There's no substitute for a local DNS resolver. What you can do is to
> > install the Unbound recursive resolver daemon on your computer, then
> > edit /etc/resolv.conf to always point to that daemon's IP address (I
> > use 192.168.0.102, which is an alias for my desktop's main IP of
> > 192.168.0.2). Immediately after, chattr +i /etc/resolv.conf to prevent
> > "helpful" DNS programs like networkmanager, etc, from "helpfully"
> > changing that file. I do it like this:
> >
> > chattr -i /etc/resolv.conf;vim /etc/resolv.conf;chattr +i
> > /etc/resolv.conf
> >
> > By the way, it might be a good idea to list one or two public name
> > servers after the one pointing to Unbound's address. For one using
> > Linux, I see no reason in the 21st century to depend on the DNS server
> > provided by your ISP.
> >
> > The following document is an introduction to Unbound:
> >
> > http://troubleshooters.com/linux/unbound_nsd/unbound.htm
> >
> > After reading that document, you'll be able to RTFM your way to
> > success, and from the perspective of DNS, your ISP will forever be out
> > of the loop.
> >
>
> A good answer but an answer to the question - - - - how do I install a
> dns server
> on my system.
>
> My question was and still is - - if I'm getting dns resolution on my router
> how and/or what do I change so that I can now access the internet from
> my computer.
>
> What I've been able to find " $ service connman restart " dunno if that
> will fix things.

I do not like connman.

connman maintains its own DNS cache.
I have found no method to delete its cache.
I ran into troule with this while attempting to update my Devian system.
t seems the round-robin choice of Devuan package repositiry mirrors happened to choose a dud mirror.
So the update failed.
I think -- no problem. I just need to try the upgrade again and I'll likely get a new random mirror.
But connman's cache just gave me the same IP number again. It figure it already knew it.

The only remedy was to edut /etc/resolv.conf to refer explicitly to some DNS resolver other than 127.0.0.1, such as 1.1.1.1 oe 8.8.8.8 ...

When I do this upgrading works again, connman's DNS is bypassed, and (puzzling) my system's printer discovery stops working.

I do not like connman.

-- hendrik

>
> Regards
> _______________________________________________
> Dng mailing list
> Dng@???
> https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng