I'm not sure how to do that. I have tried a couple of methods I Googled but they didn't seem to stick.
After some more Googling and a bit of searching I have found /etc/resolvconf.conf which has an entry for DNS. It seems to survive a reboot. Have to see if it holds up, I have set it for 1.1.1.1
@Lee Armstrong
I've reached a bit of a dilemma now, Running Planefinder on a PiAware system it's impossible to keep both running with my ISPs DNS problem.
FlightAware uses Google DNS that bypasses my ISPs problem. Planefinder uses my router (my iSPs DNS) and this will fail every few hours. I...
Seems to be running OK at the moment, the DNS is holding but the Planefinder feeder stopped with the error "Setting NTP sync state to unsynced".
I had to restart pfclient to continue.
Thanks Lee, I looked at Cloudflare and will give it a try. I have edited /etc/dhcp/dhclient.conf in the Pi as follows:
#prepend domain-name-servers 1.1.1.1,1.0.0.1;
I hope that will do the job.
I have a problem currently with my ISP that causes the router to lose the DNS every day, when this happens the Planefinder feeder stops. I have changed all my devices in the house to use Google (8.8.8.8) and they are unaffected. I cannot change DNS in the router as it is locked out.
Can I...
I have managed to access the configuration now. I restarted the Pi and quit Chrome and reloaded it. Now it lets me in. Nothing in the logs to indicate a problem. I'll keep an eye on it and raise a ticket if it happens again.
Yes, mine has rolled back now. The errors were the usual "Failed to open connection (errno 111) but they were constant with the normal uploads in between. Normally I would see one or two of these a day. What was the update for?
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.