@jedisct1 You may want to warn macOS users to set block_unqualified to false if they are using a VPN client. It seams on macOS, a new network interface needs to set up an unqualified dns domain for lookups and bonjour. Thanks to @sparklabs for pointing me the right direction!
-
-
If I set it to true, I can't connect using protonvpn and they are listed in the nx.log, if I set it to false everything is fine. I couldn't lookup db._dns-sd._udp.utun10.viscosity using WhatRoute also.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
The work around was shutting down my Mac, wait a 10 seconds and start up. With just restarting, I would get the same problem, Viscosity trying to connect endlessly.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Here are some A querries: [2020-02-03 17:49:03]127.0.0.1gsgpzeaqol.utun10.viscosityA [2020-02-03 17:49:03]127.0.0.1zwyjoazytw.utun10.viscosityA [2020-02-03 17:49:03]127.0.0.1vnhuumdgkfmmz.utun10.viscosity
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
here is James' response "utunXX.viscosity” is the generic default domain name assigned to the VPN network interface if a DNS domain isn’t specified (i.e. either in Viscosity or pushed by the VPN server).
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
A DNS domain must be assigned to the interface for DNS lookups (including Bonjour lookups) to work correctly on macOS, and so Viscosity will set a generic one if required.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.