DNS :(

[fubar]

Hi

This is my setup:

scalix-server-11.0.2.17-1.fc5
scalix-swa-11.0.2.23-1
scalix-tomcat-connector-11.0.0.181-1.fc5
scalix-postgres-11.0.2.23-1
scalix-res-11.0.2.23-1
scalix-sac-11.0.2.23-1
scalix-mobile-11.0.2.23-1
scalix-tomcat-5.5.16-195
scalix-platform-11.0.2.23-1
scalix-sis-11.0.2.23-1

/etc/hosts:

127.0.0.1 localhost.localdomain
196.41.12.100 mail.theproshop.co.za mail

I can access /sac and /webmail from the outside world however this box also has an internal IP of 10.1.1.6. From inside my network I can't access http://10.1.1.6/webmail or /sac. We have Windows 2003 domain controllers which server DNS to the clients. if anybody knows how I can access these links internally that would be great!

[jcaudell]

The webserver may not be listening on the second interface you have configured internally (the 10.1.1.6 ip). You will need to have apache listen for connections on both interfaces I believe. Are you able to connect internally to 196.41.12.100?

[fubar]

Silly me, this is how I solved it.

In /etc/opt/scalix-tomcat/connector/jk/instance-mail.conf and /etc/opt/scalix-tomcat/connector/ajp/instance-mail.conf I changed mail.theproshop.co.za:80 to *:80 so it doesn't used named based virtual hosting. All working now!

[fubar]

Hi

I'm testing the 60 day trial enterprise version and I want to make the best of it.

Here's my setup:

internet -- firewall -- Scalix -- lan

I have external DNS working from my ISP for the Scalix box i.e I have an A record for the machine. My ISP routed an additional /29 subnet to my diginet line so I could assign the Scalix box a public IP. No problems here. However on the internal network we run a Server 2003 domain controller. I had to create a new zone called "theproshop.co.za" with an A record "mail.theproshop.co.za" which points to 10.1.1.6 which is the internal IP of the Scalix box.

This is not ideal people, as on the internet mail.theproshop.co.za resolves to 196.41.12.100. Is there no better way to do DNS for Scalix? Any suggestions? I also run a 9 node VPN throughout South Africa for my company. So we may purchase another 3 Scalix boxes for the various branches.

Thanks

[KevinAnderson]

Why not drop one nic, and greatly simplify this by choosing either an internal or a public IP.

If you choose an internal IP, then forward ports 25 & 80 to Scalix from the Internet, with your MX record pointing at your firewall.

Having both an internal and an external nic doesn't get you much, but it adds drastically to the overall complexity of the install.

Kev

[dkelly]

Our Apache configuration is name-based so using IP addresses is not a good way to start.

Please take a look at http://www.scalix.com/wiki/index.php?title=HowTos/ApacheConfiguration which is off the Scalix 11 FAQs link I posted at the top of each forum.

If your internal DNS server can resolve the name correctly to the internal IP address, you should be fine.

Cheers

Dave

[dougp23]

I'm going to agree with Kevin on this one. I was going to do 2 NICs too. So I added a second DNS Forward Zone on Windows 2003 Server pointing to the mailserver IP. Great! Works! Now people internally couldn't surf (or update) our web site....reason? Well, I had setup that second zone for the email, but the 2nd zone is authoritative for the entire zone.

I could just see me adding more names, removing names as host names change and all that. Way too much work.

Set it up in your DMZ, one NIC. It's pretty. Setup IPTables and all that, and you will be happy!