Skip to content
Search found 7 matches
Search found 7 matches
Page 1 of 1
- by ikappas
- Fri Feb 19, 2021 9:57 pm
- Forum: Viscosity Support (Mac Version)
- Topic: VPN Search Domain being added to resolver #1
- Replies: 9
- Views: 10603
@ James Thank you for your help. I was able to resolve the issue as it was a misconfiguration of the IP (10.0.0.1) instead of the VPN IP (10.0.1.0) which happen to be the same h/w router. Also on MacOS I was unaware that nslookup host.domain.vpn shows different results than dscacheutil -q host -a na...
- by ikappas
- Fri Feb 19, 2021 9:27 pm
- Forum: Viscosity Support (Mac Version)
- Topic: VPN Search Domain being added to resolver #1
- Replies: 9
- Views: 10603
PS: 1. I have tried various combinations with dns cache flushing in between. 2. Also connecting to the servers by IP directly works fine. 3. Don't know if it is relevant, but I have dnsmasq installed via brew with 127.0.0.1 for *.test for dns resolution in /etc/resolver/test file which is displayed ...
- by ikappas
- Fri Feb 19, 2021 9:18 pm
- Forum: Viscosity Support (Mac Version)
- Topic: VPN Search Domain being added to resolver #1
- Replies: 9
- Views: 10603
@ James Thank you for your swift response. If that is the case, there is something else going on with DNS resolution as nslookup/dig/route utility resolves the DNS info from the domail.dhcp instead of domain.vpn on a server.domain.vpn query? Attached is a screenshot with DNS configuration on the con...
- by ikappas
- Fri Feb 19, 2021 8:19 pm
- Forum: Viscosity Support (Mac Version)
- Topic: VPN Search Domain being added to resolver #1
- Replies: 9
- Views: 10603
@James
Just installed 1.9.3b1 (1566) and the issue is still there
Just installed 1.9.3b1 (1566) and the issue is still there
- by ikappas
- Thu Feb 18, 2021 10:24 pm
- Forum: Viscosity Support (Mac Version)
- Topic: VPN Search Domain being added to resolver #1
- Replies: 9
- Views: 10603
@James I have run into the same situation while connecting to a VPN where the VPN defined search domains are pushed to resolver #1 in addition to the ones from DHCP along with an additional resolver entry #2 which points the domain entry to the VPN DNS Server. So scutil --dns shows: DNS configuratio...
- by ikappas
- Wed Mar 14, 2018 3:48 am
- Forum: Viscosity Support (Mac Version)
- Topic: mDNS over tap tunnel not working in 1.7.8 betas
- Replies: 3
- Views: 4806
Hi James,
When I ping MachineName.local I get:
cannot resolve MachineName.local: Unknown host
When I ping MachineName.domain.tld It works properly.
Is there some specific setting that I need to check why the host does not resolve?
Thanks
PS: I use viscosity on a mac book pro over wifi.
When I ping MachineName.local I get:
cannot resolve MachineName.local: Unknown host
When I ping MachineName.domain.tld It works properly.
Is there some specific setting that I need to check why the host does not resolve?
Thanks
PS: I use viscosity on a mac book pro over wifi.
- by ikappas
- Wed Mar 07, 2018 8:03 am
- Forum: Viscosity Support (Mac Version)
- Topic: mDNS over tap tunnel not working in 1.7.8 betas
- Replies: 3
- Views: 4806
I am connecting to our office pfsense via a tap tunnel where we have Avahi installed. mDNS was working before updating to the 1.7.8 betas were I no longer see other computers on my finder when I connect to our VPN. Other than this issue, the connection is working properly and I am able to access rem...
Search found 7 matches
Page 1 of 1