Confusing DNS Configuration

  • Thread starter Thread starter Paul Padilla
  • Start date Start date
P

Paul Padilla

I recently took over for a previous Network Admin and
I've found that their mixed Win2k/NT domain has some very
strange configurations. For starters, the domain was set
up with a name that is already registered to someone
else. None of our servers have to interface directly
with the Internet (I.e. web server, etc.) and everything
seems to be working, but I have concerns about DNS.

Our one NT member server is running Exchange 5.5 as well
as Proxy (not my idea). This server is pointed to our
ISP's DNS. We have 2 Win2k domain controllers. The
domain root machine's DNS in TCP/IP is correctly pointed
to itself, but it also has forwarding enabled in the DNS
service and it's pointed to the NT member server running
Proxy.

We're in the prep stages for retiring the 5.5 machine and
migrating to Exchange 2K or 2K3. I know things aren't
right and I foresee problems implementing OWA, VPN and
the like. The problem is I don't have all the detailed
info my manager will need to justify reconfiguring the
entire domain to correct this issue.

Thanks in advance.
 
Hi Paul,
The domain name is really not a big deal, but you should have your own. I
your domain was called microsft.com the you could add records in your dns
server to get around problems. Its always good to name it like
mydomain.local.
Your Proxy server should point back to your internal DNS server and then
your internal DNS server should point back to your ISP.I can send you a DNS
white paper if you would like. They only thing I can tell you with the
information you have given is that DNS is a very important part of the
Exchange. It has to be correct or your have problems.
 
Back
Top