Server 2012 R2 DNS issue

I noticed an occurance today with one of our Server 2012 R2 Essentials Boxes. We have a domain setup on the server, but it's a simple setup for a small business. We don't have clients joined to the domain, we just use the users in the domain to control access to the server in the capacity of a file server. Our desktops have mapped drives with these domain credentials. Anyhow, on this said server, we specified in the network connection for the server, DNS settings to be obtained from our gateway. We had a power outage, which appeared to affect our ISP connection externally as it dropped(even though we had a UPS on all our networking equipment and server). Here is where the server reported DNS issues - unable to resolve webaddresses for for our off-site backup facility etc according to our logs. Power came back, and the internet returned, but our server didn't seem to catch the memo that internet has returned because it seemed that it was still unable to resolve DNS via the gateway - which was working fine for DNS via our other devices. I had to restart the server for it to catch itself. We have remote agents on this machine that appeared offline before the restart, now that are okay after the restart. Can anyone point to ideas as to why would this occcur? We've had power, network and internet outages in the past but the server always was able to have DNS via our gateway, and this was restored automatically . Any ideas? Thanks.

This person is a Verified Professional

PC Pharm Limited is an IT service provider.

Popular Topics in General Networking

Author Matt

there are a number of possibilities. Was it actually not able to resolve DNS when the ISP gateway was back up (you tested it)? Or could it be the remote agents just timed out and did not retry?

Default behavior if windows repeatedly gets no response from a dns server is to mark it down for 15 minutes and move to next in the list (in your case no other entry).

Best practice is the domain controller (essentials is a DC) should use itself for DNS. This wouldn't necessarily avoid the issue, but it may mitigate it to some degree as the dns server will always respond, just not be able to resolve whilst the internet link is down.

You make some good points and provided good information. Honestly, I didn't test for DNS because for some reason, it seemed that explorer hanged, and ALT+CTRL+Del didn't work. File services were working fine during all of this. I did browse the event log after my hard reset (because soft shutdown via Power button hung as well). I didn't get opportunity to test,  but things are okay now. Thank you for insight as to how Windows checks for DNS. I'll monitor the situation. Quite possibly, it didn't resolve itself because other services hung. I will. Investigate the service logs.

This topic has been locked by an administrator and is no longer open for commenting.

To continue this discussion, please ask a new question .

Read these next...

Curated Remote access a dual boot system

Remote access a dual boot system

Hi Team, I have a system with me which has dual boot os installed. I wanted to know if i can remote access this machine and switch between os or while rebooting the system I can select the specific os. Is there a way i can do that please help.

Curated Windows Server 2022 not shutting down

Windows Server 2022 not shutting down

So, first interaction here, so if more is needed, or if I am doing something wrong, I am open to suggestions or guidance with forum ettiquette. I'm excited to be here, and hope to be able to contribute. System Specs:Dell 5810 towerintel xeon 2697v3224gb E...

Curated Snap! -- Customizable AI Personalities, Time Travel Prototype, Grasshopper Bots

Snap! -- Customizable AI Personalities, Time Travel Prototype, Grasshopper Bots

Your daily dose of tech news, in brief. Welcome to the Snap! Flashback: March 3, 1971: Magnavox Licenses Home Video Games (Read more HERE.) Bonus Flashback: March 3, 1969: Apollo 9 launched (Read more HERE.) You need to hear this. N...

Curated There is no Admin (anymore)

There is no Admin (anymore)

I decided to let MS install the 22H2 build.  I had to remove the machine from the domain  Before doing that .  I added a "LocalAdmin" --  but didn't set the type to admin.  I realized I messed up when I went to rejoin the domain and was challenged.  ...

Curated What are some reputable on-prem password managers?

What are some reputable on-prem password managers?

After LastPass's breaches, my boss is looking into trying an on-prem password manager. What are some of the best ones? And what are the pros and cons vs cloud based?

Windows Server 2012 : Troubleshooting DNS (part 1) – Using the DNS Event Viewer to Diagnose Problems, Using the Nslookup Command-Line Utility

Using the dns event viewer to diagnose problems.

As any good administrator knows, Event Viewer is the first place to look when troubleshooting. Windows Server 2012 makes it even more straightforward to use because DNS events compiled from Event Viewer are immediately accessible from the DNS Manager Console. Parsing this set of logs can help you troubleshoot DNS replication issues, query problems, and other issues.

For more advanced event log diagnosis, you can turn on Debug Logging on a per-server basis. It is recommended that this functionality be turned on only as required, however, as this can affect server performance and the log files can fill up fast. To enable Debug Logging, follow these steps:

1.  Launch Server Manager from a Windows 2012 server with a full GUI.

2.  Select the DNS section. The list of servers in the server pool with the DNS role installed will be shown.

3.  Right-click the DNS server to configure and select DNS Manager.

4.  Select the DNS server name to configure.

5.  Right-click the server name and choose Properties.

6.  Select the Debug Logging tab.

7.  Check the Log Packets for Debugging check box.

8.  Configure any additional settings as required, and click OK.

By default, the log file is named dns.log and is saved in The C:\Windows\System32\dns\ directory. Listing 1 shows the debug of the DNS server dc1.companyabc.com of a lookup of the record www.cco.com from the server at 10.1.2.13. You can see from the log that the request was forwarded to the DNS server at 12.222.165.144 and that the results were then sent to the requesting server at 10.1.1.1.

Listing 1. DNS Log File

5/28/2012 6:48:32 PM 067C PACKET  000000BDAFD158A0 UDP Rcv 10.1.1.1        3b60 Q [0001   D   NOERROR] A      (3)www(3)cco(3)com(0) 5/28/2012 6:48:32 PM 067C PACKET  000000BDB0216410 UDP Snd 12.222.165.144  ebfc Q [0000       NOERROR] A      (3)www(3)cco(3)com(0) 5/28/2012 6:48:32 PM 067C PACKET  000000BDB0D8FF80 UDP Rcv 12.222.165.144  ebfc R Q [8084 A  R  NOERROR] A      (3)www(3)cco(3)com(0) 5/28/2012 6:48:32 PM 067C PACKET  000000BDAFD158A0 UDP Snd 10.1.1.1        3b60 R Q [8081   DR  NOERROR] A      (3)www(3)cco(3)com(0) 5/28/2012 6:48:58 PM 067C PACKET  000000BDB0A2B5B0 UDP Rcv 10.1.2.13       0006 Q [0001   D   NOERROR] A      (3)www(3)cco(3)com(10)companyabc(3)com(0) 5/28/2012 6:48:58 PM 067C PACKET  000000BDB0A2B5B0 UDP Snd 10.1.2.13       0006 R Q [8385 A DR NXDOMAIN] A      (3)www(3)cco(3)com(10)companyabc(3)com(0) 5/28/2012 6:48:58 PM 067C PACKET  000000BDB01CFCE0 UDP Rcv 10.1.2.13       0007 Q [0001   D   NOERROR] AAAA   (3)www(3)cco(3)com(10)companyabc(3)com(0) 5/28/2012 6:48:58 PM 067C PACKET  000000BDB01CFCE0 UDP Snd 10.1.2.13       0007 R Q [8385 A DR NXDOMAIN] AAAA   (3)www(3)cco(3)com(10)companyabc(3)com(0) 5/28/2012 6:48:58 PM 067C PACKET  000000BDB0D8FF80 UDP Rcv 10.1.2.13       0008 Q [0001   D   NOERROR] A      (3)www(3)cco(3)com(0) 5/28/2012 6:48:58 PM 067C PACKET  000000BDAFD158A0 UDP Snd 128.8.10.90     d511 Q [0000       NOERROR] A      (3)www(3)cco(3)com(0) 5/28/2012 6:48:59 PM 067C PACKET  000000BDAFD27B40 UDP Rcv 128.8.10.90     d511 R Q [0080       NOERROR] A      (3)www(3)cco(3)com(0) 5/28/2012 6:48:59 PM 067C PACKET  000000BDAFD158A0 UDP Snd 192.55.83.30    9b01 Q [0000       NOERROR] A      (3)www(3)cco(3)com(0) 5/28/2012 6:48:59 PM 067C PACKET  000000BDB09D48F0 UDP Rcv 192.55.83.30    9b01 R Q [0080       NOERROR] A      (3)www(3)cco(3)com(0) 5/28/2012 6:48:59 PM 067C PACKET  000000BDAFD158A0 UDP Snd 12.222.165.144  c2da Q [0000       NOERROR] A      (3)www(3)cco(3)com(0) 5/28/2012 6:48:59 PM 067C PACKET  000000BDAF446E30 UDP Rcv 12.222.165.144  c2da R Q [8084 A  R  NOERROR] A      (3)www(3)cco(3)com(0) 5/28/2012 6:48:59 PM 067C PACKET  000000BDB0D8FF80 UDP Snd 10.1.2.13       0008 R Q [8081   DR  NOERROR] A      (3)www(3)cco(3)com(0) 5/28/2012 6:48:59 PM 067C PACKET  000000BDB0A2B5B0 UDP Rcv 10.1.2.13       0009 Q [0001   D   NOERROR] AAAA   (3)www(3)cco(3)com(0) 5/28/2012 6:48:59 PM 067C PACKET  000000BDB0D8FF80 UDP Snd 12.222.165.144  7b4a Q [0000       NOERROR] AAAA   (3)www(3)cco(3)com(0) 5/28/2012 6:48:59 PM 067C PACKET  000000BDB0F3BB90 UDP Rcv 12.222.165.144  7b4a R Q [8084 A  R  NOERROR] AAAA   (3)www(3)cco(3)com(0) 5/28/2012 6:48:59 PM 067C PACKET  000000BDB0A2B5B0 UDP Snd 10.1.2.13       0009 R Q [8081   DR  NOERROR] AAAA   (3)www(3)cco(3)com(0)

The DNS log can be very detailed and tedious to read, but provides a wealth of information about exactly what the DNS server is doing. You can get even more detail by selecting the Details check box on the Debug Logging tab, which also enables you to see the data that was returned. Logging does add significantly to the load of the DNS server, so it should only be enabled when troubleshooting and disabled immediately afterwards.

Using Performance Monitor to Monitor DNS

Performance Monitor is a built-in, often-overlooked utility that allows for a great deal of insight into issues in a network. With regard to DNS, many critical DNS counters can be monitored relating to queries, zone transfers, memory utilization, and other important factors.

Client-Side Cache and HOST Resolution Problems

Windows 2000 and higher clients have a built-in client cache for name resolution that caches all information retrieved from name servers. When requesting lookups, the client resolver parses this cache first, before contacting the name server. Items remain in this cache until the TTL expires, the machine is rebooted, or the cache is flushed. In cases where erroneous information has been entered into the client cache, it can be flushed by typing  ipconfig /flushdns  at the command prompt.

By default, all clients have a file named HOSTS that provides for a simple line-by-line resolution of names to IP addresses. This file is normally located in \%Systemroot%\System32\Drivers\etc. Problems can occur when these manual entries conflict with DNS, and it is, therefore, wise to ensure that there are not conflicts with this HOSTS file and the DNS database when troubleshooting.

Using the Nslookup Command-Line Utility

The Nslookup command-line utility is perhaps the most useful tool for DNS client troubleshooting. Its functionality is basic, but the information obtained can do wonders for helping to understand DNS problems. Nslookup, in its most basic operation, contacts the default DNS server of a client and attempts to resolve a name that is inputted. For example, to test a lookup on www.companyabc.com, type  nslookup  www.companyabc.com at the command prompt. Different query types can also be input into Nslookup. For example, you can create simple queries to view the MX and SOA records associated with a specific domain by following these steps, which are illustrated in Figure 1:

1.  Open a command prompt instance by choosing Start, All Programs, Accessories, Command Prompt.

2.  Type  nslookup  and press Enter.

3.  Type  set query=mx  and press Enter.

4.  Type  domainname  and press Enter.

5.  Type  set query=soa  and press Enter.

6.  Type  domainname  and press Enter.

resolve dns issues windows server 2012

Nslookup’s functionality is not limited to these simple lookups. Performing an  nslookup /?  lists the many functions it is capable of. Nslookup is a tool of choice for many name-resolution problems and is a must in any troubleshooter’s arsenal.

Windows Server 2012 : Troubleshooting DNS (part 2) – Using the DNSCmd Command-Line Utility, Managing DNS with PowerShell

Related Articles

resolve dns issues windows server 2012

Complete Guide To New Features Of Windows Server 2012

Microsoft recently released the new Windows 8 Preview edition to familiarize developers with the upcoming Windows operating system. As we all known,  Microsoft often releases its Server shortly after a client Operating system release. Therefore, […]

resolve dns issues windows server 2012

Windows Server 2012 : Configuring Windows Firewall with Advanced Security

Understanding Windows Firewall with Advanced Security Windows Firewall with Advanced Security is a host-based, stateful firewall included in Windows Server 2012 and Windows 8. The feature was first introduced in Windows Vista and Windows Server […]

resolve dns issues windows server 2012

Windows Server 2012 : Monitoring System Performance – Monitoring System Memory and Pagefile Usage

1. Key Elements to Monitor for Bottlenecks As mentioned, four resources compose the common set of resources: memory and pagefile usage, processor, disk subsystem, and network subsystem. They are also the most common contributors to […]

WMLCLoud.com .

This browser is no longer supported.

Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.

I Have problem with DNS At windows server 2012 R2

13471-error-dns.jpg

And now what can i do to solve this problem ??!! Thank you Microsoft Team

Just want to confirm the current situations.

Please feel free to let us know if you need further assistance.

Best Regards, Sunny

Just checking in to see if the information provided was helpful.

If yes, you may accept useful reply as answer, if not, welcome to feedback.

Please run;

Dcdiag /v /c /d /e /s:%computername% >c:\dcdiag.log

and attach files to reply.

dcdiag ?! you mean dxdiag ? i'll try thank you

you mean dxdiag ?

(plus other files)

2 additional answers

Was there any recent network change that was done on the server, Is the DNS service running fine on the server ?Have you tried to reboot the DNS server and then check on the DNS server service status ?

Reboot and delete and create new zone i try all of them

Welcome the our new Microsoft Q&A Platform.

I noticed that there are so many Event 408, 407 and 404 in your event viewer. Please kindly check if the following articles could help you.

Event ID 408 - DNS Server Configureation

Event ID 407 - DNS Server Service Status

Event ID 404 - DNS Sever Service Status

Regarding the error "we can't sign you in with this credential because your domain isn't available. Make sure your device is connected to your organization's network and try again, if you previously sign in on this device with another credential, you can sign in with that credential", please kindly check if the following articles could help you.

we-cant-sign-you-with-this-credential-because-your-domain-isnt-available

how-to-fix-we-cant-sign-you-with-this-credential-error

Please note: Since the websites are not hosted by Microsoft, the links may change without notice. Microsoft does note guarantee the accuracy of this information.

Hope my answer will help you. Thanks!

--please don't forget to Accept as answer if the reply is helpful--

Stack Exchange Network

Stack Exchange network consists of 181 Q&A communities including Stack Overflow , the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Server Fault is a question and answer site for system and network administrators. It only takes a minute to sign up.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

DNS Issue Windows Server 2012

Background: I have a windows server 2012 install with AD, DNS and DHCP.

I also have a netopia router/modem providing my WAN access.

My router/modem is configured with DHCP off and connected to a 24 port switch. My WS2012 has static IP and uses the router/gateway as its default gateway for internet traffic and uses loopback for DNS. This WS2012 is also connected to same 24port switch.

The Problem:

My DNS server has forwarding enabled to my ISP's dns servers.

Here is the problem: All my workstations on the network are getting extremely slow internet access (.1-.2 Mbps). Connecting directly to the modem and setting static IP (and completely bypassing the WS2012) gets about 4-5 Mbps. The reason I think this is a DNS issue is because whenever I go into DNS manager and clear the Cache the internet on all machines runs at 4-5 Mbps for about 10-20 minutes and then slows to crawl again.

I have already checked my reverse lookup records and forward records and they seem to be in-tact.

This issue just arose about 1 week ago and this WS2012 has been in production for 6-7 months without a single hickup. No configuration changes have been made to this machine. Nobody has even logged into this machine (headless) since put into production besides a monthly reboot (from login screen via RDP).

PS. All internal traffic runs at full speed.

Michael Hampton's user avatar

So it worked fine with 8.8.8.8 as the original forwarder but not with your ISP's DNS servers?

That would seem to be the issue then, that your forwarders you have in place are causing slow DNS resolutions. You can easily confirm if DNS is causing this. Just use FileZilla and FTP into an FTP site via IP address (not FQDN) and then transfer a large file from that FTP site to you. If it runs at the right speed, then your issue is DNS resolution (and probably just your forwarders).

TheCleaner's user avatar

Your Answer

Sign up or log in, post as a guest.

Required, but never shown

By clicking “Post Your Answer”, you agree to our terms of service , privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged networking domain-name-system windows-server-2012 internet or ask your own question .

Hot Network Questions

resolve dns issues windows server 2012

Your privacy

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy .

How to diagnose and fix DNS problems

Dead websites, page loading issues, web not working as it should? Here's what to do next.

A laptop screen displaying a Page Not Found - Error 404 message

Browsing the web is so easy, simple and straightforward that it feels almost automatic. Sure, you know there's a lot of low-level tech making this happen, but who cares when it just works?

That only makes it more frustrating when you suddenly get major page loading issues, though, dead websites everywhere, and all kinds of other web-based complications.

Internet connectivity problems across multiple websites can look like something you'll never fix yourself, but that's not always true – they're often related to DNS (Domain Name System) problems. In this article we'll look at how to identify these, and then get your system working again.

What is DNS?

Accessing a new website looks simple, at least from user's point of view. Enter the URL in a browser, wait a few seconds, website appears, that's about it. Peek under the hood, though, and there's a lot more going on.

Your browser can't access a web server from a domain name like techradar.com, for instance. It can only find and download websites when it has a server IP address , such as 199.232.198.114.

A device normally handles this by asking your ISP's DNS server to translate the domain name into an IP address. Easy.

But what if DNS fails, and the server doesn't always return the IP address you need? Then you'll see major web problems.

What does a DNS issue look like?

If your DNS fails entirely then it's likely you'll see timeouts, DNS or other errors with all your internet apps. It might look like your entire internet is dead.

Other DNS failures are partial, though, affecting some websites only. Maybe you'll access sites a, b and c as usual, but x, y and z all seem to be down.

Partial failures can also cause odd-looking page loading issues. What if DNS allows you to access bigsite.com, but not the domain where it hosts its images, scripts or contact forms? 

You might see image placeholders, empty spaces where content used to be, or buttons and other site features not working as they should. It's this mix of problems across multiple sites that's one of the tell-tale signs of a DNS problem.

Diagnosing a DNS issue

The simplest DNS problem to diagnose is an issue with your current server. Try the same websites on a connection using another DNS server, and if they're now accessible and work correctly, it looks like you have a DNS issue.

If you've problems on a mobile device connected to your home Wi-Fi, for example, switching to your mobile network allows you to test a site with new DNS servers. 

Or if you're on the move and already using your mobile network, look for a free hotspot you can try. (Just for a quick connectivity test, though – free Wi-Fi can be a security risk causing more problems than it solves, and you should always use at least a cheap VPN to stay safe on these networks.)

No other connections available? Try the virtual online browser Browserling (opens in new tab) . If you can reach it, choose Chrome as your preferred browser, enter the URL in the address box and click Test Now! Browserling uses its own DNS to connect to the site, so if it gets you access and your own connection doesn't, it could be a DNS issue.

Test your DNS server

A more advanced test is to manually ask your DNS server for the IP address of the domain you're trying to access. If the server can't find the IP or displays an error, that points to a DNS difficulty.

To try this on Windows, click Start , type CMD and open Command Prompt , then type NSLOOKUP and press Enter. ( NSLOOKUP is often available on Macs and Linux – try opening it from your terminal window.) 

NSLOOKUP launches and displays the name and IP address of your current DNS server (or 192.168.* if devices get their DNS via your router's connection.)

Now type the name of any domain you can't currently access, press Enter, and NSLOOKUP queries your DNS server.

If NSLOOKUP displays the site IP address, it looks like DNS is working correctly.

But if NSLOOKUP displays an error like ' can't find Google.com: Non-existent domain ', that's pretty conclusive evidence that something is screwed up at the DNS level. Although there is one more quick trick you should try.

Try another DNS server

You've proved that your DNS server can't find an IP address for a domain, but will other DNS servers do any better? NSLOOKUP makes it really, really easy to find out.

Type SERVER 1.1.1.1 , press Enter , and NSLOOKUP changes its default DNS server to the IP address 1.1.1.1. (That's Cloudflare. If you know you were using Cloudflare before and that's the DNS with the problem, switch to Google's 8.8.8.8 , instead.)

Now enter whatever domain you couldn't reach earlier, and NSLOOKUP sends its DNS query to Cloudflare (or Google), instead.

If NSLOOKUP failed earlier but successfully gets an IP with Cloudflare, that looks like a problem affecting your DNS server only.

Test this by entering the IP address in your browser, instead of the regular domain. Use 142.250.179.238 for Google, for instance. If you can't access the website when you enter a domain, but it at least begins to load with the IP address, that confirms your DNS issues.

How to fix DNS problems

If it looks like your ISP's DNS isn't working, the quickest and most effective solution is to switch to a free public DNS server . Google and Cloudflare offer fast and reliable services which anyone can use, no registration required.

Changing DNS servers normally involves tweaking your device network settings. The Cloudflare (opens in new tab) support site has guides on setting up Cloudflare DNS for Windows, Mac, Android, iOS, routers, gaming consoles, Linux and more. These are sometimes very basic ('install app X to do it for you'), but Google's (opens in new tab) equivalent page has more detailed advice if you need it.

Whatever changes you make, be sure to note down your original settings first, just in case you need to switch them back later.

Reboot your device when you're done,  and it should now be using your (hopefully) problem-free new DNS server.

If you still have internet connectivity problems, though, it's time to ask your ISPs support team for help. Tell them what you've tried, and that should help them diagnose the issue and get your connection running smoothly again.

Are you a pro? Subscribe to our newsletter

Sign up to the TechRadar Pro newsletter to get all the top news, opinion, features and guidance your business needs to succeed!

Mike is a lead security reviewer at Future, where he stress-tests VPNs , antivirus and more to find out which services are sure to keep you safe, and which are best avoided. Mike began his career as a lead software developer in the engineering world, where his creations were used by big-name companies from Rolls Royce to British Nuclear Fuels and British Aerospace. The early PC viruses caught Mike's attention, and he developed an interest in analyzing malware, and learning the low-level technical details of how Windows and network security work under the hood.

Microsoft Logo

This forum is closed. Thank you for your contributions.

Windows Server 2012 DNS issue

I am unable to open certain microsoft websites on Windows Server 2012:

technet.microsoft.com

social.technet.microsoft.com

I am not able to fix this DNS problem

resolve dns issues windows server 2012

BleepingComputer.com logo

Microsoft: Recent Windows Server updates cause DNS issues

Sergiu gatlan.

Windows Server

Microsoft has addressed a new known issue causing DNS stub zones loading failures that could lead to DNS resolution issues on Windows Server 2019 systems.

DNS stub zones are copies of DNS zones containing resource records needed to determine the authoritative DNS servers for a specific zone and resolve names between separate DNS namespaces.

According to details published on the Windows health dashboard, customers will encounter this known issue only after installing updates released on January 25 and later.

"After installing updates released January 25, 2022 ( KB5009616 ) and later on affected versions of Windows Server running the DNS Server   role, DNS stub zones might not load correctly, which might cause DNS name resolution to fail," Microsoft  explained .

The other two Windows updates that might trigger these DNS resolution issues are  KB5010427 (released on February 15) and  KB5011551 (released two days ago, on March 22).

Microsoft has fixed this issue via the  Known Issue Rollback (KIR) feature . However, it will not propagate to affected devices automatically.

Group policies for deploying the KIR fix

To fix the DNS issues on enterprise-managed devices where the buggy Window Server updates have been installed, the admins will have to install and configure two group policies.

"For information on deploying and configuring these special Group Policies, please see   How to use Group Policy to deploy a Known Issue Rollback ," Microsoft added.

The two group policies admins need to install and configure to resolve this known issue can be downloaded using the links below:

Microsoft has previously fixed multiple issues linked to the Windows January updates, including a  Bluetooth issue causing Windows blue screens ,  Windows domain controller restarts caused by LSASS crashes ,  Netlogon issues , and a  Windows Active Directory bug .

Redmond also released out-of-band (OOB) emergency updates to address  issues caused by the January 2022 Patch Tuesday updates .

The problems they addressed were related to Windows Server Domain Controllers restarting, Virtual Machines failing to start, VPN connectivity, and ReFS-formatted removable media mount failures.

Related Articles:

Microsoft says Intel driver bug crashes apps on Windows PCs

Microsoft fixes ODBC connections broken by November updates

Microsoft shares temporary fix for ODBC database connection issues

Microsoft releases Windows security updates for Intel CPU flaws

Microsoft fixes bug behind apps not installing during provisioning

I_Rogue Photo

I_Rogue - 11 months ago

Every month we are lab rats.

BxN88 Photo

BxN88 - 11 months ago

This issue occurred since Cumulative Update of January - It took 3 month to Microsoft to ack this issue. We have an open case open at Microsoft prior to this announcement and we still wait for a fix. Really a pain to troubleshoot.

Post a Comment Community Rules

You need to login in order to post a comment.

Not a member yet? Register Now

You may also like:

Credit Cards

BidenCash market leaks over 2 million stolen credit cards for free

TPM cpu chip process secured

New TPM 2.0 flaws could let hackers steal cryptographic keys

Malwarebytes Anti-Malware Logo

Malwarebytes Anti-Malware

AdwCleaner Logo

Windows Repair (All In One)

Everything Desktop Search

Zemana AntiLogger Free Logo

Zemana AntiLogger Free

Sign in with Twitter button

Help us understand the problem. What is going on with this comment?

Read our posting guidelinese to learn what content is prohibited.

Before you go...

Check out today's top deals.

Plus, get free shipping and easy returns.

HP TECH TAKES /...

How to Resolve DNS Issues

How to Resolve DNS Issues

What is dns, signs of a dns error.

How to resolve DNS issues

1. Rule out ISP issues

2. Restart your networking equipment

Restart Networking Equipment

3. Flush DNS cache and reset winsock

4. Perform a clean reboot

5. Run the Microsoft LLDP Protocol Driver

6. Update network adapter driver and reinstall if needed

7. Change to public Google DNS servers

8. Check power settings

What to do if your DNS issues aren’t resolved

About the author.

Linsey Knerl is a contributing writer for HP® Tech Takes. Linsey is a Midwest-based author, public speaker, and member of the ASJA. She has a passion for helping consumers and small business owners do more with their resources via the latest tech solutions.

Popular articles

Related tags

The HP Garage

Article archives

Disclosure: Our site may get a share of revenue from the sale of the products featured on this page.

resolve dns issues windows server 2012

DNS server does not try the second forwarder and other DNS improvements in Windows Server 2012 R2

This article describes some Domain Name System (DNS) related issues that occur in Windows Server 2012 R2. A hotfix is available to resolve these issues. The hotfix has a  prerequisite .

Assume that you have a computer that is running Windows Server 2012 R2. You may encounter one of the following issues: Issue 1 The DNS server does not try the second forwarder if the first forwarder does not respond. Issue 2 If the forwarder responds a SERVFAIL error, then the recursive resolver waits for recursion time-out period before responding back the same to the client. Issue 3 It takes a long time (about 10 minutes) to load of large number of zones (40,000 to 50,000 zones). This is optimized to load in few seconds (about 15 seconds) now. See  DNS Server Startup Time Improvements in Windows Server 2012 R2 for details.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain the hotfix. Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:

http://support.microsoft.com/contactus/?ws=support Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows Server 2012 R2.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2012 R2 file information and notes

Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1/Windows Server 2012 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.

The files that apply to a specific product, milestone (RTM, SP n ), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.

For all supported x64-based versions of Windows Server 2012 R2

Additional file information

Additional file information for Windows Server 2012 R2

Additional files for all supported x64-based versions of Windows Server 2012 R2

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

See the terminology that Microsoft uses to describe software updates.

Facebook

Need more help?

Want more options.

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

resolve dns issues windows server 2012

Microsoft 365 subscription benefits

resolve dns issues windows server 2012

Microsoft 365 training

resolve dns issues windows server 2012

Microsoft security

resolve dns issues windows server 2012

Accessibility center

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.

resolve dns issues windows server 2012

Ask the Microsoft Community

resolve dns issues windows server 2012

Microsoft Tech Community

resolve dns issues windows server 2012

Windows Insiders

Microsoft 365 Insiders

Was this information helpful?

Thank you for your feedback.

resolve dns issues windows server 2012

IMAGES

  1. How to Fix "The DNS Server Isn't Responding" Error in Windows 10

    resolve dns issues windows server 2012

  2. Fix: DNS issues on Windows 10

    resolve dns issues windows server 2012

  3. Resolved DNS server is not responding Error in Windows 10

    resolve dns issues windows server 2012

  4. How to Resolve DNS Issues on Windows 10

    resolve dns issues windows server 2012

  5. PowerShell: Query DNS Server for A, PTR, MX, NS and other records

    resolve dns issues windows server 2012

  6. How to fix "DNS server isn't responding" error in Windows 10

    resolve dns issues windows server 2012

VIDEO

  1. How to Track Tools With IoT

  2. مشكل البوكماب . الجزء 2 . Lic.emu can't resolve DNS !

  3. How To Install & Configure DNS Service Quick & Simple

  4. How To Resolve DNS Issue In Windows XP

  5. Windows DNS Server Settings

  6. How to Resolve DNS Server Not Responding Problem in Windows PC

COMMENTS

  1. Troubleshooting DNS Servers

    Try to restart the DNS Server service by entering the following at a command prompt on the server: Windows Command Prompt net start DNS If the issue occurs when the service is running, the server might not be listening on the IP address that you used in your nslookup query.

  2. [SOLVED] Server 2012 R2 DNS issue

    Default behavior if windows repeatedly gets no response from a dns server is to mark it down for 15 minutes and move to next in the list (in your case no other entry). Best practice is the domain controller (essentials is a DC) should use itself for DNS.

  3. Troubleshoot DNS name resolution on the Internet

    To manually add root hints on a Windows Server DNS server that is not configured as a domain controller: Click Start, point to Administrative Tools, and then click DNS. In the right pane, right-click ServerName, where ServerName is the name of the server, and then click Properties. Click the Root Hints tab, and then click Add.

  4. Troubleshooting Domain Name System (DNS) issues

    To collect a Windows Networking Diagnostic from an affected client and its configured DNS server, follow these steps: Start network captures on the client and server: Windows Command Prompt Copy netsh trace start capture=yes tracefile=c:\%computername%_nettrace.etl Clear the DNS cache on the DNS client by running the following command:

  5. DNS name resolution and DNSSEC validation fail in Windows Server 2012

    This article describes problems that occur on a Domain Name System (DNS) server in Windows Server 2012 R2. A hotfix is available to resolve these problems. The hotfix has a prerequisite. Symptoms You experience one of the following problems on a computer that is running Windows Server 2012 R2. Problem 1

  6. Windows Server 2012 : Troubleshooting DNS (part 1)

    Launch Server Manager from a Windows 2012 server with a full GUI. 2. Select the DNS section. The list of servers in the server pool with the DNS role installed will be shown. 3. Right-click the DNS server to configure and select DNS Manager. 4. Select the DNS server name to configure. 5. Right-click the server name and choose Properties. 6.

  7. How to troubleshoot errors that occur when you join Windows-based

    Disconnect all previous connections to the server or shared resource and try again. Resolution Restart the computer that you are trying to join to the domain to make sure that there are no latent connections to any of the domain servers. When you type the domain name, make sure that you type the DNS name and not the NetBIOS name. Error 5

  8. Resolved issues in Windows Server 2012

    Find information on recently resolved issues for Windows Server 2012. To find a specific issue, use the search function on your browser (CTRL + F for Microsoft Edge). For immediate help with Windows update issues, use Get Help in Windows or go to support.microsoft.com. Follow @WindowsUpdate on Twitter for Windows release health updates.

  9. I Have problem with DNS At windows server 2012 R2

    I Have problem with DNS At windows server 2012 R2 i was setup new domain in my company and the server was stability but now i have many errors at DNS And if i create new user or other user he cant join to any pc and type this message "we can't sign you in with this credential because your domain isn't available.

  10. Problem with Name resolution in DNS server 2012 R2

    Hi All, We are having DNS role on Server 2012 R2. some of our clients has changed their Public IPs. when we are resolving those name from our Local DNS server, it first try to resolve previous IP, if try again then resolve to new IP. we check dns Cache, there is no cache and there is no old records. Labels: Networking 20.6K Views 0 Likes

  11. networking

    The Problem: My DNS server has forwarding enabled to my ISP's dns servers. Here is the problem: All my workstations on the network are getting extremely slow internet access (.1-.2 Mbps). Connecting directly to the modem and setting static IP (and completely bypassing the WS2012) gets about 4-5 Mbps. The reason I think this is a DNS issue is ...

  12. Update to fix name resolution failure and other DNS issues on a Windows

    Issue 1 Name resolution for some external websites fails on a Windows Server 2012-based DNS server that uses Internet root hints. Issue 2 An incorrect Canonical Name (CNAME) record is returned by the DNS server when it processes an answer that contains a Delegation Name (DNAME) record. Issue 3

  13. How to diagnose and fix DNS problems

    If the server can't find the IP or displays an error, that points to a DNS difficulty. To try this on Windows, click Start, type CMD and open Command Prompt, then type NSLOOKUP and press Enter ...

  14. Windows Server 2012 DNS issue

    I am unable to open certain microsoft websites on Windows Server 2012: technet.microsoft.com social.technet.microsoft.com I am not able to fix this DNS problem

  15. Microsoft: Recent Windows Server updates cause DNS issues

    To fix the DNS issues on enterprise-managed devices where the buggy Window Server updates have been installed, the admins will have to install and configure two group policies.

  16. How To Resolve DNS Issues

    By checking for network adapter driver updates and manually updating them, you may resolve your DNS issues. To check for driver updates: Type devmgmt into the Windows Start Menu search bar and open the Device Manager app. Go to the Network adapters section in the list, and click to expand it.

  17. DNS server does not try the second forwarder and other DNS improvements

    A hotfix is available to resolve these issues. The hotfix has a prerequisite. Symptoms. Assume that you have a computer that is running Windows Server 2012 R2. You may encounter one of the following issues: Issue 1 The DNS server does not try the second forwarder if the first forwarder does not respond. Issue 2