Re: DCDIAG DNS Failure
- From: "Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx>
- Date: Wed, 9 Aug 2006 18:04:08 +0100
ok let me know the results
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator
"dlove106" <dlove106@xxxxxxxxxxxxxxxxxxx> wrote in message
news:06ED0563-AE9B-4C76-91D1-FF333CFCCF10@xxxxxxxxxxxxxxxx
--
DLove
"Jorge Silva" wrote:
Ok
so the sddcsrv03 is a DC and DNS server right?
Correct
and the errors are accouring in this server correct?
That is correct, although I receive the same error when dcdiag is run
against the child dc.
the NIC properties looks ok.
Make sure that under TCP/IP properties you have the option "Register this
connection's address in DNS" selected.
It is selected.
check if the Shiprepair.com dns zone allows dynamic updates if the zone
is
AD integrated select secure updates only.
It is.
instead of having 1 Reverse lookupzone for each subnet:I will perform this later today and look over the articles you listed
192.168.0.x,192.168.1.x, etc, create ONLY 1 reverse lookup zone only but
like: 192.168.x.x.
- rightclick the DNS server and clear the cache.
- run from cmd: ipconfig /flushdns
- run from cmd: ipconfig /registerdns
- restart the netlogon service.
- run netdiag /fix
below.
Thanks for your help.
Then check if the records were created for the reverse and Forwarding
zones.
Run the tests again and check if the problem remains, if yes you might
try
to recreate the zone for Shiprepair, check these articles that migh help
you
to acomplish these tasks:
How to enable or disable DNS updates in Windows 2000 and in Windows
Server
2003
http://support.microsoft.com/default.aspx?scid=kb;EN-US;246804&sd=RMVP
How to Verify the Creation of SRV Records for a Domain Controller
http://support.microsoft.com/?id=241515
Verify DNS registration for domain controllers using the nslookup command
http://technet2.microsoft.com/WindowsServer/en/library/b6879c0b-cff7-438d-a7f3-0715456dcefb1033.mspx?mfr=true
Verify DNS server responsiveness using the nslookup command
http://technet2.microsoft.com/WindowsServer/en/Library/f8761f04-d665-4507-9509-ebb92bbb66ef1033.mspx
How to reinstall a dynamic DNS Active Directory-integrated zone
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q294328&sd=RMVP
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator
"dlove106" <dlove106@xxxxxxxxxxxxxxxxxxx> wrote in message
news:36522D31-C7AB-4A4B-A34A-001DB21B6CF6@xxxxxxxxxxxxxxxx
--
DLove
"Jorge Silva" wrote:
OkDNS Server ---
- can you post here the results for ipconfig /all of your DNS server.
- also can you check if the DNS server is responding to all its
IPAddress
(DNS Console->right click->interfaces tab.
also describe (can be other different names) your actual reverse
lookup
zone
and forward zones.
Windows IP Configuration
Host Name . . . . . . . . . . . . : sddcsrv03
Primary Dns Suffix . . . . . . . : Shiprepair.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : Shiprepair.com
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast
Ethernet
Controller (3C905C-TX Compatible)
Physical Address. . . . . . . . . : 00-B0-D0-B2-3E-A9
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 172.20.100.10
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 172.20.0.2
DNS Servers . . . . . . . . . . . : 172.20.100.10
Primary WINS Server . . . . . . . : 172.20.0.30
My Forward zones are as follows:
shiprepair.com
sdsr (child)
Hawaii.com (remote site with their own dns)
Web Site (on a different subnet)
Reverse zones:
I have one for each subnet.
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator
"dlove106" <dlove106@xxxxxxxxxxxxxxxxxxx> wrote in message
news:4B78A324-7D75-4CFB-AFA7-2C709F631A69@xxxxxxxxxxxxxxxx
--
DLove
"Jorge Silva" wrote:
Inline
0.in-addr.arpa- these are loopback related, don't worry.
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.
- 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.
My DNS server is not multihomed. Everything certainly worked better
- 7 reverse lookup zones?
do you need all these reverse zones or your DNS server is
multihomed
(multiple NICs)
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.
I am in mixed mode right now with both ek55 and ek2003. I will post
-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.
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
.
- Follow-Ups:
- Re: DCDIAG DNS Failure
- From: dlove106
- Re: DCDIAG DNS Failure
- References:
- DCDIAG DNS Failure
- From: dlove106
- Re: DCDIAG DNS Failure
- From: Jorge Silva
- Re: DCDIAG DNS Failure
- From: dlove106
- Re: DCDIAG DNS Failure
- From: Jorge Silva
- Re: DCDIAG DNS Failure
- From: dlove106
- Re: DCDIAG DNS Failure
- From: Jorge Silva
- Re: DCDIAG DNS Failure
- From: dlove106
- Re: DCDIAG DNS Failure
- From: Jorge Silva
- Re: DCDIAG DNS Failure
- From: dlove106
- Re: DCDIAG DNS Failure
- From: Jorge Silva
- Re: DCDIAG DNS Failure
- From: dlove106
- Re: DCDIAG DNS Failure
- From: Jorge Silva
- Re: DCDIAG DNS Failure
- From: dlove106
- DCDIAG DNS Failure
- Prev by Date: Re: Empty DNS Log Problem ??
- Next by Date: Re: PTR records no longer existing
- Previous by thread: Re: DCDIAG DNS Failure
- Next by thread: Re: DCDIAG DNS Failure
- Index(es):
Relevant Pages
|