For some reason, I just couldnt see why it was happening, Windows Server 2012 R2 DNS AD DC dns entries just disappearing! It started with one, I clicked refresh, and they all dissapeared.
Sometimes you just need to go back a couple of steps, and remember that you have selected a Filtered View. It was only when adding a test DNS entry, the system said the record was already added, but where!?
Note: written march 2018 but only just published
Using a brand new Raspberry Pi Zero Wireless for the first time, I found the WiFi to be awful.
I used Raspbian Jessie Lite to setup the Pi Zero Wireless with a headless configuration, WiFi details and SSH enabled before the initial boot.
Pi unboxed and put into a nice little case for protection, power plugged up…here we go!
On booting the system the Pi connected to my WiFi and I was able to connect via SSH remotely using the hostname. The connection kept on dropping or hanging, which I thought was slightly strange.
I took a look at my UniFi AP Controller which gives statistics on devices connected, I was shocked to see the strength of the signal between the AP and the Pi flexed from 0% to 5%!?
Grab the lasted Raspbian Lite OS from https://www.raspberrypi.org/downloads/raspbian/ and burn it to an SD card. Once burnt, unmount and remount the SD card with the PC, this allows you to access the removal drive, now named ‘Boot’.
SSH is disabled by default. Place a blank text file with the name ssh onto the root of the SD card:
To add network info you need to create a file called wpa_supplicant.conf and place that in the root SD card .
country=GB
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
network={
ssid="NETWORK-NAME"
psk="NETWORK-PASSWORD"
}In the event of a power outage, an analogue power socket timer switch will simply turn off. When then power returns, the unit is not aware of how long the power has been out for and the timer will continue from when the power cut.
If a digital timer is used, on power being restored, the time should be correct with your on/off schedule preserved.
When using a Linux system (Raspberry Pi) and Cron to set a scheduled task, if a power cut occurred within the time an action was supposed to initiate, this window will be missed as when the system power is restored the action event would have passed and won’t be initiated until the next scheduled time.
For the ARPIC or Linux system to act like a 7 day digital timer a script is used on start up to check the time.
Whilst setting up a new APRIC I noticed that the time was not updating as expected, no update on boot.
I have not setup an RTC on this unit yet, but NTPD would need to be installed anyway to updated the RTC later.
It appears in the Jan 2018 release of Rasbian Lite Stretch does not have NTPD installed as default.
A quick way to check the time and date configuration is to use timedatect1
