-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Google Drive getting blocked #7
Comments
What version of Pi-hole are you using? My guess is something went wrong and *.google.com was wildcarded. I will look into this for you when I have some free time 😊
From: Ben <notifications@github.com>
Reply-To: jaykepeters/PSS <reply@reply.github.com>
Date: Wednesday, February 26, 2020 at 11:48 PM
To: jaykepeters/PSS <PSS@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [jaykepeters/PSS] Google Drive getting blocked (#7)
Not sure exactly how, but when I apply this, drive.google.com gets blocked.
macbookpro:~ kupan787$ nslookup drive.google.com
;; Got SERVFAIL reply from 2601:204:ca00:f61:8787:7fd6:1b90:23d1, trying next server
;; Got SERVFAIL reply from 2601:204:ca00:f61:62aa:c8c2:e695:fb4b, trying next server
Server: 10.100.1.2
Address: 10.100.1.2#53
** server can't find drive.google.com: SERVFAIL
As soon as I remove what this script did, Google Drive starts working again.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
I’m still on the 4.x version.
I’m going to dig in as well. I get weird results when doing nalookup on any google domain from the Pihole.
If it matters, I’m using Unbound with my pihole.
|
Thanks! I would investigate as much as you can on your end. Maybe something is wrong between unbound and Pi-hole? How does that work? I have never setup Pi-hole in that fasion…
Best regards,
Jayke
From: Ben <notifications@github.com>
Reply-To: jaykepeters/PSS <reply@reply.github.com>
Date: Thursday, February 27, 2020 at 12:29 AM
To: jaykepeters/PSS <PSS@noreply.github.com>
Cc: Jayke Peters <jaykepeters@gmail.com>, Comment <comment@noreply.github.com>
Subject: Re: [jaykepeters/PSS] Google Drive getting blocked (#7)
I’m still on the 4.x version.
I’m going to dig in as well. I get weird results when doing nalookup on any google domain from the Pihole.
If it matters, I’m using Unbound with my pihole.
Thanks,
Ben Mackin
Sent from my iPhone
On Feb 26, 2020, at 9:50 PM, Jayke Peters ***@***.***> wrote:
What version of Pi-hole are you using? My guess is something went wrong and *.google.com was wildcarded. I will look into this for you when I have some free time 😊
From: Ben ***@***.***>
Reply-To: jaykepeters/PSS ***@***.***>
Date: Wednesday, February 26, 2020 at 11:48 PM
To: jaykepeters/PSS ***@***.***>
Cc: Subscribed ***@***.***>
Subject: [jaykepeters/PSS] Google Drive getting blocked (#7)
Not sure exactly how, but when I apply this, drive.google.com gets blocked.
macbookpro:~ kupan787$ nslookup drive.google.com
;; Got SERVFAIL reply from 2601:204:ca00:f61:8787:7fd6:1b90:23d1, trying next server
;; Got SERVFAIL reply from 2601:204:ca00:f61:62aa:c8c2:e695:fb4b, trying next server
Server: 10.100.1.2
Address: 10.100.1.2#53
** server can't find drive.google.com: SERVFAIL
As soon as I remove what this script did, Google Drive starts working again.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
https://docs.pi-hole.net/guides/unbound/
The setup has worked great for me for awhile now.
I’ll dig in tomorrow, and let you know if I figure it out.
|
Sounds good!
From: Ben <notifications@github.com>
Reply-To: jaykepeters/PSS <reply@reply.github.com>
Date: Thursday, February 27, 2020 at 12:52 AM
To: jaykepeters/PSS <PSS@noreply.github.com>
Cc: Jayke Peters <jaykepeters@gmail.com>, Comment <comment@noreply.github.com>
Subject: Re: [jaykepeters/PSS] Google Drive getting blocked (#7)
https://docs.pi-hole.net/guides/unbound/
The setup has worked great for me for awhile now.
I’ll dig in tomorrow, and let you know if I figure it out.
Thanks,
Ben Mackin
Sent from my iPhone
On Feb 26, 2020, at 10:50 PM, Jayke Peters ***@***.***> wrote:
Thanks! I would investigate as much as you can on your end. Maybe something is wrong between unbound and Pi-hole? How does that work? I have never setup Pi-hole in that fasion…
Best regards,
Jayke
From: Ben ***@***.***>
Reply-To: jaykepeters/PSS ***@***.***>
Date: Thursday, February 27, 2020 at 12:29 AM
To: jaykepeters/PSS ***@***.***>
Cc: Jayke Peters ***@***.***>, Comment ***@***.***>
Subject: Re: [jaykepeters/PSS] Google Drive getting blocked (#7)
I’m still on the 4.x version.
I’m going to dig in as well. I get weird results when doing nalookup on any google domain from the Pihole.
If it matters, I’m using Unbound with my pihole.
Thanks,
Ben Mackin
Sent from my iPhone
> On Feb 26, 2020, at 9:50 PM, Jayke Peters ***@***.***> wrote:
>
> What version of Pi-hole are you using? My guess is something went wrong and *.google.com was wildcarded. I will look into this for you when I have some free time 😊
>
> From: Ben ***@***.***>
> Reply-To: jaykepeters/PSS ***@***.***>
> Date: Wednesday, February 26, 2020 at 11:48 PM
> To: jaykepeters/PSS ***@***.***>
> Cc: Subscribed ***@***.***>
> Subject: [jaykepeters/PSS] Google Drive getting blocked (#7)
>
>
>
> Not sure exactly how, but when I apply this, drive.google.com gets blocked.
> macbookpro:~ kupan787$ nslookup drive.google.com
> ;; Got SERVFAIL reply from 2601:204:ca00:f61:8787:7fd6:1b90:23d1, trying next server
> ;; Got SERVFAIL reply from 2601:204:ca00:f61:62aa:c8c2:e695:fb4b, trying next server
> Server: 10.100.1.2
> Address: 10.100.1.2#53
>
> ** server can't find drive.google.com: SERVFAIL
> As soon as I remove what this script did, Google Drive starts working again.
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub, or unsubscribe.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Not sure exactly how, but when I apply this, drive.google.com gets blocked.
As soon as I remove what this script did, Google Drive starts working again.
The text was updated successfully, but these errors were encountered: