Page 1 of 1

DHCP/DNS and home.com issue

Posted: Mon Aug 22, 2011 12:12 pm
by ajssbp
Hi Everyone,

I'm trying to get my hda up and running to my liking, and I'm hitting a bit of a wall. I have another box I use as a router (multi-wan, VERY customizable, firewall, etc.) that also serves as my DNS and DHCP server along with a couple of other servers I use for filestorage and testing purpoess. Long story short, I would like to have the current box continue to be the DNS and DHCP server for my network as I know it is stable and have some settings that would be (seemingly) impossible or very hard to change over to the HDA.

I got the hda to work half-way. I put an entry in the router's DNS table that hda=the hda IP address. So, the links to hda still bring up the Amahi dashboard. However, whenever I click on an installed app, it just takes me to literally home.com, not the app that I want. Is there a way to change this behavior in Amahi (like change the link location for the app)? Is there some way I can change the app link within amahi to still work (ie hda/webcalendar or something similar)? I'm not familiar enough with how and where Amahi stores the apps to figure it out on my own.

Thanks in advance.

Re: DHCP/DNS and home.com issue

Posted: Mon Dec 12, 2011 1:59 pm
by beamer
Well, the answer lies in the result of your choices.

DHCP is not the important issue in this matter. Having 2 DHCP servers in a network, can result in issuing the same IP twice, and the DHCP server will supply the DNS IP to the client.

The hart of your issue is DNS.

The choice, to use home.com, an existing public domain, is not ideal. I would advise you to use a non-existing public domain, like my.home atmy.home home.mine choose a top domain name, that does not exist (yet)
A top domain name is: .edu .com .eu and so on. you can check if the domain exists, by typing it in a browser: http://www.my.home will result in an error, so that would be useful, to use in_house

The advantage of the HDA being the DNS server, is that it will recognize: <service>.<yourdomain> e.g. phpmyadmin.home.com to be local, instead of out in the real world.

If you insist on using the_other_box as your in_house DNS server, you need to add all the <service>.<yourdomain>'s in that DNS server, as well as all aliases you will be using.

Or you use the HDA as your DNS server for the services, and as slave to the_other_DNS_box, changing the HDA's source to the_other_DNS_box using Changing Amahi's DNS , but that does require, that you know what you are doing..