DNS GC entry

  • Thread starter Thread starter Reed Wiedower
  • Start date Start date
R

Reed Wiedower

I recently removed a global catalog server from the group of AD-integrated
DNS servers. However, in the _MSDCS subdomain, there is still an entry of
type "GC" with the old server's name. None of the other global catalogs
appear with a GC entry. Should I

1) delete the old GC entry

and

2) add some new GC entries for the other global catalogs?

end of line,

Reed Wiedower
 
In
Reed Wiedower said:
I recently removed a global catalog server from the group of
AD-integrated DNS servers. However, in the _MSDCS subdomain, there is
still an entry of type "GC" with the old server's name. None of the
other global catalogs appear with a GC entry. Should I

1) delete the old GC entry

and

2) add some new GC entries for the other global catalogs?

end of line,

Reed Wiedower
Click to expand...


Well, you can delete that manually, but as far as the other GCs, they should
be auto registering. Are you getting any Event log errors? Are you getting
any AD event log errors (netlogon, NTFRS, etc)?

Tell you what, if you can post an ipconfig /all and your AD DNS domain name,
that configuration information will give us a big start in diagnosing this
for you. Otherwise, with the limited info and the fact that the new GC is
not registering, is not enough to go on, but you definitely have an issue
based on what you posted.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
I managed to get the other machines to auto-register, but in the process,
another series of error messages are populating the logs:

DNS Event 6702 errors:

Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 6702
Date: 5/18/2004
Time: 2:25:57 PM
User: N/A
Computer: KIBITO
Description:
DNS Server has updated its own host (A) records. In order to insure that
its DS-integrated peer DNS servers are able to replicate with this server,
an attempt was made to update them with the new records through dynamic
update. An error was encountered during this update, the record data is the
error code.

If this DNS server does not have any DS-integrated peers, then this error
should be ignored.

If this DNS server's ActiveDirectory replication partners do not have the
correct IP address(es) for this server, they will be unable to replicate
with it.

To insure proper replication:
1) Find this server's ActiveDirectory replication partners that run the DNS
server.
2) Open DnsManager and connect in turn to each of the replication partners.
3) On each server, check the host (A record) registration for THIS server.
4) Delete any A records that do NOT correspond to IP addresses of this
server.
5) If there are no A records for this server, add at least one A record
corresponding to an address on this server, that the replication partner can
contact. (In other words, if there multiple IP addresses for this DNS
server, add at least one that is on the same network as the ActiveDirectory
DNS server you are updating.)
6) Note, that is not necessary to update EVERY replication partner. It is
only necessary that the records are fixed up on enough replication partners
so that every server that replicates with this server will receive (through
replication) the new data.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: b4 05 00 00 ´...



Here's the ipconfig information for one of the two servers:

U:\>ipconfig /all

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : kibito
Primary DNS Suffix . . . . . . . : dbz.peyser.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : dbz.peyser.com
peyser.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Netelligent 10/100TX PCI
Embedded UT
P Coax Controller
Physical Address. . . . . . . . . : 00-08-C7-1C-74-DC
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 66.208.7.100
Subnet Mask . . . . . . . . . . . : 255.255.255.248
IP Address. . . . . . . . . . . . : 192.168.0.3
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.3
192.168.0.2
66.208.7.100
66.208.7.99

PPP adapter RAS Server (Dial In) Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 66.208.7.101
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 127.0.0.1

U:\>

Any hints?

end of line,

Reed Wiedower




"Ace Fekay [MVP]"
 
Hello,

You have 4 DNS servers listed;
192.168.0.3
192.168.0.2
66.208.7.100
66.208.7.99

Are each of these DNS servers DC's? In an active directory integrated zone
you want to point ONLY at your DC's for DNS. Also look in DNS for any host
record for the DC's that may have the incorrect IP listed. If you find on
then remove this record in DNS and see if the events come back.


Larry Stotler, MCSE
Microsoft Product Support

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!

This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose
 
In
Larry Stotler said:
Hello,

You have 4 DNS servers listed;
192.168.0.3
192.168.0.2
66.208.7.100
66.208.7.99

Are each of these DNS servers DC's? In an active directory
integrated zone you want to point ONLY at your DC's for DNS. Also
look in DNS for any host record for the DC's that may have the
incorrect IP listed. If you find on then remove this record in DNS
and see if the events come back.


Larry Stotler, MCSE
Microsoft Product Support

NOTE: Please reply to the newsgroup and not directly to me. This
allows others to add to and benefit from these threads and also helps
to ensure a more timely response. Thank you!

This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose
Click to expand...


I agree Larry.

In addition, I would also suggest to change the 127.0.0.1 in the PPP adapter
to 192.168.0.2. There is also an extra IP on this machine and it is an
external IP. I would highly suggest to remove that external IP, since it
will cause major issues with AD functionality.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
Back
Top