Fix dns windows 2008

Applies ToWindows Server 2008 R2 Standard Windows Server 2008 R2 Enterprise Windows Server 2008 R2 Datacenter Windows Server 2008 R2 Foundation

Symptoms

Consider the following scenario:

  • You install the DNS Server role on a computer that is running Windows Server 2008 R2.

  • You configure the DNS server to connect to a public DNS server on the Internet for name resolution.

  • You do not configure any forwarders on the DNS server.

In this scenario, the DNS Server service does not resolve some external DNS names after it works for a while. Therefore, you cannot access some applications or some websites that rely on these external DNS names.

Notes

  • To resolve this issue, you have to restart the DNS Server service or clear the DNS cache.

  • This issue usually occurs if you use the DNS Cache Locking feature in Windows Server 2008 R2.

Cause

This issue occurs because the DNS Server service cannot correctly handle the situation in which the glue record is expired or removed.

Resolution

Hotfix information

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:

  • Windows Server 2008 R2

  • Windows Server 2008 R2 Service Pack 1 (SP1)

For more information about how to obtain a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

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

Restart requirement

You must 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 2008 R2 file information notes

Important Windows 7 hotfixes and Windows Server 2008 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 7/Windows Server 2008 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, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.

    Version

    Product

    SR_Level

    Service branch

    6.1.760 0. 20xxx

    Windows Server 2008 R2

    RTM

    LDR

    6.1.760 1. 21xxx

    Windows Server 2008 R2

    SP1

    LDR

  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the «Additional file information for Windows Server 2008 R2» section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely 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 2008 R2

File name

File version

File size

Date

Time

Platform

Cache.dns

Not applicable

3,198

10-Jun-2009

20:31

Not applicable

Dns.exe

6.1.7600.20930

696,320

22-Mar-2011

05:15

x64

Dnsserver.events.xml

Not applicable

609

10-Jun-2009

20:31

Not applicable

Cache.dns

Not applicable

3,198

05-Nov-2010

01:52

Not applicable

Dns.exe

6.1.7601.21689

696,832

22-Mar-2011

05:08

x64

Dnsserver.events.xml

Not applicable

609

05-Nov-2010

01:52

Not applicable

Workaround

Workaround for Windows Server 2008 R2

To work around this issue, restart the DNS Server service. Or, type the following command at a command prompt, and then press ENTER to clear the DNS cache:

dnscmd /clearcache

Status

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

More Information

For more information about the DNS Cache Locking feature, visit the following TechNet website:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008 R2

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

File name

Amd64_626603afd074f82a85a123a8284b1a67_31bf3856ad364e35_6.1.7601.21689_none_e28975fd1d5ee264.manifest

File version

Not applicable

File size

710

Date (UTC)

23-Mar-2011

Time (UTC)

07:57

File name

Amd64_eb10c5926a17acb934a77496c4381161_31bf3856ad364e35_6.1.7600.20930_none_3853ac3a142a00de.manifest

File version

Not applicable

File size

710

Date (UTC)

23-Mar-2011

Time (UTC)

07:57

File name

Amd64_microsoft-windows-dns-server-service_31bf3856ad364e35_6.1.7600.20930_none_aab58b90093f26d7.manifest

File version

Not applicable

File size

158,131

Date (UTC)

22-Mar-2011

Time (UTC)

06:06

File name

Amd64_microsoft-windows-dns-server-service_31bf3856ad364e35_6.1.7601.21689_none_ac6ed9ae06860560.manifest

File version

Not applicable

File size

158,131

Date (UTC)

22-Mar-2011

Time (UTC)

05:42

Need more help?

Want more options?

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

Время на прочтение1 мин

Количество просмотров23K

Никогда не было, и вот опять Microsoft выпустили непротестированное обновление с критическим багом.

На этот раз пострадал DNS-сервер из состава Windows Server 2008 R2, который падает и больше не поднимается после установки KB3145126 из майского Patch Tuesday, а в журнале событий появляются сообщений вида:

Faulting application name: dns.exe, version: 6.1.7601.23375, time stamp: 0x56e06454
Faulting module name: dns.exe, version: 6.1.7601.23375, time stamp: 0x56e06454
Exception code: 0xc0000005

Лечится удалением этого патча командой wusa.exe /uninstall /kb:3145126 с последующей перегрузкой.

Update: Проблема оказалась в использовании CNAME для корневых записей «@» в конфигурации DNS-зон. Определить такие настройки поможет скрипт из KB2647170, который надо запускать при работающей службе DNS Server. Некорректные записи можно исправить в оснастке dnsmgmt.msc или удалить командой «DNSCMD /recorddelete DNS <имя зоны> @ cname» перед установкой KB3145126.

Ещё пострадавшие:
Heads up: Win2008 R2 & Microsoft Update (KB3145126) issue
KB3145126 Causing DNS.exe Crashes?
Windows 2008 R2 KB3145126 KILLED DNS

Всего голосов 12: ↑12 и ↓0

+12

Комментарии19

Quote from: ival on 31 May 2019, 14:34Что вообще у Вас там происходит?? Просто триллер какой-то. Есть отработанный механизм удаления нерабочих КД через ntdsutil, а потом ручками вычистить его из «Сайты AD» и DNS. Не надо никуда лезть ADSII-Edit’ом и править какие-то записи в NTDS.

Это не просто триллер, это фильм ужасов. Да, он удалял вышедший из строя домен, но, повторюсь, что-то пошло не так. Потому — что та запись не просто так нарушилась.

Рассказываю, снова да ладом, по порядку. Был у нас старый контроллер домена, но он вышел из строя. Просто сломался, перестал загружаться. Попытки его восстановить ни к чему не привели. Тем администратором был создан в существующем домене (остальные, в других подразделениях, Слава Богу пахали) vm-dc-01. Но так, как загрузить старый не представлялось возможным, то помимо удаления хлама (я не знаю, как точно он делал) пришлось производить захват FSMO. Он и захватил, опять же, не знаю как. Потом был создан vm-dc-02, но хозяин операций опять же vm-dc-01.

31.05.2019, как я уже говорил, перестал по непонятной причине работать DNS на vm-dc-01. Лог я скинул, там написано про первичную синхронизацию каталога, посмотрите. Я развернул третий контроллер домена, p2-dc-01, для того, чтобы в спешном порядке передать на него хозяев операций, но не успел. vm-dc-01 заработал. Тогда я по согласованию опять же с начальством принял решение, чтобы не засорять и не нарушать существующего положения дел, понизить и вывести из работы p2-dc-01. Так как при выводе возникла ошибка, скриншот в посте #12, то мне пришлось гуглить. А гугель выдал информацию о том, чтобы исправить схему. Я полез туда и обнаружил, что действительно, некорректно указано значение, в виде абракадабры, вместо названия сервера. Но это же сама по себе катастрофа! Как контроллер домена может нормально функционировать, если не может определить, кто хозяин?

Вот что было

CN=NTDS Settings\0ADEL:54c6470c-943f-4b46-9cbe-9683049ebf0f,CN=SERVER\0ADEL:f01947a3-7b35-4c4c-9313-d66396f4768b,CN=Servers,CN=P2-DFSN,CN=Sites,CN=Configuration,DC=pgfa,DC=local
Что стало, что я сделал

CN=NTDS Settings,CN=VM-DC-01,CN=Servers,CN=P2-DFSN,CN=Sites,CN=Configuration,DC=pgfa,DC=local

Fix DNS on Windows Server 2008

July 15, 2014 by admin · Leave a Comment
Filed under: How To Restart and Stop The DHCP Service on Windows Server 2008 

If you run into a situation where you can access your network drives yet are unable to get onto the internet, then you may have a problem with your DNS.

Your DNS is controlled by the DHCP server which you can find on the Windows Server 2008 by going to Server Manager > Roles > DHCP Server. Be sure that DHCP service is running.

Tags:

Comments are closed.

Updating DNS records on a Windows Server 2008 R2 is a crucial task for maintaining a well-functioning and secure network infrastructure. DNS (Domain Name System) is responsible for translating domain names into IP addresses, allowing computers to communicate with each other over a network. In this tutorial, we will guide you through the steps to update DNS records on a Windows Server 2008 R2.

Step 1: Open the DNS Manager by clicking on the Start menu and selecting «Administrative Tools.» From the list of tools, choose «DNS Manager.«

Step 2: In the DNS Manager window, expand the server’s name to reveal the list of Forward Lookup Zones. Select the zone where you want to update the DNS records.

Step 3: Right-click on the record you want to update, and select «Properties» from the context menu.

Step 4: The record’s properties window will open. Here, you can make the necessary changes to the record, such as the IP address or other attributes. Modify the required fields according to your needs.

Step 5: After making the necessary changes, click on the «Apply» button to save the updated DNS record.

Step 6: To verify that the DNS record has been successfully updated, you can run a DNS lookup using the command prompt. Open the command prompt by clicking on the Start menu and typing «cmd» in the search field. In the command prompt, type the following command: nslookup domain_name (replace «domain_name» with the actual domain you updated). If the correct IP address is displayed, the DNS record update was successful.

Pros Cons
1. Easy and straightforward process. 1. Requires administrative access to Windows Server.
2. Allows for precise control over DNS records. 2. May cause network disruption if not done correctly.
3. Provides flexibility in managing network resources. 3. Mistakes in updating DNS records can lead to service outages.

Updating DNS records on Windows Server 2008 R2 is a critical task to ensure accurate domain name resolution. By following these steps, you can effectively update the DNS records and maintain a reliable network infrastructure. Remember to double-check all changes before applying them to prevent any unintended consequences or disruptions.

Video Tutorial: What is the command to update DNS record?

How do I refresh my DNS?

Refreshing your DNS can help resolve network issues and improve internet connectivity. Here are the steps to refresh your DNS on various operating systems:

Windows:

1. Open the Command Prompt by typing «cmd» in the search bar and clicking on the Command Prompt app.
2. In the Command Prompt window, type «ipconfig /flushdns» and press Enter.
3. Wait for the DNS Resolver Cache to clear. You will see a message saying, «Windows IP configuration successfully flushed the DNS Resolver Cache.«
4. Close the Command Prompt window.

macOS:

1. Open the Terminal app. You can find it in the Utilities folder within the Applications folder or by using Spotlight Search.
2. In the Terminal window, type «sudo killall -HUP mDNSResponder» and press Enter.
3. Enter your administrator password when prompted, which won’t be visible as you type.
4. Wait for the command to execute and refresh your DNS cache.
5. Close the Terminal window.

Linux (Ubuntu):

1. Open the Terminal application.
2. In the Terminal window, type «sudo systemd-resolve –flush-caches» and press Enter.
3. Provide your user’s password when prompted.
4. Wait for the command to complete and refresh the DNS cache.
5. Close the Terminal window.

Android:

1. Open the Settings app on your Android device.
2. Depending on your device and Android version, navigate to the Wi-Fi or Network & Internet settings.
3. Tap on your currently active Wi-Fi network.
4. On the Wi-Fi’s details page, tap and hold on the network name until a menu appears.
5. Select the option «Forget network» or «Disconnect.«
6. After disconnecting, reconnect to the Wi-Fi network.
7. This will trigger a refresh of your DNS settings.

iOS:

1. Open the Settings app on your iPhone or iPad.
2. Tap on Wi-Fi, and then tap the (i) icon next to your currently connected Wi-Fi network.
3. Scroll down to find the option «Renew Lease.«
4. Tap on «Renew Lease» to refresh your DNS settings.

These steps should help you refresh your DNS cache on different operating systems. By doing so, you can resolve issues related to domain name resolution and potentially improve your internet browsing experience.

How do I manually update DNS records?

To manually update DNS records, you would typically need to access the control panel or management interface provided by your domain registrar or hosting provider. The specific steps may vary depending on the provider, but here is a general outline of the process involved:

1. Log in to your domain registrar or hosting provider account. This is where you initially registered your domain name or where your website is hosted.

2. Navigate to the DNS management section. This might be labeled as «DNS settings,» «Domain settings,» or something similar. Look for an option that allows you to manage your DNS records.

3. Identify the DNS record you want to update. Common types of DNS records include the A record (for mapping a domain to an IP address), CNAME record (for aliasing one domain to another), MX record (for email routing), and TXT record (for additional information like SPF records).

4. Make the necessary changes to the DNS record. This can involve editing existing records, adding new records, or deleting unwanted records. Ensure that you input the correct information based on your requirements. For example, if you want to update the IP address that your domain points to, modify the A record accordingly.

5. Save your changes. Depending on the interface, you may need to click on a «Save» or «Apply» button to confirm the modifications you made to the DNS records.

6. Wait for DNS propagation. DNS changes can take some time to propagate across the internet, typically ranging from a few minutes to several hours. During this period, some users may still see the old DNS information, while others will see the updated version, based on their ISP’s DNS caching.

7. Verify the changes. Once the DNS propagation is complete, you can verify if the DNS records accurately reflect your updates by using online DNS propagation checkers or by performing manual tests.

Remember, the process may slightly differ depending on your specific domain registrar or hosting provider. It’s always advisable to consult their documentation or support resources for detailed instructions tailored to their platform.

How do I flush and renew my DNS?

To flush and renew your DNS, follow these steps:

1. Open the command prompt: Press the Windows key, type «cmd,» and select the Command Prompt app.
2. In the command prompt, type «ipconfig /flushdns» and press Enter. This command will clear your DNS resolver cache.
3. Wait for the process to complete, which usually takes a few seconds.
4. Once the cache is flushed, type «ipconfig /registerdns» and press Enter. This command will refresh and update your DNS records with the DNS server.
5. Wait for the process to complete and verify that the registration is successful.
6. Close the command prompt and restart your computer to ensure the changes take effect.

By following these steps, you will successfully flush and renew your DNS, which can help resolve issues related to DNS cache, outdated records, or network connectivity problems.

Updating DNS records in Windows Server involves several steps. Here’s a guide on how to do it:

1. Open the DNS Manager: Press the Windows key, type «DNS» and select «DNS Manager» from the search results.

2. Connect to the DNS server: Right-click on the DNS server name in the DNS Manager console and select «Connect to DNS Server.» Choose «The following computer» and enter the server’s IP address or host name. Click OK to connect.

3. Navigate to the desired zone: Expand the DNS server folder and locate the Forward Lookup Zones or Reverse Lookup Zones folder depending on the type of DNS record you want to update. Find the specific zone containing the record you wish to modify.

4. Edit the DNS record: Double-click on the record you want to edit. In the record’s properties window, make the necessary changes in the appropriate fields. This could include updating the IP address, name, or other relevant information associated with the record.

5. Save the changes: Once you have made the required modifications, click OK to save the changes to the DNS record.

6. Verify the updated record: To ensure that the DNS record update has propagated, you can use various methods such as running nslookup commands or using online DNS lookup tools.

It’s important to note that the steps above assume familiarity with Windows Server and DNS management. It’s recommended to have a solid understanding of DNS and backup any critical DNS records before making changes to avoid potential issues.

How do I force DNS to refresh?

To force DNS (Domain Name System) to refresh, you can follow these steps:

1. Clear the DNS cache:
– On Windows:
– Open Command Prompt as an administrator.
– Run the command «ipconfig /flushdns» to clear the DNS cache.
– On macOS:
– Open Terminal.
– Execute the command «sudo killall -HUP mDNSResponder» to flush the DNS cache.

2. Change your DNS server:
– On Windows:
– Go to the Control Panel.
– Select «Network and Internet» > «Network and Sharing Center.«
– Click on your network connection.
– Go to «Properties» > «Internet Protocol Version 4 (TCP/IPv4).«
– Choose «Use the following DNS server addresses» and enter new DNS server addresses such as Google DNS (8.8.8.8, 8.8.4.4) or Cloudflare DNS (1.1.1.1, 1.0.0.1).
– On macOS:
– Open System Preferences.
– Select «Network» > your network connection.
– Click on «Advanced» > «DNS» tab.
– Remove existing DNS servers and click the «+» button to add new DNS server addresses like Google DNS (8.8.8.8, 8.8.4.4) or Cloudflare DNS (1.1.1.1, 1.0.0.1).

3. Restart your network devices:
– Power off your modem, router, or any other network devices you have.
– Wait for a few minutes and power them back on.
– This will restart the network and can sometimes resolve DNS issues.

4. Restart or flush your device’s DNS cache:
– On Windows or macOS:
– Restart your computer or device.
– Alternatively, you can also open Command Prompt or Terminal and execute the respective commands mentioned in step 1 to flush the DNS cache again.

By following these steps, you can force the DNS to refresh, potentially resolving any DNS-related issues and ensuring that your device can access the latest DNS records for websites and domains you visit.

How do I add records to DNS settings?

To add records to DNS settings, you would typically follow these steps:

1. Access your DNS management dashboard: This can usually be done through your domain registrar or web hosting provider. Look for a section or option related to DNS management.

2. Identify the DNS zone: Once you are in the DNS management dashboard, locate the DNS zone for the domain you want to modify. The DNS zone contains the DNS records that determine how your domain functions.

3. Choose the record type: Determine the type of DNS record you want to add. The most common types include A records, CNAME records, MX records, TXT records, and AAAA records. Each record type serves a different purpose, so choose the one that aligns with your specific needs.

4. Input the record details: For each record, you will need to provide specific details based on the record type. This can include the hostname (subdomain or domain), the IP address for A records, the target domain for CNAME records, the preference and mail server address for MX records, and any additional text for TXT records.

5. Save the changes: Once you have entered the record details, save your changes. The process of saving may vary depending on the DNS management interface you are using, but it is typically a button or option labeled «Save» or «Update DNS.«

6. Verify the changes: After saving the changes, it is recommended to verify the new DNS records to ensure they have propagated successfully. DNS propagation can take some time, usually a few hours or up to 48 hours, so it’s crucial to allow for this propagation period.

It’s important to note that the precise steps and options may differ depending on your specific DNS provider or hosting platform. Always refer to the documentation provided by your service provider for detailed instructions tailored to their system.

Понравилась статья? Поделить с друзьями:
0 0 голоса
Рейтинг статьи
Подписаться
Уведомить о
guest

0 комментариев
Старые
Новые Популярные
Межтекстовые Отзывы
Посмотреть все комментарии
  • Windows 10 обновляется в спящем режиме
  • Активатор ворд 2010 windows 10
  • Windows консольное приложение служба
  • Activate windows go to settings to activate windows как убрать
  • Как обновить видеокарту на компьютере windows 10