Re: DNS problems after domain rename



Good netiquette suggest that you post how you resolved it so that others can benefit.... TIA....

Regards,
Hank Arnold

Dani P wrote:
I resolved the problem, thank you very much Laura Zhang:
-----------------------------------------------------------


Hi Dani,

Thank you for your posting.

If I understand properly, you renamed the domain from .net to .local. After
that, you found that the netlogon.dns file still have old domain .net
records. You have tried to delete the incorrect records; however, they were
added automatically.

According to the symptom, it seems that the old domain names still exist in
registry. To troubleshoot this problem efficiently, let us use the
Fixdomainsuffix.vbs file to correct the domain name on the two DCs.

1. Log on to the domain controller by using an account that has domain
administrator credentials.
2. Download and unzip the "Fixdomainsuffix.zip" attachment. Please double
click the Fixdomainsuffix.vbs file to run it.
3. Rename the following files in the "Windows\System32\config" folder:

netlogon.dns to netlogonold
netlogon.dnb to netlogon.old1

4. Restart the domain controller.
5. Repeat the above steps on the other DC.

Please check whether this problem continues. If this issue remains, please
run the following commands one by one on the two DCs:

ipconfig /flushdns
net stop netlogon
net start netlogon
ipconfig /registerdns
netdiag /fix

If this problem continues, please help me collect some information so that
I can perform further research on this issue:

1. Please export the
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters]
registry value to registry file on both DCs.
2. Please perform the following steps to collect the MPSReport of both DCs:

Download the MPSRPT_DirSvr.EXE file from the following website:

http://www.microsoft.com/downloads/details.aspx?FamilyId=CEBF3C7C-7CA5-408F-
88B7-F9C79B7306C0&displaylang=en

2) Double-click to run the MPSRPT_ DirSvr.EXE file and wait for it to
complete.
3) Send me the .cab file generated in the following folder:
systemroot%\MPSReports\Setup\<Report Type>\Cab

My email address is laurazh@xxxxxxxxxxxxxx You can send the above files to
my email address directly. As our email system blocks any files with .reg
extension, please first zip the registry files before you send it to me.
Thank you for your efforts.

More Information
----------------
257623 The DNS suffix of the computer name of a new domain controller may
not match the name of the domain after you upgrade a Windows NT 4.0 primary
domain controller to Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;EN-US;257623

Have a nice day!

Best regards,

Laura Zhang
Microsoft Online Partner Support

======================================================
PLEASE NOTE: The partner managed newsgroups are provided to assist with
break/fix issues and simple how to questions.

We also love to hear your product feedback! Let us know what you think by
posting

from the web interface: Partner Feedback
from your newsreader: microsoft.private.directaccess.partnerfeedback.

We look forward to hearing from you!
======================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
======================================================



.



Relevant Pages

  • Re: DNS problems after domain rename
    ... Fixdomainsuffix.vbs file to correct the domain name on the two DCs. ... Log on to the domain controller by using an account that has domain ... Rename the following files in the "Windows\System32\config" folder: ... registry value to registry file on both DCs. ...
    (microsoft.public.windows.server.general)
  • Re: Active Directory problem
    ... >> You might also want to configure the DCs in the branch offices not to ... >> When joining a computer to a domain, that same computer does not yet know ... >> from registering domain service records and will register only site wide ... they are not joining the correct domain controller (DNS is ...
    (microsoft.public.windows.server.dns)
  • Re: Missing DC in ADSS Default-first-site NTDS Settings
    ... Indeed the PDC Emulator is configured to use an external time source. ... All the DCs were built from scratch using the cd, and not rapidly deployed from images. ... The DC with the PDCEmulator role should be configured to use an external time source if not already done. ... but not the domain controller with the FMSO role of PDC ...
    (microsoft.public.win2000.active_directory)
  • Re: AD 2003 Replication Failure/Authentication Failure
    ... >Verify time is synchronized on all DCs. ... users can authenticate to the Seidler-root domain controller, ... users can authenticate to the enterprise domain controller. ...
    (microsoft.public.windows.server.active_directory)
  • Re: There are no more endpoints available... for Windows 2003 x64
    ... what you are trying to do is restrict AD activity to certain ports. ... The domain controller can't connect to the GC. ... are no more endpoints available from the endpoint mapper" I have running ... The registry file have this. ...
    (microsoft.public.windows.server.active_directory)