Windows Server

Dave · Guest

I have an Exchange 2003 server on site and have my ISP have a backup email
server so oif my server goes down we will still be able to receive mail.
Sending and receiving email appears to be working good. My concern is
verifying that the DNS configuration is correct. We have a T1 in place and
experience slow Internet connetions frequently. I was thinking if the DNS
configuration was not configured properly this might have something to do
with the connectinvity speeed.

Current server configuration

SERVER 1, SERVER 2, SERVER 3 >all configured the same 2003 standard edition
AD/ DHCP/DNS/WINS. The servers were installed in order 1, 2, 3.

Server 1 and 2 reside at site 1. Server 3 is located in another office and
connected to site 1 through VPN.

Server 1
DNS settings>interface points to itself, Forwarders point to local ISP
TCP/IP DNS preferred points to itself, alternate points to server 2
WINS points to itself

Server 2
DNS settings>interface points to Server 1, Forwarders point to local ISP
TCP/IP DNS preferred points to Server 1

Server 3
DNS settings>interface points to itself, Forwarders point to local ISP and
server 1
TCP/IP DNS preferred points to itself
WINS points to itself

I did a DNS report and it showed that NS records are at the parent server
which is the ISP’s backup server.
Also there is a warning that both servers claim to be the host.

What if any settings should I verify with my local ISO to ensure that
configuration is correct?

Curt Spanburgh · Guest

You said that a diagnostic shows that the NS records are on the ISP's DNS
server?

My friend, how and why would the ISP's DNS server be asked to resolve DNS
searches for your active directory?

Make sure you have forward and reverse zones on your DCs. If each one
points to itself you get what is called the "Island effect". Make the zone
"Active Directory intergrated". If your ISP host your registered name "Like"
myplace.net then that server should have an "A" record and an MX record for
your exchange server to the public IP of your SMTP access on your firewall.
Make sure that you have the root servers listed in your DNS configuration.
Test the basic Iterative and recursive test and make sure that if your
manually create a host record in one dns server, that it replicates to the
others in a decent amount time. Then test resolution witn NSlookup for all
your servers and host. Afteward test resolution for external sites the same
way. And make sure the clinet machines are pointing to the in house DNS
servers. Not the external ones. If the ISP dns server are far away, use
others that are closer. They all work. You also do not want to do zone
transfers with the ISP's DNS servers that have your client IP addresses on
them.

This is just the basic stuff. Get on the project and tell us how you make out.

Visit us at www.minasi.com

"Dave" wrote:

	Windows Server Forum Index -> DNS	All times are GMT
Page 1 of 1