Hi there
Thanks for your replies, it helped pointing me into the correct
direction. As said on the initial post I could navigate with my
browser to http://sub.domain.com:28080/. However the server itself
can't resolve the sub domain 2. I've added it to the hosts file and
will restart the server th
Obviously as the error says you have DNS problem. Apache can not resolve
sub.domain2.com into IP address. Contact who ever is maintaining the DNS
server in your company and ask them to add an alias for
sub.domain2.compointing to the same IP address as
sub.domain1.com.
Igor
On Tue, May 4, 2010 at
You can also resolve it locally on the Suse server in /etc/hosts file if you
know the ip_address of the sub.domain2.com
ip_address subdomain2 sub.domain2.com
and make sure that the name resolution for hosts in the /etc/nsswitch.conf
file is
hosts: files dns
Igor
On Tue, May 4, 2010 at
>
> Contact who ever is maintaining the DNS server in your company and ask them
> to add an alias for sub.domain2.com pointing to the same IP address as
> sub.domain1.com.
>
Actually this is wrong. Should be contact who ever is maintaining the DNS
server in your company and ask them to add proper
Good day there.
I'm using mod_proxy to redirect trafic to java applications running on
JBoss instances. I have 3 JBoss instances running seperate apps, the
redirects of 2 of these works fine with mod_proxy configuration but
the third doesn't.
The first 2 instances where set up a long time ago. I'