Skip to main content

DNS and Organisational Planning

I fixed up my DNS server last week. Its really strange how organisations can still rely on hosts file for name resolution. What was even more amazing was that I just accepted that for almost 2 years. When the network change and you realise that its a real pain to make changes and you start wondering who's bright idea it was to use the hosts file in the first place and of course its always easier to for people to blame the guy who's not there.

So whats the big deal with running a DNS server anyway? Its not a big overhead to create a functional a workgroup DNS server, unless of course, its some windows thing that need to log into some domain that requires some auto population something that caches some hosts to some server that needs to be assessible via some funny port across the intranet, etc? No doubt windows can also do a simplified version, but in a typical organisation setup, policies determine logic. Mind you that common sense normally means that logic should dictate policy. But in the burocratic enviornment who cares if things just dont make any sense?

If you are wondering why fully "featured" management applications are so expensive, it is probably because they are banking on the fact that there is no planning made by system mangers who are more than willing to spend the extra cash to hide their ignorance, thinking the package can do their work for them. I'm sure you heard the saying "a computer is only as good as the user". In my experience, most system managers purely have no understanding on how the system works and I dont mean by the book definition on what the system is.

So is planning that difficult? A tour guide out in the bush told me things dont need to be complicated to do stuff. I think that might explain some of the many interesting inventions here that are so cool, but taken out of context, just look like really strange objects. The umbrella clothes rack which is a real big hit here and the shoo roo, a car mounted whistle to shoo kangaroos from hitting your car. One of the greater signature inventions out in the bush is the "stick to check rock movement", which is actually a stick to check rock movement.

Apparently some scientists have debated how to check if lava tubes were unstable and prone to collapsing. Some suggested using all types of sensors, but I was told it was an aussie who stuck a stick against the wall and said that will work.

Comments

Popular posts from this blog

Multiple Broadlink RM mini 3 integration using MQTT

Broadlink now has quite a lot of integration options almost out of the box. If you enable Broadlink IHC, you can directly link it to Alexa by giving the device a unique name.

There is a homebridge plug in for homekit integration but I haven't tried or tested this. https://lprhodes.github.io/slate/

I wanted to put the device in domoticz so I can have more control over what can trigger my broadlink. I decided to use broadlink-mqtt for this, which is a fairly easy method to trigger from any source.

Setup Instructions for broadlink-mqtt

1. git clone https://github.com/eschava/broadlink-mqtt

2. vi /home/pi/broadlink-mqtt/mqtt.conf

3. Update the mqtt.conf file with the device type set as multiple_lookup

device_type = 'multiple_lookup'
mqtt_multiple_subprefix_format = '{type}_{mac_nic}/'
4. Start the python script and check that it started and detected all the RM devices.
Check the log file to see what the IP / MAC addresses are. DEBUG Connected to RM2 Broadlink device at …

Fibaro HCL Virtual Device Slider

How to setup Fibaro home center lite (HCL) slider for virtual devices.

As the Fibaro HCL does not support LUA. The question was how to update the number value of the slider to send to the HTTP string. Thanks to this site which is a really good reference https://www.vesternet.com/resources/application-notes/apnt-88/

The 2 use cases here are;

Sonos HTTP API Volume

To allow for volume control for all Sonos devices, add a virtual device with the IP address for SONOS HTTP API and specify the default port to 5005. Create Slider and put the following text into the string.

GET /volume/_sliderValue_ HTTP/1.10x0D0x0A0x0D0x0A


Domotiz Virtual Devices

GET /json.htm?type=command&param=switchlight&idx=XX&switchcmd=Set%20Level&level=_sliderValue_ HTTP/1.10x0D0x0A0x0D0x0A

Replace XX with the device ID.

Restart Fibaro HCL when it stops working automatically

It seems that the Fibaro HCL seems to hang every now and then. Instead of trying to restart it regularly, which doesn't really work, as it's almost impossible to predict when this will happen.

This method checks that the HCL is actually running and in the event it stops working, trigger a script that will restart it.


1. Get a non Fibaro controlled power plug and scripts to control it.

I used a wifi smart plug, TP-link HS100 and downloaded the scripts from

https://blog.georgovassilis.com/2016/05/07/controlling-the-tp-link-hs100-wi-fi-smart-plug/

2. Create a bash script to restart the Fibaro, e.g. restart_fibaro.sh

#!/bin/bash

ip_addr=
scripts=

$scripts/tplink-smartplug.py -t $ip_addr -c off
sleep 10
$scripts/tplink-smartplug.py -t $ip_addr -c on


3. Create a test global variable in the Fibaro HCL

Go to the variables panel and create a test variable, e.g. Test


4. Add a cron entry to test that the Fibaro API is still working and restart if it's not.

The cron script is scheduled ev…