Re: DCDIAG DNS Failure


--
DLove


"Jorge Silva" wrote:

Inline
0.in-addr.arpa
127.in-addr.arpa
255.in-addr.arpa
- these are loopback related, don't worry.

So, with advance view I have 4 forward lookup zones and 10 reverse lookup
zones. Without advance view I have 4 forward lookup zones and 7 reverse
lookup zones.

- are you hosting 4 different domains?
domain01.com, domain02.com,etc?
did you created MX records for the exchange domains that you're hosting?

The domains are valid. I have created an MX record for the exchange domain.

- 7 reverse lookup zones?
do you need all these reverse zones or your DNS server is multihomed
(multiple NICs)

My DNS server is not multihomed. Everything certainly worked better after
the reverse zones were created. They are all valid reverse zones.

-Your exchange server that is giving you problems, can it send Mail outside,
or the problem is only to receive Mails?
if the problem is only to receive mails, check that your FW/ROUTER have the
correct ports (SMTP 25TCP) pointing to the exchange server, also make sure
that the FW/ROUTER for your domain has the correct public address.

The router has the correct info. The problem is mainly slow delivery, not
so much non-delivery of incoming mail.

-If the problem is between the Exchange 5.5 and 2003 you should check the
connectors between them, goto exchange ng they can help you out better.

I am in mixed mode right now with both ek55 and ek2003. I will post in the
exchange group, although I would like to correct the DNS error found in
dcdiag.
--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"dlove106" <dlove106@xxxxxxxxxxxxxxxxxxx> wrote in message
news:A6E2C987-4829-469B-9DD7-4F70A01D3AC6@xxxxxxxxxxxxxxxx

--
DLove


"Jorge Silva" wrote:

Ok, disable the advance view on DNS console, what do you see now?
No zones?
If yes then you can configure one zone, make AD integrated (If the server
is
a DC), run ipconfig /registerdns

I still see zones after disabling the advance view (Expected?). The only
change is I no longer see 3 of the reverse lookup zones. They are as
follows:
0.in-addr.arpa
127.in-addr.arpa
255.in-addr.arpa

So, with advance view I have 4 forward lookup zones and 10 reverse lookup
zones. Without advance view I have 4 forward lookup zones and 7 reverse
lookup zones.



--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"dlove106" <dlove106@xxxxxxxxxxxxxxxxxxx> wrote in message
news:90E860AB-1EE7-48EA-8FB9-4D9B729AA41D@xxxxxxxxxxxxxxxx
Jorge,

I have looked at most of the articles you sited and I have configured
DNS
accordingly sometime ago. My clients are pointing to my internal DNS
server
only. The DNS server lists only itself as the preferred server with no
alternate. I am not certain about the reverse lookup zone setup as I
have
3
entries that seem to refer to the loopback address. I'm not sure which
one
is the correct one. They list as follows:

0.0.127.in-addr.arpa (Has NS & SOA records pointing the lone DNS
server)

0.in-addr.arpa (Has NS & SOA records pointing the lone DNS server)

127.in-addr.arpa (Has NS & SOA records pointing the lone DNS server)
This
one also has a child entry as follows:
0 (Yellow folder with 1 record listed below)
0 (NS record)

I hope this sheds a little more light on what I am seeing and can help
in
how to proceed.

Thanks.

--
DLove


"Jorge Silva" wrote:

This sounds more like a Exchange missconfiguration.
to check DNS config:
- Make sure that you configure the Preferred DNS server in TCP/IP
properties
on each Domain Controller to use itself as Primary DNS Server (If DC
IP
Address is 10.0.0.1 then Dns should be 10.0.0.1).When adding an
additional
DC to an existent Domain, do not configure the domain controller to
utilize
its own DNS service for name resolution until you have verified that
both
inbound and outbound Active Directory replication is functioning and
up
to
date. During the DCPromo process, you must configure additional domain
controllers to point to another domain controller that is running DNS
in
their domain and site, and that hosts the namespace of the domain in
which
the new domain controller is installed. More Info here:

Best practices for DNS client settings in Windows 2000 Server and in
Windows
Server 2003

http://support.microsoft.com/kb/825036/en-us

- Make sure that every DNS server can resolve all existent domains in
the
forest. (You can use Forwarding, Stub Zones or Secondary Zones).

DNS Conditional Forwarding in Windows Server 2003

http://www.windowsnetworking.com/articles_tutorials/DNS_Conditional_Forwarding_in_Windows_Server_2003.html

DNS Stub Zones in Windows Server 2003

http://www.windowsnetworking.com/articles_tutorials/DNS_Stub_Zones.html

How To Create a Child Domain in Active Directory and Delegate the DNS
Namespace to the Child Domain

http://support.microsoft.com/kb/255248/

- Make sure that all clients only use their local(s) Dns Server. Note
That
DNS client does not utilize each of the DNS servers listed in TCP/IP
configuration for each query. By default, on startup the DNS client
will
attempt to utilize the server in the Preferred DNS server entry. If
this
server fails to respond for any reason, the DNS client will switch to
the
server listed in the alternate DNS server entry. The DNS client will
continue to use this alternate DNS server until: fails to respond to a
DNS
query, or The ServerPriorityTimeLimit value is reached (15 minutes by
default). For more information:

How To Install and Configure DNS Server in Windows Server 2003

http://support.microsoft.com/kb/814591/en-us

Best practices for DNS client settings in Windows 2000 Server and in
Windows
Server 2003

http://support.microsoft.com/kb/825036/en-us

How to configure DNS for Internet access in Windows Server 2003

http://support.microsoft.com/kb/323380/en-us

How to configure TCP/IP to use DNS in Windows XP

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




--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"dlove106" <dlove106@xxxxxxxxxxxxxxxxxxx> wrote in message
news:50EDC2F6-F02B-4C06-8CB2-22F2207B8E8F@xxxxxxxxxxxxxxxx
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.

.

Relevant Pages

  • Re: Usage Report show IP addr instead of computer names
    ... The reverse DNS look-up is only query DNS server, ... | the reverse lookups at 4:30, will that cause the Usage Report to identify ...
    (microsoft.public.windows.server.sbs)
  • Re: DCDIAG DNS Failure
    ... Without advance view I have 4 forward lookup zones and 7 reverse ... do you need all these reverse zones or your DNS server is multihomed ... -Your exchange server that is giving you problems, can it send Mail outside, ...
    (microsoft.public.windows.server.dns)
  • Re: DCDIAG DNS Failure
    ... also can you check if the DNS server is responding to all its IPAddress ... zone and forward zones. ... did you created MX records for the exchange domains that you're hosting? ...
    (microsoft.public.windows.server.dns)
  • RE: SBS2003: Intermitent Connectivity from Clients to Public websi
    ... I already had two zones set up under the Forward Zones. ... names along with their respective IP addresses per DNS name. ... Originally, I did install ISA Server, but uninstalled it. ... you can access them normally on SBS. ...
    (microsoft.public.windows.server.sbs)
  • Re: [opensuse] what does 127.0.1.1 mean?
    ... and accurate reverse tables. ... This is where the Samba guys ... It has its own built in KDC and LDAP server. ... it will have its own DNS server too. ...
    (SuSE)