DNS records SOA and Name server are replaced with servername.

Question

We are replacing our old windows 2008R2 server. We are reusing the domain name on a new windows 2022 std installation. The first weird thing that happened is the administrator password stopped working and we had to reset with Windows repair command line to get the machine on line. SFC comes up with no errors. Server was removed for old domain put in workgroup. Rebooted Name changed Rebooted Add roles Active Directory, DNS and DHCP. Installed showed no errors. Rebooted. AD users added to the system. AD appears to be ok. At least we hope so. When I exit to the command prompt it shows the old computer name not what I would have expected when I drop from admin desktop to a command prompt. Then configured DNS same domain name as old domain. xx.local The Zones did not publish as expected so we added the recording manually to Forward and Reverse lookup. Forward lookup and reverse lookup as they did not populate with anything when the wizard was run. I worked with Dell engineer for 6 1/2 hour and we added records manually but we cannot find where the servername. record is coming from or how to fix it. We uninstalled DNS rebooted and then installed DNS - same exact response. I ran sfc /scannow. The guid for the AD does not get added in DNS as expected. If anyone know a fix I am in a huge issue. Just need a recommendation on whether to remove all roles reboot - and start over. Is there something wrong in the OS load? Servername. is the new machine name and I can find nothing in the registry with servername.

Answer 1

Hello Aggie,

Hope you have a lovely day!

Based on the information provided, it seems like there may be some issues with the DNS configuration on the new Windows Server 2022 installation. Here are some steps you can take to troubleshoot the issue:

1.Administrator Password Issue:

• Since the administrator password stopped working after the migration, it's possible that the password policy or account settings were not properly transferred or configured during the setup. Ensure that the password meets the complexity requirements and try resetting it again.

2.Old Computer Name in Command Prompt:

• The old computer name appearing in the command prompt might indicate that the renaming process wasn't successful. Double-check the computer name settings in the System properties to ensure it's updated correctly
• Check the DNS server settings on the new server to ensure that it is pointing to itself as the primary DNS server. You can do this by going to the network adapter settings and checking the DNS tab.

---

3. Check the DNS zone settings to ensure that the SOA and Name server records are pointing to the correct server name.

You can do this by opening the DNS Manager console, expanding the Forward Lookup Zones folder, right-clicking on the zone, and selecting Properties.

Then, go to the SOA tab and check the Primary server field, and go to the Name Servers tab and check the list of name servers.

4. Check the DNS cache on the new server to ensure that there are no stale records causing issues.

You can do this by opening the command prompt and running the command "ipconfig /flushdns".

5. Check the event logs on the new server for any DNS-related errors or warnings that may provide more information about the issue.

If none of these steps resolve the issue, it may be necessary to remove all roles, reboot, and start over. However, before doing so, it may be helpful to consult with a Microsoft support professional to ensure that all necessary steps are taken to avoid any potential data loss or other issues.

Best Regards

Rosy