[jitsi-users] How to force an alternate DNS resolver? Jitsi fails resolving


#1

Thank you, Marious. But sorry I wasn't clear enough: I have erased the previous name server address, and left only
the new one. Here is the entire /run/resolvconf/resolv.conf file:

   > # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
   > # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
   > nameserver 127.0.0.2

and still, dig works fine (uses the 127.0.0.2 name server address, and succeeds in
resolving), but Jitsi fails. How can this be fixed?


#2

Do you also have a file /etc/resolv.conf ?

If yes, do the contents differ from the above "nameserver 127.0.0.2"?

Antony.

···

On Thursday 04 February 2016 at 00:18:51, Hsu Tsai wrote:

Thank you, Marious. But sorry I wasn't clear enough: I have erased the
previous name server address, and left only

the new one. Here is the entire /run/resolvconf/resolv.conf file:

> # Dynamic resolv.conf(5) file for glibc resolver(3) generated by
> resolvconf(8)
> # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
> nameserver 127.0.0.2

and still, dig works fine (uses the 127.0.0.2 name server address, and
succeeds in resolving), but Jitsi fails.

--
Bill Gates has personally assured the Spanish Academy that he will never allow
the upside-down question mark to disappear from Microsoft word-processing
programs, which must be reassuring for millions of Spanish-speaking people,
though just a piddling afterthought as far as he's concerned.

- Lynne Truss, "Eats, Shoots and Leaves"

                                                   Please reply to the list;
                                                         please *don't* CC me.