Windows 10: Strange DNS Issues - Trying to add a Windows 11 Desktop to a domain

Good Afternoon,So I got a CyberGeek mini PC for use as a jump box or quick testing box. I have a small network at the house... Where this issue is. My Network is:1 Meraki MS2200 24 Switch2 Meraki MX64 Firewall 3 UCS C200 M2 Rack Mount server4 Buffalo NAS 5TBOn the server I have a VM that is my domain controller my domain is: slappy.home and it is running the DNS Server. On the DNS Server I have added the A HOST record for the new device. I also have the DNS prescribed in the Adapter settings IPV4. I can ping every device and VM in the network from the new device... IF I just

:)

 

Windows 11 - DNS issue

Hello

I am currently testing the compatibility of our organization with Windows 11 and I am facing a strange behavior. The DNS service is not working well with Windows 11.

On Windows 10 there is no issue and all the IP addresses are resolved correctly from our DNS, but on Windows 11, the DNS results are strange:

- If the request belongs to our main domain, nslookup provides the correct internal IP address

- If the request belongs to an internal domain only, nslookup provides the correct internal IP address

- If the request belongs to any other domain, nslookup provides the public IP address instead of the internal IP address

This is only happening from the internal network. If I connect by VPN, using the same DNS servers, then the result is correct in every case.

Has anybody experienced the same issue? Is this a problem of the Windows 11 desktop, the DNS server...?

Thanks in advance

Best regards

Yann

 

Raising the windows domain and forest issues?


hi,

I run a domain that was all 2003 r2 servers. I recently upgraded all my domain controllers to windows 2012 r2.
That went off without any problems.. Our trust relationships had no issues also.

My first step was to raise the Domain and Forest levels past 2003 to 2008. This went off without a hitch.
These are the features for raising the levels to 2008:

• Features and benefits include all default Active Directory features, all features from the Windows Server 2003 domain functional level, plus:
• Read-Only Domain Controllers – Allows implementation of domain controllers that only host read-only copy of NTDS database.
• Advanced Encryption Services – (AES 128 and 256) support for the Kerberos protocol.
• Distributed File System Replication (DFSR) – Allows SYSVOL to replicate using DFSR instead of older File Replication Service (FRS). It provides more robust and detailed replication of SYSVOL contents.

Forest Level Windows Server 2008

• Features and benefits include all of the features that are available at the Windows Server 2003 forest functional level, but no additional features. All domains that are subsequently added to the forest will operate at the Windows Server 2008 domain functional level by default.

My next step is to raise the domain and forest to 2008 r2, then 2012, and finally 2012 r2. I have been trying to find out exactly what I could expect from raising the Domain and Forest for each step.

The step involving 2008 r2 seems relatively a non issue. But getting the couple of new features seem very nice

Domain Level Windows Server 2008 R2

• All default Active Directory features, all features from the Windows Server 2008 domain functional level, plus 2 new features

Forest Level Windows Server 2008 R2

• All of the features that are available at the Windows Server 2003 forest functional level, plus the following features:

• Active Directory Recycle Bin, which provides the ability to restore deleted objects in their entirety while AD DS is running. <== New Feature very cool
• All domains subsequently added to the forest will operate at the Windows Server 2008 R2 domain functional level by default.

Here is my big concerns for the next raising of domain and forest to 2012.

Forest Level Windows Server 2012:

• All of the features that are available at the Windows Server 2008 R2 forest functional level, but no additional features.
• All domains subsequently added to the forest will operate at the Windows Server 2012 domain functional level by default.

Domain Level Windows Server 2012 R2: <=====Need to investigate more and why this post

• DC-side protections for Protected Users. Protected Users authenticating to a Windows Server 2012 R2 domain can no longer:

• Authenticate with NTLM authentication <==============(what issues may arise)
• Use DES or RC4 cipher suites in Kerberos pre-authentication
• Be delegated with unconstrained or constrained delegation
• Renew user tickets (TGTs) beyond the initial 4-hour lifetime

Will this affect my exchange anywhere users with remote access authenticating either clear of NTLM???
and what would/may not to work properly day 1 when I raise the domain and forest to 2012. I cant really find anyone that can answer a straight question.

Has anyone gone through this? what problems did you have, if any , if a lot???

Any thoughts and suggestions will be much appreciated??

thanks


- - - Updated - - -

One more point... I am not sure if I posted this to the correct forum.. So if I was wrong and it should be in a different one..
PLEASE LET ME KNOW

 

DNS server causing problem

Hi Andrea,

DNS is a server that translates websites' addresses so that browsers can connect to them. If the addresses become outdated or the server has issues, problems and DNS errors occur. For us to provide an accurate solution, we would need you to answer the following
questions:

• Which build, version and edition of Windows is installed on your computer?
• What changes have you made to your device before this issue occurred?
• Are you experiencing the same issue regardless if you are trying to be connected to a wired or wireless connection?

For initial troubleshooting, we suggest deleting the DNS cache. This can refresh the DNS files and settings on your PC. Follow these steps to delete the DNS cache:

• Using Search type Command Prompt.
• Form the search results, right click on Command Prompt (Desktop app) and then choose Run as administrator.
• In the Command Prompt window, type ipconfig /flushdns and then hit the Enter key.
• Once done, restart your computer and then check if the same issue persists.

We are looking forward to your response.