-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Comments
On Wed, Nov 9, 2016 at 10:23 PM limxtop1989 [email protected]
|
Please read this https://peering.google.com/#/learn-more/faq for why you need different DNS. |
if I could get https://peering.google.com/#/learn-more/faq |
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?
The text was updated successfully, but these errors were encountered: