Need immediate help with ISA Server & DNS Server

[CBuxton]

I'm in need of some serious help with ISA Server. I've recently moved my webserver and email server behind my proxy/firewall and am having some problems getting things to connect and work right. My website works just great, but I can't get any email to work. I've ran the email security wizard and it sets things up, but still can't seem to send or receive any email. From a remote computer I can telnet into the external address of my proxy server and it forwards port 25 and 110 correctly to my email server. What could I have setup incorrectly? I need internal users to be able to check and send mail, and also remote users to be able to check and send mail, so I need SMTP and POP3 both incoming and outgoing. Any help would be greatly appreciated!

2nd question is, is there a way to make a client use an internal DNS server before it goes out to the internet? Reason being that I have an internal DNS server setup with the same domain name as my public domain, but when I try to access a host using the server, I get the external address, not the internal address as I have specified in the DNS server. Thanks for any help!!

 

[WoundedWallet]

Sorry if it sounds dumb, but what is an ISA server?

 

[Damaged]

Don't know diddly about ISA server, but I do know what it is. You sure you allowed the internal IPs to relay (SMTP only here)? May be something similar with the POP server as well seeing as how you ran some sort of security script to set that up.

As to the DNS, you have a couple of options:

1) You maintain zone files for the internal stuff on the internal server. This is one reason to have both .com and .net domains. Just one though. And I'm sure I don't have to tell you this. This would certainly be the most transparent to the user.

2) You create a host file on each workstation. Easily deployed with scripts if you're configured to do that, and not much harder to write a batch file that will copy the file into the proper location and just tell everyone to download and run it.

3) Split DNS with mappings. Argh! No. Ugly, and at least as time consuming as the other options in initial setup time. Though you could mirror www.microsoft.com and locally and redirect people there. But why?


Oh yeah! Try this site for DNS questions: Ask Mr. DNS. It's a great resource.