NS Record dynamically updates wrong?

I have a single domain.local domain.

The main DC is a DNS and DHCP Server also.

Main DC has a single IP of 192.168.0.6
Second DC is 192.168.0.9
Third DC is 192.168.0.18

There are two NS Records, one for lessrv1.domain.local (the main DC) and
there is one NS record for domain.local.

Every so often, the third DC ip address of 192.168.0.18 shows up in the
nameserver tab for domain.local. The second DC never shows up. I remove it
and it comes back.

This is causing some authentication problems for an Exchange 2007 server I
am setting up, as well as causing some other authentication issues from
workstations. When I remove the 192.168.0.18 address, things go back to the
way they should be as the 192.168.0.6 is the correct IP for the domain.

DCDiag passes all tests


Am I missing something here?

Can someone point me in the right direction so that the 192.168.0.18 address
does not appear in the NS record?


I've posted the DNSDiag below.

--

Steve D.
Computer Tech
Somewhere in Vermont

==============================
C:\Documents and Settings\admin.000>dnsdiag ludlow.local -d -a -s
192.168.0.18 1
92.168.0.6
Running in debug/verbose mode.


Querying DNS server: 192.168.0.18
Created Async Query:
--------------------
QNAME = ludlow.local
Type = MX (0xf)
Flags = UDP default, TCP on truncation (0x0)
Protocol = UDP
DNS Servers: (DNS cache will not be used)
192.168.0.18

Connecting to DNS server 192.168.0.18 over UDP/IP.
Connected to DNS 192.168.0.18 over UDP/IP.
Connection dropped by DNS server - Win32 error 1234.
Marking DNS server 192.168.0.18 as down.
No working DNS servers to retry query with.


Querying DNS server: 192.168.0.6
Created Async Query:
--------------------
QNAME = ludlow.local
Type = MX (0xf)
Flags = UDP default, TCP on truncation (0x0)
Protocol = UDP
DNS Servers: (DNS cache will not be used)
192.168.0.6

Connecting to DNS server 192.168.0.6 over UDP/IP.
Connected to DNS 192.168.0.6 over UDP/IP.
Response received from DNS server.
Received DNS Response:
----------------------
Error: 0
Description: Success
These records were received:
ludlow.local MX 10 2ships.ludlow.local
2ships.ludlow.local A 192.168.0.100

Processing MX/A records in reply.
Sorting MX records by priority.

Target hostnames and IP addresses
---------------------------------
HostName: "2ships.ludlow.local"
192.168.0.100
Shutting down ATQ
Shutting down IISRTL
Exit code: 0
.

Relevant Pages

  • Re: Replication issues
    ... I wanted to say Zone Transfers not Zone Forwarding. ... AD-Integrated DNS does not do zone transfers between the ... your DNS server will bypass ...
    (microsoft.public.windows.server.active_directory)
  • Re: Servers hang on boot
    ... The last DC at that site (not a DNS server). ... EventID: 0x00000457 ... (Event String could not be retrieved) ...
    (microsoft.public.windows.server.networking)
  • Re: DNS Redesign Issue
    ... set the new child domain DNS server as primary for the domain controllers? ... -If you are going to create a new AD Integrated Zone in each child domain, ...
    (microsoft.public.windows.server.dns)
  • Re: Internet connection wizard
    ... turn on DHCP on the workstation. ... Connection-specific DNS Suffix. ... calling CNetCommit::ValidateRouterConnectionProperties. ... Call to Reading preferred DNS server IP returned ok. ...
    (microsoft.public.windows.server.sbs)
  • Re: RPC Endpoint Mapper Error
    ... Event Type: Warning ... I checked DNS entries with articles from Microsoft on ... PASS - All the DNS entries for DC are registered on DNS server ... List of NetBt transports currently bound to the Redir ...
    (microsoft.public.win2000.active_directory)
Loading