I posted this problem a few days ago and nobody responded but today I
have some interesting information.

To recap, some NTFRS errors were showing up and machine account
passwords weren't replicationg. GPO updates were not working for the
secondary DC either. Running netdiag /test:dns /v showed that for each
SRV record the primary and secondary DCs thought their DNS server was
0.0.0.0 even though it wasn't.

Our configuration is 2 physical onboard NICs configured in a team using
a Broadcom utility. A virtual interface therefore exists upon which all
network settings are set. This interface has a DNS server IP set which
works fine when using nslookup or any other utility (except netdiag).

Today I did some more troubleshooting and found out that if I add a
secondary DNS server to my DNS server list then the netdiag utility will
attempt to query 0.0.0.0 as well as what I originally specified as my
primary DNS server as shown by the properties of the Team interface's
connection properties. The set of queries going to 0.0.0.0 still fail of
course but a second set of queries for each SRV record are sent to our
DNS server and return fine.

If I add a third DNS server IP then the 2nd DNS IP I added above is used
as a 3rd DNS IP in addition to 0.0.0.0 and my primary DNS server IP. We
actually only have 1 DNS server IP (load-balanced appliances) so a 2nd
DNS server IP isn't needed.

So basically, netdiag is trying to use 0.0.0.0 as a DNS IP which causes
all subsequent IPs listed (by netdiag) to be off by one when comparing
the "used" list to what is configured to be used.

The physical NIC properties for the 2 NICS are empty because we have a
virtual NIC in use. I don't know where the 0.0.0.0 is coming from
though. The 'nameserver' key in the registry is set to our primary DNS
server.

Still not sure 100% yet whether this is going to fix our replication
issues between our domain controllers but I'm hoping it will. I'll know
more tomorrow I hope as replication attempts will be made overnight.

Any ideas?

Thanks

Im kind of lost with all that information, but you've set on the DNS Server
properties on which IPs the server will listen to requests?

Cheers

noticias:4946f5f6$0$8513$9a6e1***@unlimited.newshosting.com...
Show quoteHide quote

augusto.alvare***@gmail.com wrote:
Microsoft DNS isn't installed on this machine. We use appliances for
DNS. ADS points to the appliances for DNS information. The IP of the
appliance is in the network properties for the teaming interface on the
server but netdiag doesn't want to use it. Other tools have no problem
with the DNS being located on an external (to machine) device. SRV
records are in the appliance BIND database. Netdiag reports that the DNS
server is 0.0.0.0 and therefore can't resolve SRV records when I run
'netdiag /test:dns /v'.

If I add in another DNS server IP to the interface properties then
netdiag still reports the 0.0.0.0 DNS IP but begins to list the correct
DNS Server IP but not until I add that secondary DNS.

So at this point I have DNS Server IP1 and DNS Server IP2 but only IP1
is listed in netdiag output because it wants to hold on to 0.0.0.0 from
somewhere.

If I add a 3rd DNS Server IP (we'll call it IP3) then I'll have IP1,
IP2, and IP3 listed as DNS servers on the interface connection
properties. But in netdiag output it still only queries 0.0.0.0, IP1,
and IP2. Because 0.0.0.0 won't go away netdiag is always missing a DNS
IP compared to what is configured for the network interface. All queries
to 0.0.0.0 of course fail but the netdiag SRV queries start succeeding
as long as I specify another DNS Server IP beyond the only one we should
have configured.

Note: As a test I'm specifying more than 1 DNS IP but the others are
located in parts of the network that these servers shouldn't be using
which is why the normal configuration only includes 1 DNS IP.

Summary:
Current configuration is this:
Normal DNS server IP list: 192.168.1.10
Normal (but wrong) NetDiag DNS IP list: 0.0.0.0 (obviously this should
match the line above but it doesn't, hence the problem I was
troubleshooting)

As a test I set this up:
Modified DNS Server IP list: 192.168.1.10,192.168.10.11,192.168.20.12
Modified NetDiag DNS IP list: 0.0.0.0,192.168.1.10,192.168.10.11
As you can see, NetDiag lags behind in knowing what DNS IPs to query
compared to what the official list of DNS IPs are in my LAN configuration.

Does that help? If so, have you seen this before?

thanks
Brandon




Brandon McCombs wrote:
Show quoteHide quote

Event 861 fills event log on newly built Domain Controller
Home folder creation via script
profilepath - User Profile
Lost Resources
how to change from sub.domain.com to domain.com
Scripted Drives
Password Change
AD 2003 and GPO on Windows 2008
GPO for Vista, allow normal User to create shares and to deactiv.
Clarification on computer object migration