On 30/09/2020 13.40, Ralph wrote:
On Wed, 30 Sep 2020 12:09:36 +0200 "Carlos E. R." <> wrote:
On 30/09/2020 11.53, Ralph wrote:
What your Linux machine will use, aside of Firefox, is written in "/etc/resolv.conf". Doesn't mean you have to edit the file, but that whatever sets it up should end written in there. Hopefully automatically.
Hi Carlos, thanks for reply.
So all the many (linux) ways of setting DNS still all end up in exactly the same place, written in resolv.conf? Ok, so these questions remain:
1 - if all the different ways of setting the resolver(s) have different resolver(s), which one gets the 'prize', which is the final one written to resolv.conf? What order does linux read and write them?
I don't know for sure, it depends on the actual configuration of each machine. In each case I have to look around to find out - or I directly edit that resolv.conf
2 - why is dhclient.conf (prepend) not being applied? Because it is not the 'last' place searched for a resolver? This used to be where I made my only-needed changes pre-15.2 (different modem/router) but it does nothing in 15.2.
Maybe that daemon is not used.
3 - can the ISP, 'owning' the firmware sitting between linux and the net, still redirect the query to his own server (and logs), return fake data, and spoof the reply to make it appear it went to and came from the requested server? (theoretical issue, don't ask 'why' I ask this question...)
They might... they would have to create software for this, to capture packages and repurpose them. But then, you can issue a command like "host -v someaddress yourdnsipaddress" and see if the reply is suspicious. My guess is this could be a crime or offence. Or they could log the transaction and look inside, but not doing anything to alter it. This would not be traceable. If this is suspected, the alternative would be to cipher the dns queries. I heard of this, but I don't know if it is possible and how to do it. -- Cheers / Saludos, Carlos E. R. (from 15.1 x86_64 at Telcontar)