SRV record error

[SilvrT]

When I do a dcdiag /test:dns I get the following error...

Missing GC SRV record at DNS server 192.168.1.5 :
_ldap._tcp.gc._msdcs.<mydomainname>.com

Can anyone tell me how to fix this? I've tried a number of things I've
found on the net and unless I need to reboot the DNS servers, nothing
seems to work.

I have 2 DNS servers. First one is a Win2003 server and second one is
a Win2000 server. The Win2003 server was the "lone" DNS server and I
just installed DNS onto the Win2000 server (IP 192.168.1.5). Now,
everything runs slower (internet, logging in, etc) and I had to change
my firewall which uses LDAP for authentication to point to the Win2000
server (it used to work fin when pointing to the Win2003 server
IP=192.168.1.1)

Thanks for any help out there.

[Herb Martin]

Post by SilvrT
When I do a dcdiag /test:dns I get the following error...
_ldap._tcp.gc._msdcs.<mydomainname>.com
Can anyone tell me how to fix this? I've tried a number of things I've
found on the net and unless I need to reboot the DNS servers, nothing
seems to work.

Check these:

First:
DCDiag /fix OR
NetDiag /fx
...on affected DC, and/or restart NetLogon service

Then check:
zone is dynamic (probably is or you would likely have more errors)
192.168.1.5 DNS Server is REPLICATING from the master
(or is the master)
DC complaining is a GC (AD Sites and Services)
DNS server(s) used by this DC is ONLY the itnernal ones and
can find the DNS Server(s) that accept dynamic requests

Post by SilvrT
I have 2 DNS servers. First one is a Win2003 server and second one is
a Win2000 server. The Win2003 server was the "lone" DNS server and I
just installed DNS onto the Win2000 server (IP 192.168.1.5). Now,
everything runs slower (internet, logging in, etc) and I had to change
my firewall which uses LDAP for authentication to point to the Win2000
server (it used to work fin when pointing to the Win2003 server
IP=192.168.1.1)
Thanks for any help out there.

[SilvrT]

        DCDiag /fix  OR
        NetDiag /fx
      ...on affected DC, and/or restart NetLogon service

Can this be done when users are logged on and there is network
activity going on or should I be doing this during off-hours?

    zone is dynamic (probably is or you would likely have more errors)
    192.168.1.5 DNS Server is REPLICATING from the master
        (or is the master)

From my own workstation, I have run netdom verify <workstationName> /
domain:<domainName>

It tells me that the connection is with the machine
ccentre2.<domainName>
This is the Win2000 server at IP 192.168.1.5.
This would suggest that it is the master, would it not? How then can I
get things to think the master is ccentre1 (the Win2003 server)?

    DC complaining is a GC (AD Sites and Services)
    DNS server(s) used by this DC is ONLY the itnernal ones and
        can find the DNS Server(s) that accept dynamic requests

[Herb Martin]

DCDiag /fix OR
NetDiag /fx
...on affected DC, and/or restart NetLogon service

<<
Can this be done when users are logged on and there is network
activity going on or should I be doing this during off-hours?
Go ahead -- should offer no problems -- even less intrusive than
temporarily Stopping and then re-Starting the NetLogon service.

While the NetLogon service is stopped it cannot perform authentication.

BUT consider that if you already have problem that may not really
matter and the problems need to be fixed (usually NOW.)

zone is dynamic (probably is or you would likely have more errors)
192.168.1.5 DNS Server is REPLICATING from the master
(or is the master)

<<
From my own workstation, I have run netdom verify <workstationName> /
domain:<domainName>

It tells me that the connection is with the machine
ccentre2.<domainName>
This is the Win2000 server at IP 192.168.1.5.
This would suggest that it is the master, would it not?
I don't do it that way or use that tool for this.

<<
How then can I
get things to think the master is ccentre1 (the Win2003 server)?
By configuring the zone correctly.

DC complaining is a GC (AD Sites and Services)
DNS server(s) used by this DC is ONLY the itnernal ones and
can find the DNS Server(s) that accept dynamic requests

[Jorge Silva]

Hi
Check if the DNS is correctly configured (on the Server and workstation,
remember that the workstation must use the LOCAL DNS), als check this link
to verify the srv creation http://support.microsoft.com/kb/241515.
Additionally check FW configurations.

[SilvrT]

Post by Jorge Silva
Hi
Check if the DNS is correctly configured (on the Server and workstation,
remember that the workstation must use the LOCAL DNS), als check this link

HOW do I check to see if it's correctly configured?
What do you mean "the workstation must use local DNS"? How do I check
that?

Post by Jorge Silva
to verify the srv creationhttp://support.microsoft.com/kb/241515.
Additionally check FW configurations.
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services

[Jorge Silva]

In the NIC configuration.

Primary and secondary DNS server under TCPIP configuration.

[SilvrT]

Post by Jorge Silva
In the NIC configuration.
Primary and secondary DNS server under TCPIP configuration.
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services

That is configure properly.

Preferred DNS server is 192.168.1.1
Alternate is 192.168.1.5

[Herb Martin]

Post by Jorge Silva
In the NIC configuration.
Primary and secondary DNS server under TCPIP configuration.
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services
That is configure properly.
Preferred DNS server is 192.168.1.1
Alternate is 192.168.1.5

So these are both internal DNS servers, both can resolve ALL the
names the clients will (ever) need, and both resolve the SAME
things to the same values?

No other DNS is listed.

[SilvrT]

Well, after a lot of "mucking around", the most common error that
seemed to be cropping up was the the Win2003 server was "unavailable"
or "offline". The last thing I tried was forcing a replication....got
similar error. I put 2 and 2 together, logged onto that server and
disabled the firewall...voila` ... everything works!

I guess that's a lesson to be learned...Win2003's built-in firewall
state is "ON" and basically blocks all such traffic (it appears).

________________________________

Post by Jorge Silva
Primary and secondary DNS server under TCPIP configuration.

Jorge means: PREFERRED and ALTERNATE DNS services in
the NIC->IP properties configuration.

Primary and Secondary are SERVER only concepts and irrelevant
to clients for DNS resolution.
________________________________

Yes, I understand that and knew what was meant.

Thanks for all your assistance guys !!! much appreciated.

[Jorge Silva]

In previous posts I said to check the FW.... eheheh.
But by default the Windows 2003 FW is NOT ON.

Glad that evrything is working now.

[SilvrT]

Post by Jorge Silva
In previous posts I said to check the FW.... eheheh.
But by default the Windows 2003 FW is NOT ON.
Glad that evrything is working now.
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services

That's correct... you did mention that... but, being the airhead I
am... I didn't associate "FW" with FireWall .... ;-)

As for the default setting for the FW <---- (abbreviation for
FireWall) .... you may be correct but I sure didn't turn it on ...
at least I don't recall doing that.

(just ribbin ya with the FW thing)

Thanks a bunch.

[Jorge Silva]

The pleasure was mine.

[Herb Martin]

Post by Jorge Silva
In the NIC configuration.
Primary and secondary DNS server under TCPIP configuration.

Jorge means: PREFERRED and ALTERNATE DNS services in
the NIC->IP properties configuration.

Primary and Secondary are SERVER only concepts and irrelevant
to clients for DNS resolution.

For registration, the Primary (or multi-mastered AD Integrated)
Server must be found by querying the SOA records.

[SilvrT]

Post by Jorge Silva
Hi
Check if the DNS is correctly configured (on the Server and workstation,
remember that the workstation must use the LOCAL DNS), als check this link
to verify the srv creationhttp://support.microsoft.com/kb/241515.
Additionally check FW configurations.
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MCSE, MVP Directory Services

I did the NSLOOKUP suggested in the link you supplied. Following is
what I get...
(obvioulsy something is not right so what do I do to fix it?)

_______________________________________
From the Win2003 server (IP=192.168.1.1)...
________________________________________


C:\>nslookup
Default Server: ccentre1.therobertsongroup.com
Address: 192.168.1.1

Post by Jorge Silva
set type=all
_ldap._tcp.dc._msdcs.therobertsongroup.com

Server: ccentre1.therobertsongroup.com
Address: 192.168.1.1

_ldap._tcp.dc._msdcs.therobertsongroup.com SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = ccentre2.therobertsongroup.com
_ldap._tcp.dc._msdcs.therobertsongroup.com SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = ccentre1.therobertsongroup.com
ccentre2.therobertsongroup.com internet address = 192.168.1.5
ccentre1.therobertsongroup.com internet address = 192.168.1.1
________________________________________
From the Win2000 server (IP=192.168.1.5)...
________________________________________

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\Documents and Settings\%admin!!>nslookup
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 192.168.1.1: Timed out
*** Default servers are not available
Default Server: UnKnown
Address: 192.168.1.1

Post by Jorge Silva
set type=all
_ldap._tcp.dc._msdcs.therobertsongroup.com

Server: UnKnown
Address: 192.168.1.1

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

[Jorge Silva]

Okay,
-Is the ccentre2 also a DNS server?
-Can you post here the results for ipconfig /all for both servers?

Also Run dcdiag /e /c /v and post here the results