Netdiag DNS error

  • Thread starter Thread starter Zeke
  • Start date Start date
In (e-mail address removed) <[email protected]>
commented
Then Kevin replied below:

I see a couple of problems, read inline.

here is the latest:


C:\>nslookup
Default Server: DC1.anydomain.domain.org
Address: 192.168.5.6

Server: DC1.anydomain.domain.org
Address: 192.168.5.6

Name: _ldap._tcp.dc._msdcs.anydomain.domain.org

Server: DC1.anydomain.domain.org
Address: 192.168.5.6

_ldap._tcp.dc._msdcs.anydomain.domain.org SRV service
location:
priority = 0
weight = 100
port = 389
svr hostname = DC2.anydomain.domain.org
_ldap._tcp.dc._msdcs.anydomain.domain.org SRV service
location:
priority = 0
weight = 100
port = 389
svr hostname = DCA.anydomain.domain.org
_ldap._tcp.dc._msdcs.anydomain.domain.org SRV service
location:
priority = 0
weight = 100
port = 389
svr hostname = DC1.anydomain.domain.org
_ldap._tcp.dc._msdcs.anydomain.domain.org SRV service
location:
priority = 0
weight = 100
port = 389
svr hostname = DC2.anydomain.domain.org
DC2.anydomain.domain.org internet address = 192.168.5.4
DC2.anydomain.domain.org internet address = 38.233.154.182<--Public IP
address

This DC is multi-homed, which requires additional configuration to keep
other machines from trying to connect to the Public IP address which usually
does not have the proper services or file sharing enabled on the Public
interfaces. Please post if this server is also an RAS server so I can post
the correct KB article.
DCA.anydomain.domain.org internet address = 192.168.5.3
DC1.anydomain.domain.org internet address = 192.168.5.6<-----Wrong IP
registered for DC1.

The IP registered for this DC does not match the IP for this DC interface
that you posted below.
Run netdiag /fix on this DC.
and ipconfig /all:


C:\>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : DC1
Primary Dns Suffix . . . . . . . :
anydomain.domain.org
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . :
anydomain.domain.org
domain.org

Ethernet adapter Broadcom NetXtreme Dual Port Gigabit
Ethernet Adapter - Onboard
- Link B:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme
Gigabit Ethernet #2
Physical Address. . . . . . . . . : 00-0F-1F-66-CF-6F
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.5.7
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.5.253
DNS Servers . . . . . . . . . . . : 192.168.5.7

In addition, You should list the IP of all DCs with DNS installed as DNS
servers.
 
Thanks for your help guys.
I cannot give the results of this netdiag as it would give information I do
not want to share in this newsgroup.
A call has been openned with Microsoft...

Thanks again!
Ebk

Kevin D. Goodknecht Sr. said:
In Ace Fekay [MVP] <PleaseSubstituteMyActualFirstName&[email protected]>
commented
Then Kevin replied below:
In
Ebk said:
I have checked every option you mentionned and it is
fine except number two:
2. You do not have a single label name AD DNS domain
name: WHAT DO YOU MEAN?

<snip>

You don't seem to have a single label name. An example of
a single label name is "domain" versus a proper defined
name of "domain.com".

What concerns me is this:
DNS test . . . . . . . . . . . . . : Failed
[WARNING] The DNS entries for this DC are not
registered correctly on DNS se
rver '10.15.246.3'. Please wait for 30 minutes for DNS
server replication. [WARNING] The DNS entries for
this DC are not registered correctly on
DNS se
rver '10.15.246.2'. Please wait for 30 minutes for DNS
server replication. [FATAL] No DNS servers have the
DNS records for this DC registered.


Did you physically check those two DNS servers mentioned
in the message for the DC's record?

It might help if he ran netdiag /fix then post results from a
netdiag /test:dns /v
 
In
Ebk said:
Thanks for your help guys.
I cannot give the results of this netdiag as it would
give information I do not want to share in this newsgroup.
A call has been openned with Microsoft...

This is unfortunate, the netdiag will only give private addresses (or
should) thus, nobody would be able to use any info from it and would help
us.
 
I will share what we will obtain from MSFT!



Kevin D. Goodknecht Sr. said:
In

This is unfortunate, the netdiag will only give private addresses (or
should) thus, nobody would be able to use any info from it and would help
us.
 
Thanks for your reply.
***************************************************
This DC is multi-homed, which requires additional
configuration to keep
other machines from trying to connect to the Public IP
address which usually
does not have the proper services or file sharing enabled
on the Public
interfaces. Please post if this server is also an RAS
server so I can post
the correct KB article.
*****************************************************
This server is multihomed but used a special app and does
not cause any DNS problems. As far as the wrong IP on
DC1, that was my fault. I edited the DC names (for
privacy) and made an error, so the IP should have been
what appeared in IPconfig. Given that, what else could be
causing this issue?




-----Original Message-----
In (e-mail address removed)
 
Back
Top