![]() Turning this off is as easy as removing the configuration file I had added to /etc/rsyslog. To the bottom of this file, you will want to enter the following lines. Run the following command to edit the config file that tells NUT what UPS to talk to. Rsyslog appears to only be forwarding logs sent through the system (auth, kern, mail, syslog) which is useful – but all of the other log files such as /var/log/pihole.log were not being transported. For NUT to be aware of the UPS connected to your Raspberry Pi, you must modify one of the configuration files. On one hand, seeing all of the sudo actions in one place is useful, but not knowing where they happened was a problem. Unfortunately logwatch combined with rsyslog wasn’t giving me any separation of what was happening where. I setup rsyslog because I wanted to get logwatch to run over my logs and avoid yet another daily automated email arriving. The rest of this post is just details on these 6 changes. Satisfied I’d solved that mystery, along the way I’d also created a list of things to ‘fix’ ![]() This is another thread and different solution to a similar problem. I think this is exactly what this post was describing when it was seeing the error messages. This will fix the first problem, and it seems the second problem was also caused by the same unable to resolve myhost. Where myhost is whatever appears in /etc/hostname. This is a potentially scary DNS recursion problem, but it doesn’t seem to be getting used to forward the lookup of ‘myhost’ to the pi-hole so I’m going to ignore this for now. In short, LEMP uses Linux as the operating system on the device hosting the server, nginx as the server itself, MySQL as a database management system, and PHP for dynamic processing. Since the static configuration doesn’t specify an upstream IPv6 DNS – the ULA for the pi-hole leaks into the configuration. How to set up a web server on the Raspberry Pi To run our web server, we’re using what’s commonly called the LEMP stack: Linux, nginx, MySQL, and PHP. While it’s nice that it just worked, the machine should really be able to resolve its own name without relying on DNS.Īs my network has IPv6 as well, the pi-hole also gets an IPv6 DNS entry. My setup was working fine because the DNS service on my OpenWRT router was covering up this gap. I asked on the forum, – and after a long discussion I came to agree that I fell into a trap.Ī properly configured linux machine will have the name from /etc/hostname also reflected in /etc/hosts (as I have done). I wonder if all pi-hole installations have this challenge. This feels like the pi-hole install script intentionally makes the pi-hole host machine not able to do local DNS resolutions. The pi-hole setup script believes that we should have a static IP and it also has assigned the pi-hole to use DNS servers that are the same DNS servers that I specified as my custom entries for upstream resolution.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |