Re: DCDIAG DNS Failure

1 AD domain - Parent DC is located in Shiprepair, which is also the sole DNS
server, which has forwarders to our ISP. Child DC has has all member servers
including 2003 exchange. Exchange points to parent dc as preferred dns
server (no alternate). Exchange 2003 is co-existing with Exchange5.5, with
2003 handling both inbound and outbound traffic. Presently, 95% of the
mailboxes still reside in 5.5, which is located in a NT4 domain.

We actually have 2 email addresses, 1 from corporate with DNS handled by
them (Mail working fine), the other handled locally by me (does not route
thru corporate). Incoming mail is forwarded from 2003 Exchange to 5.5
exchange after going thru spam filter.

The DNS structure has a zone configured for the parent domain and a child
zone for the child domain, with the appropriate host, NS, and SOA's in the
parent and host records in the child. Reverse lookup zones are also
configured.

I hope this help. If you need more specifics let me know.

Thanks for the help.
--
DLove


"Jorge Silva" wrote:

Hi

Can you describe a little more about network config:

-Did you monitored the exchange (Memory,CPU,DISK,SMTP Queues,virtual
memory,etc)?
-Exchange configuration (NIC Properties).
-Existent DNS servers and its configuration.
-How the mail is being delivered to Exchange.
-DNS structure.
-Etc.


--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"dlove106" <dlove106@xxxxxxxxxxxxxxxxxxx> wrote in message
news:2DDFBD9A-DAA2-41D4-95F3-63326895E458@xxxxxxxxxxxxxxxx
I suspect that DNS issues are causing me to have email messages arrive
hours
or even a day late. It does not happen all the time, but does I have
confirmed the problem. I ran dcdiag /test:dns and received the output
below.
I am able to successfully query other domains, and everything appears to
be
functioning fine. I'm not sure why the test is failing or what caused it.
Without the sometimes slow mail delivery, I would not even know there was
a
problem. Any help in troubleshooting the problem would be greatly
appreciated.

DNS is running on a DC in the Parent container; Exchange 2003 server is
located in child domain.

Thanks.

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\SDSERVER
Starting test: Connectivity
......................... SDSERVER passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\SDSERVER

DNS Tests are running and not hung. Please wait a few minutes...

Running partition tests on : SDSR

Running partition tests on : Schema

Running partition tests on : Configuration

Running enterprise tests on : Shiprepair.com
Starting test: DNS
Test results for domain controllers:

DC: sdserver.SDSR.Shiprepair.com
Domain: SDSR.Shiprepair.com


TEST: Basic (Basc)
Warning: adapter [00000005] HP NC7760 Gigabit Server
Adapter has invalid DNS server: 172.20.100.10 (<name unavailable>)
Error: all DNS servers are invalid

TEST: Records registration (RReg)
Error: Record registrations cannot be found for all the
network adapters

Summary of test results for DNS servers used by the above domain
controllers:

DNS server: 172.20.100.10 (<name unavailable>)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the
1.0.0.127.in-addr.arpa. failed on the DNS server 172.20.100.10

Summary of DNS test results:

Auth Basc Forw Del Dyn RReg
Ext

________________________________________________________________
Domain: SDSR.Shiprepair.com
sdserver PASS FAIL n/a n/a n/a FAIL
n/a

......................... Shiprepair.com failed test DNS

--
DLove



.

Relevant Pages

  • Re: set up first child DC in a remote site
    ... has not set its IP and DNS in the creation of ... delegation can the parent DC see the child DC-to-be? ... and child zone created as the Conditional forwarding configured pointing to ...
    (microsoft.public.windows.server.active_directory)
  • Re: set up first child DC in a remote site
    ... Since step 3 is done before installing the DNS on it, ... necessary to put the DNS server pointing to the parent domain. ... DC on the Child doamin and it's IP Address, at the moment that you create ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replication Headache - Urgent please Assist!
    ... 1.Manually created a delegation for the child domain on our root server DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: set up first child DC in a remote site
    ... The reason I put step 3 in front of step 4 is that if the child DC-to-be has ... not set its IP and DNS in the creation of delegation ... can the parent DC see the child DC-to-be? ... Forwarding to point to the parent domain, point the server to itself under ...
    (microsoft.public.windows.server.active_directory)
  • Re: Misconfigured AD
    ... I have a Parent domain with 2 child domains and an exchange server ... I agree with Herb that it's more than likely a DNS misconfiguration. ...
    (microsoft.public.windows.server.active_directory)