Postboot.log reports unresolvable RS domain name

Technical Support
1

Good morning, it would appear there is a Cloudflare configuration issue with a domain name that the most recent update is trying to utilize:

025 329 10:01:07: Cleaning up any dangling Docker data...
2025 329 10:01:07: Starting the FE Config Server
2025 329 10:01:25: adding fallback DNS servers to /etc/resolv.conf file
2025 329 10:01:25: Testing for Internet Access...
environment: line 121: host: command not found
2025 329 10:01:25: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
2025 329 10:01:25: No internet connection found
environment: line 121: host: command not found
2025 329 10:01:25: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
environment: line 121: host: command not found
2025 329 10:01:28: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
environment: line 121: host: command not found
2025 329 10:01:31: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
environment: line 121: host: command not found
2025 329 10:01:34: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
environment: line 121: host: command not found
2025 329 10:01:38: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
environment: line 121: host: command not found
2025 329 10:01:41: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
environment: line 121: host: command not found
2025 329 10:01:44: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
environment: line 121: host: command not found
2025 329 10:01:47: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
environment: line 121: host: command not found
2025 329 10:01:50: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available
environment: line 121: host: command not found
2025 329 10:01:53: Unable to resolve hostname 'raspberryshake.net', most likely no DNS server available

When attempting to go to raspberryshake.net on the browser, Cloudflare is throwing an error to the client: Error 1000: DNS points to prohibited IP.

2

hello BrettC,

thanks for the report. the domain raspberryshake.net is indeed old and is only used for purposes of testing for an internet connection. but, this is not actually the problem your unit is exhibiting.

rather, the command host seems to be not found on your system. this is strange, as it is a basic element of the operating system, i.e., not a program specific to the Shake itself. and, this method of testing access to the internet-at-large has been in place since the first units shipped nine years ago, i.e., nothing in this upgrade modified this part of the code.

would you happen to know why the program /usr/bin/host is missing on your computer, by chance?

thanks in advance for any further info you are able to provide.

cheers,
richard

3

That is a very good question. I’ve gone the route with the “fire and forget” method with the raspberry shake that I have, leaving it to its own all these years. Let me get bind9-host reinstalled on this raspberry pi running RS. I honestly have not a clue why that package is missing. Now I’m curious if i’m missing any other packages.

4

As an update, i’m not sure what has transpired - but ntpsec and bind9-host were both missing. I don’t see anything else missing on this RBPi3 install at this time. Both reinstalled, rebooted for sanity, and once again, live on the map once more. :slight_smile:

1 Like
5

hi,

thanks for the update, glad it was an easy fix. as a follow-up, can you let me know your station name so that i can do some further checks on our side?

thanks in advance,
richard

6

Current station name is RD4B6.

1 Like