I have recently replaced my WHS with Amahi and need to change the DHCP scope. Currently it defaults to 192.168.0.100 - 192.168.0.254 every time it reboots. I need it to be 192.168.0.192 - 192.168.0.254 because I have IP conflicts below x.x.x.192.
Also, the DHCP clients should be able to resolve via the Amahi DNS server, correct? It doesn't seem to be resolving them. Could the File not found message below be causing that?
Apr 2 18:50:27 hda named[2114]: generating session key for dynamic DNS
Apr 2 18:50:27 hda named[2114]: set up managed keys zone for view internal, file '3bed2cb3a3acf7b6a8ef408420cc682d5520e26976d354254f528c965612054f.mkeys'
Apr 2 18:50:27 hda named[2114]: command channel listening on 127.0.0.1#953
Apr 2 18:50:27 hda named[2114]: command channel listening on ::1#953
Apr 2 18:50:27 hda named[2114]: the working directory is not writable
Apr 2 18:50:27 hda named[2114]: zone 0.168.192.in-addr.arpa/IN/internal: loaded serial 1103022250
Apr 2 18:50:27 hda named[2114]: zone home.local/IN/internal: loaded serial 1103022250
Apr 2 18:50:27 hda named[2114]: managed-keys-zone ./IN/internal: loading from master file 3bed2cb3a3acf7b6a8ef408420cc682d5520e26976d354254f528c965612054f.mkeys failed: file not found
Apr 2 18:50:27 hda named[2114]: managed-keys-zone ./IN/internal: loaded serial 0
Apr 2 18:50:27 hda named[2114]: running
Any help would be greatly appreciated.
Thanks...
Modify DHCP Scope and Client DNS Resolution
Re: Modify DHCP Scope and Client DNS Resolution
Any guidance would be greatly appreciated. Thanks...
Who is online
Users browsing this forum: No registered users and 4 guests