From: alexander brown (albrown@eecs.berkeley.edu)
Date: Tue Mar 05 2002 - 18:37:58 PST
Hey Jon;
That is in fact a feature. :>
When you set up an AD, an A record with the name of the zone (i.e.,
ce.berkeley.edu) is created, pointing at your domain controller. It
does create one for each domain controller. This is 'how it works'.
[My comments on whether or not this is 'how it should work' suppressed.]
It is safe to remove this record (there is a Q article somewhere that
documents that). But, if you're running DDNS on your DCs I imagine it
will continually repopulate itself, although this may be OK if you're
not pointing clients at your DCs for DNS service?
--alex
Jon Forrest wrote:
>I've found what appears to be a bug in Microsoft's
>DNS implementation on Windows Server 2000 SP2.
>
>I originally setup a DNS server on W2K Server as
>a secondary that got its zone data from a Unix bind
>server which is primary for my domain. That worked fine.
>
>I then promoted the W2K Server to be a domain
>controller and converted the DNS server to Active
>Directory integrated. I then noticed a bad record
>in my DNS zone. What I was seeing was an "A" record
>for the name of my domain (e.g. "ce.berkeley.edu")
>containing the address of the name server. Since
>there already was an "A" record in my zone for the
>Unix DNS server with this name I started to get worried.
>In other words, what I was seeing was
>
>(same as parent folder) Host 128.32.143.106 < good - the Unix DNS server
>(same as parent folder) Host 128.32.143.162 < bad - the new W2K DNS server
>
>The first entry is correct. The second is the address of the DNS server +
>Domain controller PC. This is incorrect because this isn't
>the address of the machine who's name is the same as the parent
>folder (e.g. 'ce.berkeley.edu').
>
>I added another DNS server + Domain controller. Guess what!
>I now see three "A" records for the parent folder, with the
>new record containing the address of the new DNS + DC.
>
>In addition to these incorrect "A" records I'm also seeing
>"NS" records pointing to the new DNS servers but this
>is correct. What isn't correct is the additional "A"
>records. I turned on logging and I can see that the bogus
>records are coming from the DNS servers.
>
>Any idea why I'm seeing the incorrect entries?
>
>--
>Jon Forrest
>Computer Resources Manager
>Civil and Environmental Engineering Dept.
>205 Davis Hall
>Univ. of Calif., Berkeley
>Berkeley, CA 94720-1710
>510-642-0904
>
>
>
>
>
>
>------------------------------------------------------------------------
>The following was automatically added to this message by the list server:
>
>For information about Micronet, including subscribing to
>or unsubscribing from its mailing list and finding out
>about upcoming meetings, please visit the Micronet Web site:
><http://micronet.berkeley.edu/>.
>
------------------------------------------------------------------------
The following was automatically added to this message by the list server:
For information about Micronet, including subscribing to
or unsubscribing from its mailing list and finding out
about upcoming meetings, please visit the Micronet Web site:
<http://micronet.berkeley.edu/>.
This archive was generated by hypermail 2b29 : Tue Mar 05 2002 - 18:38:56 PST