>1) I know that as an email admin, I need to know much more about DNS,
>and specifically how to configure it. I have seen posts, both here and
>elsewhere, that argue the superiority of BIND over MS-DNS.
Well, bind is what every root servers uses, if I recall correctly. That
should say something.
As far as I know, the only real advantage to MS DNS is that it has a GUI
(that looks nicer than Notepad!). But, I've also seen that GUI make some
bad mistakes (IE someone who had more DNS knowledge than the typical
mailserver admin entered something that seemed obvious, but didn't do what
it was expected to do).
We set up bind here internally, and although I can't say I know much about
how it works, it works. We only have a couple of domains that we need it
to be authoritative for, so it is mostly a caching DNS server, and as such,
it works flawlessly, and requires very little (if any) maintenance.
>2)Should I build an independent cacheing-only nameserver for IMAIL on
>the IMAIL server? The hardware could handle it, I'm sure (dual AthlonMP
>2200+, 1G ECC PC2100, W2KS). What would be the pros and cons of this?
It's not a bad idea. If it is caching only, it should be (relatively) easy
to set up with bind. That prevents some extra network traffic that would
be seen from both IMail's MX record lookups as well as the numerous spam
database lookups, which use DNS as well.
-Scott
---
Declude: Anti-virus, Anti-spam and Anti-hijacking solutions for
IMail. http://www.declude.com
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html
List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
