Skip to content
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

output warnings directly after running auto.sh #100

Closed
limxtop1989 opened this issue Nov 9, 2016 · 3 comments
Closed

output warnings directly after running auto.sh #100

limxtop1989 opened this issue Nov 9, 2016 · 3 comments

Comments

@limxtop1989
Copy link

Question 1
output warnings directly:
limxtop@IdeaPad:~/bin/google-hosts/scripts$ ./auto.sh
[WARNING] *.google.com
[WARNING] accounts.google.com
[WARNING] checkout.google.com
[WARNING] adwords.google.com
[WARNING] mail.google.com
[WARNING] *.mail.google.com
[WARNING] *.googleusercontent.com
[WARNING] *.gstatic.com
[WARNING] *.googleapis.com
[WARNING] *.appspot.com
[WARNING] *.googlecode.com
[WARNING] *.google-analytics.com
[WARNING] ssl.google-analytics.com

This is the content of /etc/resolv.conf file:
nameserver 127.0.0.1
search DHCP HOST

Question 2:
How to make sure that I use google DNS or open DNS? I made the content of /etc/resolv.conf file to be
nameserver 8.8.8.8
nameserver 8.8.4.4
search DHCP HOST

and run auto.sh for a couple of hours, finally copy generated hosts file to cover the hosts file in /etc. but I can't access https:www.google.com still. where is the problem?

suggestion
why not create a FQA file or describe more clearly how to use it?

@txthinking
Copy link
Owner

On Wed, Nov 9, 2016 at 10:23 PM limxtop1989 [email protected]
wrote:

Question 1
output warnings directly:
limxtop@IdeaPad:~/bin/google-hosts/scripts$ ./auto.sh
[WARNING] *.google.com
[WARNING] accounts.google.com
[WARNING] checkout.google.com
[WARNING] adwords.google.com
[WARNING] mail.google.com
[WARNING] *.mail.google.com
[WARNING] *.googleusercontent.com
[WARNING] *.gstatic.com
[WARNING] *.googleapis.com
[WARNING] *.appspot.com
[WARNING] *.googlecode.com
[WARNING] *.google-analytics.com
[WARNING] ssl.google-analytics.com

This is the content of /etc/resolv.conf file:
nameserver 127.0.0.1
search DHCP HOST

This auto.sh script find IP from this IP POOL: $ nslookup -q=TXT _
netblocks.google.com 8.8.4.4. IP may be all dead.
Then:
You need find IP from OTHER POOL and don't make it public.
or use other proxy.

Question 2:
How to make sure that I use google DNS or open DNS? I made the content of
/etc/resolv.conf file to be

$ nslookup [ENTER]
server [ENTER]

nameserver 8.8.8.8
nameserver 8.8.4.4
search DHCP HOST

and run auto.sh for a couple of hours, finally copy generated hosts file
to cover the hosts file in /etc. but I can't access https:www.google.com
still. where is the problem?

suggestion
why not create a FQA file or describe more clearly how to use it?—

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#100, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ABLyz49zVns4L-EdxoW1mnBeCzJOylbFks5q8dSXgaJpZM4KtkjP
.

txthinking added a commit that referenced this issue Nov 10, 2016
@txthinking
Copy link
Owner

Please read this https://peering.google.com/#/learn-more/faq for why you need different DNS.

@qiuzhongrun
Copy link

qiuzhongrun commented Nov 15, 2016

if I could get https://peering.google.com/#/learn-more/faq
why do I need hosts...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants