08-30-2020 08:52 AM
Discovered this morning that some web sites cannot be reached. However, if I fire up my VPN all is fine.
I have rebooted my laptop and the Ignite modem, but no difference.Anyone experiencing this?
An example:
1. No VPN running
C:\>ping grc.com
Ping request could not find host grc.com. Please check the name and try again.
C:\>
2. With VPN active
C:\>ping grc.com
Pinging grc.com [4.79.142.200] with 32 bytes of data:
Reply from 4.79.142.200: bytes=32 time=114ms TTL=241
Reply from 4.79.142.200: bytes=32 time=208ms TTL=241
Reply from 4.79.142.200: bytes=32 time=217ms TTL=241
Reply from 4.79.142.200: bytes=32 time=215ms TTL=241
Ping statistics for 4.79.142.200:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 114ms, Maximum = 217ms, Average = 188ms
C:\>
Solved! Solved! Go to Solution.
08-30-2020 11:21 AM
All working now.
08-30-2020 09:18 AM - edited 08-30-2020 09:34 AM
@Bplayer Could this be related to recent issues brought up in this thread? Ignite Parental Controls and Protected Browsing use DNS to restrict network access. Using a VPN will bypass all of those protections.
Protected Browsing has also been known to cause strange connectivity problems sometimes, especially when it blocks access to non-malicious sites or blocks access to 3rd-party domains that a site relies on. Do you have it enabled in the Ignite WiFi Hub?
If the Ignite Gateway is blocking sites even when Parental Controls and Protected Browsing are disabled, that's a bigger problem.
08-30-2020 09:58 AM
Parental Controls and Protected Browsing have always been disabled here.
It is strange as most sites are available, except for two. One is US and the other in UK:
grc.com
bbc.co.uk
Looks like the DNS is messed up.
08-30-2020 10:26 AM - edited 08-30-2020 10:32 AM
@Bplayer wrote:
Parental Controls and Protected Browsing have always been disabled here.
It is strange as most sites are available, except for two. One is US and the other in UK:
grc.combbc.co.uk
Looks like the DNS is messed up.
Yup, but grc.com also fails to resolve using other servers, not just the Rogers DNS server:
$ nslookup
> server 8.8.8.8
Default server: 8.8.8.8
Address: 8.8.8.8#53
> grc.com
Server: 8.8.8.8
Address: 8.8.8.8#53
** server can't find grc.com: SERVFAIL
> server 9.9.9.9
Default server: 9.9.9.9
Address: 9.9.9.9#53
> grc.com
Server: 9.9.9.9
Address: 9.9.9.9#53
** server can't find grc.com: SERVFAIL
> server 1.1.1.1
Default server: 1.1.1.1
Address: 1.1.1.1#53
> grc.com
Server: 1.1.1.1
Address: 1.1.1.1#53
Non-authoritative answer:
Name: grc.com
Address: 4.79.142.200
> server 64.71.255.204
Default server: 64.71.255.204
Address: 64.71.255.204#53
> grc.com
Server: 64.71.255.204
Address: 64.71.255.204#53
** server can't find grc.com: SERVFAIL
>
08-30-2020 11:21 AM
All working now.