On Tue, Mar 07, 2017 at 09:56:23PM +0100, 'Antoine' via qubes-users wrote: > On Mon, Mar 06, 2017 at 04:31:31PM -0800, Andrew David Wong wrote: > > >> Filed a bug report: > > >> > > >> https://github.com/QubesOS/qubes-issues/issues/2674 > > >> > > >> Antoine, you didn't mention which version of Qubes or Debian > > >> you're using, so I assumed Qubes 3.2 and the Debian 8 > > >> TemplateVM. > > > > > > In fact, I am using a Debian 9 TemplateVM. > > > > > > Antoine > > > > > > > Thanks. I've updated the bug report. > > > > However, please note that Debian 8 has gone more extensive testing > > than Debian 9 as a TemplateVM. You may wish to try Debian 8 to see > > whether this resolves your problem. > > I have the same problem with Fedora 23, Debian 8 and Debian 9: > > = Fedora 23 = > [user@work ~]$ grep PRETTY /etc/os-release > PRETTY_NAME="Fedora 23 (Workstation Edition)" > [user@work ~]$ cat /etc/resolv.conf > nameserver 10.137.2.1 > nameserver 10.137.2.254 > [user@work ~]$ dig +short gov.uk @10.137.2.1 > 23.235.33.144 > 23.235.37.144 > [user@work ~]$ dig +short gov.uk @10.137.2.254 > ;; connection timed out; no servers could be reached > > = Debian 8 = > user@cloud:~$ grep PRETTY /etc/os-release > PRETTY_NAME="Debian GNU/Linux 8 (jessie)" > user@cloud:~$ cat /etc/resolv.conf > nameserver 10.137.2.1 > nameserver 10.137.2.254 > user@cloud:~$ dig +short gov.uk @10.137.2.1 > 23.235.33.144 > 23.235.37.144 > user@cloud:~$ dig +short gov.uk @10.137.2.254 > ;; connection timed out; no servers could be reached > > = Debian 9 = > user@Email:~$ grep PRETTY /etc/os-release > PRETTY_NAME="Debian GNU/Linux 9 (stretch)" > user@Email:~$ cat /etc/resolv.conf > nameserver 10.137.2.1 > nameserver 10.137.2.254 > user@Email:~$ dig +short gov.uk @10.137.2.1 > 23.235.33.144 > 23.235.37.144 > user@Email:~$ dig +short gov.uk @10.137.2.254 > ;; connection timed out; no servers could be reached > > Do you have an advise how to remove 10.137.2.254 from the list of > default name servers?
Probaly more relevant would be for you to discover why the first nameserver isnt reachable or isnt responding. With multiple entries they are queried in the order given, so if the first is working correctly the second entry wont be hit. Thats the real problem. . -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20170307210807.GA30418%40thirdeyesecurity.org. For more options, visit https://groups.google.com/d/optout.
