Am 28.07.2020 23:16, schrieb Michael Fischer:
On Tue, Jul 28, Dave Howorth wrote:
On Tue, 28 Jul 2020 12:22:55 -0400 Michael Fischer <michael@visv.net> wrote:
It seems to work when I use dig(1) on something which just failed in the browser, and showed that the vpn's DNS server was used to get the answer. However, I've no idea if FF is using the path to get the resolver.
You're aware that FF can use its own resolution mechanism, as others have said?
And that it does so by default in the US since Feb this year? I don't know where you are.
USA, and yes, thanks to up-thread, I now know this.
Yes, but FF uses its own resolving lib, which is not system based. The mozilla-nss stuff. Might be that it does some caching on the settings. Tries the changed new file, has problems with lookups, falls back to the previous working settings. Just some possibilities what might go on. Do you run "nscd"? This would explain why FF works after dig because the stuff is in cache of nscd after you dig it. Have you tried to restart FF after the resolv.conf has changed? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org