Networking In General

[Riptexious]

had some challenges.

[Riptexious]

Here are my questions: I'm am sure that there is an explanation somewhere; either on the wiki or in the mail list archive. Regardless, it should be cross posted here, so I'll pose the questions anyway.

I do not have a declared domain name anywhere configured on my Router; that I know of. So, following my own logic train: If my router is providing DNS services (which it is for my clients to reach outside my network), I am going to assume that it can also do this for for my internal clients as well. (e.g. it would tell my vista client that http:\\hda belongs to server 10.220.6.26. Or so, I would have thought. When I type http:\\hda, my browser re-writes the string to http:\\www.hda.com and sends me off into nether-space. This is where I'm a bit confused. So... What I did to get access to http:\\hda (internal IP 10.220.6.26) was set up my hosts file on my client box as: '10.220.6.26 hda'. How do I get my router to do this for me?


With the hosts entry, I can successfully nav to http:\\hda, the Amahi server comes up. However,... If I then attempt to access one of the web apps such as http:\\wiki ~ my browser on the client machine reactors the entry for me to: http:\\www.wiki.com. Logic train derailed.

I guess I just do not understand my networking.

[Riptexious]

http://www.amahi.org/faq#is-the-hda-sup ... me-network

Ok, so this is going to be a bit of self discovery here. The link above is to the wiki (yea!). Problem is, I'm running Amahi in a VM on my Vista box, so I can't rely on it for DNS. I am, however figuring out that I'm going to need to set some static routes to get this to work across all machines.

I'll keep posting here until I figure this out. Feel free to comment.

[Riptexious]

Ok. So my network problems were related to the fact that my HDA needs to be the primary DNS server / Router. Since I'm running in a virtual machine, on an existing Vista machine, dedicating it really isn't an option.

Instead, I modified the hosts file

Here are the entries I needed thus far:
10.220.6.26 hda
10.220.6.26 wiki
10.220.6.26 webcal
10.220.6.26 setup
10.220.6.26 zina

[devauto]

Ok. So my network problems were related to the fact that my HDA needs to be the primary DNS server / Router. Since I'm running in a virtual machine, on an existing Vista machine, dedicating it really isn't an option.

Instead, I modified the hosts file

Here are the entries I needed thus far:
10.220.6.26 hda
10.220.6.26 wiki
10.220.6.26 webcal
10.220.6.26 setup
10.220.6.26 zina

Okay, using the hosts file does work, but as things change, it could get more and more complex and harder to maintain all the separate aliases. My router has a secondary set of DNS settings specifically for the internal network, I added the HDA IP address as the primary DNS server here, and now all internal DNS lookups come from the HDA. External DNS does not seem to be affected and life is good. Another method, if your router does not have internal DNS support, is to set the router's primary DNS server to the HDA box. The problem is this, if the secondary DNS server goes off-line for whatever reason, then you have no external DNS support.

[cpg]

by the way, we're working on a "router/gateway" control module. it should make sorting this situation easier in the future.