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

Adding default DNS server #6

Closed
kylycht opened this issue Feb 24, 2017 · 8 comments
Closed

Adding default DNS server #6

kylycht opened this issue Feb 24, 2017 · 8 comments
Assignees

Comments

@kylycht
Copy link
Contributor

kylycht commented Feb 24, 2017

There was a problem installing dependencies on a device with our script service
The issue comes with connecting to the repo

Proposed solution is to add a 8.8.8.8 as default DNS server during device init

I am opening this as a discussion since some might think it is a user's responsibility to configure it

Here is issue that was encountered:
{"level":"debug","msg":"Publishing ({\"payload\":{\"name\":\"pre_install\",\"stdout\":\"I run before user application is installed\\nupdate\\nGet:1 http://archive.raspberrypi.org jessie InRelease [22.9 kB]\\nGet:2 http://archive.raspberrypi.org jessie/main armhf Packages [144 kB]\\nGet:3 http://archive.raspberrypi.org jessie/ui armhf Packages [54.8 kB]\\nIgn http://archive.raspberrypi.org jessie/main Translation-en\\nIgn http://archive.raspberrypi.org jessie/ui Translation-en\\nGet:4 http://mirrordirector.raspbian.org jessie InRelease [14.9 kB]\\nErr http://mirrordirector.raspbian.org jessie/main armhf Packages\\n Unable to connect to mirrordirector.raspbian.org:http:\\nErr http://mirrordirector.raspbian.org jessie/contrib armhf Packages\\n Unable to connect to mirrordirector.raspbian.org:http:\\nErr http://mirrordirector.raspbian.org jessie/non-free armhf Packages\\n Unable to connect to mirrordirector.raspbian.org:http:\\nErr http://mirrordirector.raspbian.org jessie/rpi armhf Packages\\n Unable to connect to mirrordirector.raspbian.org:http:\\nErr http://mirrordirector.raspbian.org jessie/contrib Translation-en\\n Unable to connect to mirrordirector.raspbian.org:http:\\nErr http://mirrordirector.raspbian.org jessie/main Translation-en\\n Unable to connect to mirrordirector.raspbian.org:http:\\nErr http://mirrordirector.raspbian.org jessie/non-free Translation-en\\n Unable to connect to mirrordirector.raspbian.org:http:\\nErr http://mirrordirector.raspbian.org jessie/rpi Translation-en\\n Unable to connect to mirrordirector.raspbian.org:http:\\nFetched 237 kB in 4min 1s (981 B/s)\\n\",\"stderr\":\"W: Failed to fetch http://mirrordirector.raspbian.org/raspbian/dists/jessie/main/binary-armhf/Packages Unable to connect to mirrordirector.raspbian.org:http:\\n\\nW: Failed to fetch http://mirrordirector.raspbian.org/raspbian/dists/jessie/contrib/binary-armhf/Packages Unable to connect to mirrordirector.raspbian.org:http:\\n\\nW: Failed to fetch http://mirrordirector.raspbian.org/raspbian/dists/jessie/non-free/binary-armhf/Packages Unable to connect to mirrordirector.raspbian.org:http:\\n\\nW: Failed to fetch http://mirrordirector.raspbian.org/raspbian/dists/jessie/rpi/binary-armhf/Packages Unable to connect to mirrordirector.raspbian.org:http:\\n\\nW: Failed to fetch http://mirrordirector.raspbian.org/raspbian/dists/jessie/contrib/i18n/Translation-en Unable to connect to mirrordirector.raspbian.org:http:\\n\\nW: Failed to fetch http://mirrordirector.raspbian.org/raspbian/dists/jessie/main/i18n/Translation-en Unable to connect to mirrordirector.raspbian.org:http:\\n\\nW: Failed to fetch http://mirrordirector.raspbian.org/raspbian/dists/jessie/non-free/i18n/Translation-en Unable to connect to mirrordirector.raspbian.org:http:\\n\\nW: Failed to fetch http://mirrordirector.raspbian.org/raspbian/dists/jessie/rpi/i18n/Translation-en Unable to connect to mirrordirector.raspbian.org:http:\\n\\nE: Some index files failed to download. They have been ignored, or old ones used instead.\\n\",\"exitCode\":100},\"type\":\"scriptCompleted\"})","time":"2017-02-24T07:13:12Z"}

@bnuriddin
Copy link
Contributor

bnuriddin commented Feb 24, 2017

someone thinks that DNS issue should be resolved on DNS server itself, not on the board.

Device might be running on the network with bad connectivity to Goggle DNS or user running devices in private network and we putting user to the situation where he got no other choice than allowing Goggle DNS, which is not good

@makeupsomething
Copy link
Contributor

Moving this issue to issax main

@kylycht
Copy link
Contributor Author

kylycht commented Feb 24, 2017

And your proposed solution is to leave it up to user to resolve DNS issue?

If you disagree, please add your alternative solution

@makeupsomething
Copy link
Contributor

Issue moved to xshellinc/isaax-main #119 via ZenHub

@dbsparkle dbsparkle reopened this Feb 25, 2017
larenso added a commit that referenced this issue Mar 3, 2017
Refactor code for better go linting, migrate to iotit vboxes

#12 #11 #9 #7 #6
@larenso
Copy link
Contributor

larenso commented Mar 10, 2017

@dbsparkle @kylycht
seems that configs are written only if you configure a board, if you skip this step would you like to configure your board (y/n): n then the secondary dns is not configured

is that ok?

@dbsparkle
Copy link
Contributor

yeah, but lets add option in would you like to configure your board (y/n):y

Something like "Would you like to set a secondary DNS? (y/n):"

And if answer is yes then Enter an IP address for a secondary DNS

#6 (comment)

@larenso
Copy link
Contributor

larenso commented Mar 10, 2017

@dbsparkle I have added 8.8.8.8 as a secondary dns silently, so no need to enter ip address as explained in the description, or should I ask would you like to setup 8.8.8.8 as a secondary dns?

@dbsparkle
Copy link
Contributor

Yeah, user must be aware of that kind of stuff.

#6 (comment)

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

No branches or pull requests

5 participants