DHCP/DNS oddity
Posted: Fri Apr 01, 2011 9:34 am
I have several machines with static IPs on my network, plus a couple that use DHCP.
I've hit a couple of oddities in Amahai's handling of DHCP/DNS which I really don't understand.
First, the machine called box2. This is a desktop machine, using DHCP. For some reason, Amahi has not picked up its hostname, and shows it as a static IP (192.168.1.109) and gives it the name h109.
Second, I'm experimenting with a new server - its an SMS machine (http://sms.it-ccs.com/), which I want for a customer. I've reinstalled it a couple of times, and set it up as a static IP in the Amahi dashboard. On the last reinstall, I inadvertently changed its hostname, so I went into the Amahi Dashboard, deleted the original static IP and recreated it with the new hostname. However, I had to restart the Amahi server before the new hostname was propagated to the network. Even from the Amahi machine, I could not resolve the new hostname.
Another oddity - at the moment, I'm using my laptop (wireless connection, using DHCP), but, even though the Amahi machine is both DHCP and DNS server, the Amahi Dashboard is showing no DHCP clients, and doesn't seem to recognize the laptop at all (even though I'm logging in from it...).
Is there a way of flushing the DNS cache so that things like the newly assigned static IP are propagated (without restarting the Amahi machine)? Also, is there a way of preventing the Dashboard from losing track of the DHCP clients?
Paul.
I've hit a couple of oddities in Amahai's handling of DHCP/DNS which I really don't understand.
First, the machine called box2. This is a desktop machine, using DHCP. For some reason, Amahi has not picked up its hostname, and shows it as a static IP (192.168.1.109) and gives it the name h109.
Second, I'm experimenting with a new server - its an SMS machine (http://sms.it-ccs.com/), which I want for a customer. I've reinstalled it a couple of times, and set it up as a static IP in the Amahi dashboard. On the last reinstall, I inadvertently changed its hostname, so I went into the Amahi Dashboard, deleted the original static IP and recreated it with the new hostname. However, I had to restart the Amahi server before the new hostname was propagated to the network. Even from the Amahi machine, I could not resolve the new hostname.
Another oddity - at the moment, I'm using my laptop (wireless connection, using DHCP), but, even though the Amahi machine is both DHCP and DNS server, the Amahi Dashboard is showing no DHCP clients, and doesn't seem to recognize the laptop at all (even though I'm logging in from it...).
Is there a way of flushing the DNS cache so that things like the newly assigned static IP are propagated (without restarting the Amahi machine)? Also, is there a way of preventing the Dashboard from losing track of the DHCP clients?
Paul.