Exchange 5.5 and DNS

[steveot]

Ok, got a problem with a test lab and Windows 2000/Exchange 5/5.
I setup a Win2k ADV server. Installed windows with the network cable unplugged. After install, gave it a static ip of 10.10.1.1 Subnet 255.0.0.0. DNS 10.10.1.1 and gateway of 10.10.1.1. Ran Dcpromo and setup the server for the first server in the domain etc. Picked yes to let it setup DNS for me. Got everything up and running but after ..changed the network settings/properties and added a gateway and dns entry to point to my wirelesss router. So I could get onto the internet. I installed Exchange 5.5 with SP4. When I goto add a Internet Mail Service SMTP and get the message per MS Technote

http://support.microsoft.com/default.aspx?scid=kb;en-us;247063.

Most of them point to adding Primary DNS Suffix for this Computer under system properties, but thats not a option since this is already a DC. I also have problem just adding another server as the second DC or installing Exchange on my second server because it cant contact the first DC, even though I can authenicate, ping, etc. Not sure of this Exchange or or AD issue.

 

[ShackDaddy]

Easy one.

You should not be pointed at your wireless router for DNS. By doing so, you are breaking your Active Directory. Your server is the DNS server and doesn't need to point anywhere outside, since it can query the root domain servers itself. A default gateway should be enough to send you on your way, as far as this system resolving queries for you.

You should ignore any DNS server's that your ISP gave you, unless you want to set your DNS up to forward queries to them so that less DNS outbound traffic is handled by your host.

ShackDaddy

 

[AlexIT]

You are runing Win2k ADC and 5.5 on one box. The NIC in the server is static assigned (because its ADC), and there is your router address as the default gateway in this nic. (So the server can get to the outside.)

There should be no DNS in the NIC (or its set to loopback address.) Your DNS server is not a root server (no ".") and you should assign a forwarder to some outside DNS server (your ISP DNS will work fine here.) As Shack said do not point your DNS at the router (unless its way more advanced that I assume, it won't have DNSd or such...) use your ISP DNS server as a forwarder.

Alex

 

[steveot]

I will give that a shot. Im think the DNS already point to itself or loopback and I add the other later. I think my problem lies within DNS itself. No matter what I do I cant get another server or exchange to be part of active directory.
And yes Exchange and my AD server are the same pc.

 

[ShackDaddy]

It may be that since you set up Exchange when you were pointed to the router for DNS, there may be some bad settings in the Exchange setup.

You may need to reinstall Exchange in an environment in which DNS is already working properly. If you have the server pointed to its loopback for DNS and have no other servers listed, you should be good. If not, see what's going on in the event log.

ShackDaddy