RE: BDC IP changed in DNS

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance



Hi man,
I really am sorry I didn't mean it like that, I was only trying to point out
the importance of not using these terminologies any more since there is a
huge difference between PDC/BDC structure and the current Multi-Master
structure, but in all means I didn't mean to insult you or under estimate
your technical skills, so if you, or anyone else interpreted my message like
that, I do appologize and take my words back.

As for your technical problem, I suggest that you disable DNS Automatic
Updates as a first step to start troubleshooting this issue.

Have a nice day.
--
Ziad K. Chafi
MCT, MCTS, MCDBA, MCSE: S, MCDST
CompTIA A+, CompTIA N+,


"kelmel" wrote:

Well, Ziad....thank you for making me feel like an idiot for my terminolgy.
For one thing, when I go to Microsoft articles for help, this is the way they
are referred to in the articles. Also, if you will read what I posted again,
I have already manually changed the IP and it did not work....the IP reverted
back to the incorrect entry in DNS.

"Ziad K. Chafi" wrote:

Hi Kelmel,
First of all pleassssssssssssssse, stop using the terms PDC and BDC when
talking about 2000 servers and above, PDC and BDC are for Windows NT, from
Windows 2000 Server and above Microsoft implemented Multi-Master replication
for AD Servers.

As for your problem, try to change the IP manually in DNS and wait if you
see if it changed back or remains.
--
Ziad K. Chafi
MCT, MCTS, MCDBA, MCSE: S, MCDST
CompTIA A+, CompTIA N+,


"kelmel" wrote:

I have a Windows 2003 AD PDC and a Windows 2000 BDC running in a child
domain. I just realized last week that these two servers have stopped
talking. Using nslookup, I discovered that the IP for my BDC is incorrect.
Even though I have given it a static IP (that has not changed), DNS thinks it
is something different. I deleted the entries for the incorrect IP and added
the BDC back with the correct IP, changed the SOA and restarted the service
and still no luck. When I run dcdiag, I get the LDAP bind failed with error
31. Everything passes with netdiag except the DNS test (which tells me the
DNS registration is incorrect), DC List test and Trust Relationship. Also,
on both servers, when I try to replicate I get the message that the target
principal name is incorrect. I have followed the steps in KB article
288167...still no luck. Any help would be appreciated. One other thing,
when I looked in the event viewer to find out when this started happening,
the only other occurance that happened at the same time were critical
updates. Thanks!
.



Relevant Pages

  • RE: BDC IP changed in DNS
    ... For one thing, when I go to Microsoft articles for help, this is the way they ... talking about 2000 servers and above, PDC and BDC are for Windows NT, from ... try to change the IP manually in DNS and wait if you ... I discovered that the IP for my BDC is incorrect. ...
    (microsoft.public.windows.server.dns)
  • Re: Logon problems after beginning AD migration
    ... the machines that are logging into the non-2003 ... BDCs to the DNS servers in the 2003 domain, ... It was barely adequate for 2003 server, so after I had a BDC in place, I tried to transfer the FSMO roles to the BDC so I could demote and reload it. ...
    (microsoft.public.win2000.active_directory)
  • Re: Unable to authenticate users in windows 2003 SP1 secondary DC
    ... is it because my PDC hosts user folders and apps ... long as you have the domain setup to handle in accessible servers. ... domain in your forest) and that both dc's are dns servers for AD (The ... I have a PDC & BDC. ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT4 domain to 2003 server AD in place upgrade.
    ... And SMS 2 on a NT4 sp6a BDC. ... > of making NT host DNS since NT does not fully support DNS. ... > servers, will the se have any issues? ... the upgrade process will not infect them. ...
    (microsoft.public.windows.server.migration)
  • RE: BDC IP changed in DNS
    ... talking about 2000 servers and above, PDC and BDC are for Windows NT, from ... I discovered that the IP for my BDC is incorrect. ... Even though I have given it a static IP, DNS thinks it ...
    (microsoft.public.windows.server.dns)