DNS works but sort of does not...
Posted: Sat Jul 03, 2010 4:05 pm
Hey people,
First fantastic bit of software and getting stronger all the time .
I have to confess, I like WHS2 and use it for audio and video, mainly because the Amahi video software does not install, but that is not the question here.
I need some help with the dns, it got me stumped and I am close to insanity (I try the same thing over and over in the hope it will change).
Environment:
All servers/software is install as a VMWare instance on a windows 2008R2 standard server. No DNS/DHCP etc installed on windows 2008R2 server.
- Ahami server on its own vminstance (ip x.x.x.213
- gallery installed (gallery2)
- ajaxexplorer installed (ajax)
- webmin installed (webmin)
- WHS2 on its own vminstance (whs) (ip x.x.x.206), amahi knows about it and has an alias setup of whs.home.com to ip x.x.x.206
I am using the standard home.com doman for internal use, and have my own external domains <mydomain>.
Scenario:
http://gallery2.home.com gives me the gallery webpage, same if i use http://gallery2.
This applies for all ahami installed apps, so that is good. This shows that the routing from <mydomain> works.
http://whs.home.com gives me the Window$ home$erver login page. This shows that it is working on the internal network and the alias is know.
http://whs. gives me the amahi login screen instead of the whs login screen.
Sum up:
Amahi installed applications work, routing to another IP (outside the amai vmware instance) does not work. Why is that as amahi is controlling the dns.
How can i change the amahi dns to route http://whs. to http://whs.home.com? I want to type http://whs. from an external network and end up with the whs login prompt, not the amahi login prompt.
Yeah I am a n00b when it comes to this, but you have to learn some how.
Thanks
H.
First fantastic bit of software and getting stronger all the time .
I have to confess, I like WHS2 and use it for audio and video, mainly because the Amahi video software does not install, but that is not the question here.
I need some help with the dns, it got me stumped and I am close to insanity (I try the same thing over and over in the hope it will change).
Environment:
All servers/software is install as a VMWare instance on a windows 2008R2 standard server. No DNS/DHCP etc installed on windows 2008R2 server.
- Ahami server on its own vminstance (ip x.x.x.213
- gallery installed (gallery2)
- ajaxexplorer installed (ajax)
- webmin installed (webmin)
- WHS2 on its own vminstance (whs) (ip x.x.x.206), amahi knows about it and has an alias setup of whs.home.com to ip x.x.x.206
I am using the standard home.com doman for internal use, and have my own external domains <mydomain>.
Scenario:
http://gallery2.home.com gives me the gallery webpage, same if i use http://gallery2.
This applies for all ahami installed apps, so that is good. This shows that the routing from <mydomain> works.
http://whs.home.com gives me the Window$ home$erver login page. This shows that it is working on the internal network and the alias is know.
http://whs. gives me the amahi login screen instead of the whs login screen.
Sum up:
Amahi installed applications work, routing to another IP (outside the amai vmware instance) does not work. Why is that as amahi is controlling the dns.
How can i change the amahi dns to route http://whs. to http://whs.home.com? I want to type http://whs. from an external network and end up with the whs login prompt, not the amahi login prompt.
Yeah I am a n00b when it comes to this, but you have to learn some how.
Thanks
H.