Amahi DNS loses ALL entries

[pmccarty]

Hey!

I've had this issue with Amahi from the beginning - it has recently become critical potentially requiring me to use another DHCP/DNS solution.

I normally have approximately 30 or 35 entries on my http://hda.home.com/setup?sub=dhcp&tab=network page. Then, unexpectedly, all name resolution on my network fails. If I return to the above page or refresh it if it is open I have no entries. None. I can still resolve to hda.home.com but that is it.

I have no other DHCP server, nor any other DNS server in my network. Being in technology I've checked all the obvious things I can find and a few of the not so obvious. The only symptom is the loss of name resolution. Rebooting the clients or restarting the networking on them will cause them to re-register, appear on the above page, and resolve to that device. Obviously, I can't reboot 30 to 35 devices several times an hour.

Just as I lose all name resolution the following is logged in /var/named/data/named.run:

running
received control channel command 'freeze home.com'
freezing zone 'home.com/IN' internal: success
received control channel command 'freeze 1.168.192.in-addr.arpa'
freezing zone '1.168.192.in-addr.arpa/IN' internal: success
received control channel command 'thaw home.com'
thawing zone 'home.com/IN' internal: success
received control channel command 'thaw 1.168.192.in-addr.arpa'
thawing zone '1.168.192.in-addr.arpa/IN' internal: success
received control channel command 'stop'
shutting down: flushing changes
stopping command channel on 127.0.0.1#953
stopping command channel on ::1#953
no longer listening on 127.0.0.1#53
no longer listening on 192.168.1.204#53
no longer listening on ::1#53
exiting
zone 1.168.192.in-addr.arpa/IN/internal: loaded serial 1207252203
zone home.com/IN/internal: loaded serial 1207252203
managed-keys-zone ./IN/internal: loading from master file 3bed2cb3a3acf7b6a8ef408420cc682d5520e26976d354254f528c965612054f.mkeys failed: file not found
managed-keys-zone ./IN/internal: loaded serial 0
running

The log then shows devices re-registering.

I would appreciate any help you can provide as this has plagued me for months. Because of some work I am doing this has become a critical issue with Amahi.

Best regards,

Patrick

[bigfoot65]

Have you checked the network troubleshooter? Also, are you using the HDA solely for DHCP and DNS?

http://wiki.amahi.org/index.php/Network_troubleshooting

[pmccarty]

Thank you for your response!

Yes, it is the only DHCP/DNS server in my environment and yes, I've used the network troubleshooter many times.

One of the ways I've managed is to set the lease duration down to 30 minutes - so I have at most a 30 period before all the devices re-establish their lease. This is not ideal but gets me around the issue.

Best,

Patrick

[bigfoot65]

Might consider setting static IP address for each client via dashboard.

[ Post made via Android ]