Dns сервер ошибка 404

  • Remove From My Forums

  • Вопрос

  • сразу после установки windows server 2012 r2 standard появляются ошибки в DNS логах

    error log from Windows events:
    ====================================

    The DNS server could not open socket for address x.x.x.x. 
    Verify that this is a valid IP address for the server computer. 

    If this is a valid IP address for this machine, make sure that no other
    application (e.g. another DNS server) is running that would attempt to use the DNS
    port. 
    ===========================================
    The DNS server could not bind a Transmission Control Protocol (TCP) socket to
    address x.x.x.x. The event data is the error code. 
    ===========================================
    The DNS server could not bind a User Datagram Protocol (UDP) socket to
    x.x.x.x. The event data is the error code. 
    ===========================================

    ошибки появляются только при запуске сервера — единожды в процессе — не дублируются.

    1 это вообще нормально что на чистой установки сразу эти ошибки вылезают? их коды 408, 407, 404

    2 в какую сторону хотя бы примерно смотреть для и устранения? (топ 100гугла поверьте был прочитан — решения
    не нашел — как правило у многих они возникают в процессе работы — тут же сразу после инстала)

Ответы

  • Выглядит нормально. Ошибки появляются только при запуске сервера, но не при перезапуске службы сервера DNS? Тогда, скорее всего, дело в том, что сетевой интерфейс подключается и получает IP-адрес после старта службы сервера DNS. В таком случае, смотрите
    сами, насколько это критично

    Слава России!

    • Помечено в качестве ответа

      28 июля 2014 г. 17:42

Источник

In this tutorial, which is a special case, I will explain how to solve the 404, 407 and 408 error that can occur on a DNS server with Windows Server under the following conditions:

  • Being on a virtual machine
  • Being on a Hyper-V host
  • Have configured NIC teaming, which is configured as an external virtual switch with management enabled.

If you are in this particular configuration, it is possible that on your DNS server, you encounter the error 404, 407 and 408 at the level of the DNS server:

After several searches on the Internet and on the Microsoft doc, a resolution of this error is proposed here:https://docs.microsoft.com/fr-fr/troubleshoot/windows-server/networking/events-407-408-in-dns-server-event-log

Not fitting in this case, so I continued my research, having another DNS server running on another hyper-v host and this one having no problem, so I decided to look on the side of the Hyper-V host that hosts the DNS server that has this error.

Almost at the same time, on the Hyper-V host, an error is logged: MsLbfoSysEvtProvider (16945), which indicates a MAC address conflict.

After some research, this is a known problem at Microsoft and occurs when using network card teaming, which is used as a virtual switch WITH management enabled.

In a PowerShell command prompt, use the following cmdlet:

Get-NetAdapter | sort MacAddress

As you can see the MAC address of the “active” card is used on:

  • The Virtual Switch (Teaming)
  • The virtual network adapter (Ethernet (VM)) that is attached to the host.

Now that the observation is made, this problem must be solved, for this there are several solutions:

If the Hyper-V host is under Windows Server 2012R2 and +: it is possible to modify the MAC address of the Teaming cardhttps://social.technet.microsoft.com/wiki/contents/articles/31357.hyper-v-troubleshooting-mac-address-conflict-event-16945.aspx

If the Hyper-V host is running Windows Server 2016 or newer, configure teaming with a SET switch : https://rdr-it.com/hyper-v-commutateur-virtuel-avec-agregat-de-port-switch-embedded-teaming-set/

Источник

Ever since I installed this new server I get some reoccurring errors. Within the DNS portion I get the above event ID’s. None of which I am smart enough to track down and fix. Does anyone know where to make the changes? Of course the link to Microsoft goes to a «page cannot be found»

407 — The DNS server could not bind a User Datagram Protocol (UDP) socket to 10.0.0.3. The event data is the error code. Restart the DNS server or reboot your computer.

then

408 — The DNS server could not open socket for address 10.0.0.3.
Verify that this is a valid IP address for the server computer. If it is NOT valid use the Interfaces dialog under Server Properties in the DNS Manager to remove it from the list of IP interfaces. Then stop and restart the DNS server. (If this was the only IP interface on this machine and the DNS server may not have started as a result of this error. In that case remove the DNSParameters ListenAddress value in the services section of the registry and restart.)

If this is a valid IP address for this machine, make sure that no other application (e.g. another DNS server) is running that would attempt to use the DNS port.

For more information, see «DNS server log reference» in the online Help.

then

404 — The DNS server could not bind a Transmission Control Protocol (TCP) socket to address 10.0.0.3. The event data is the error code. An IP address of 0.0.0.0 can indicate a valid «any address» configuration in which all configured IP addresses on the computer are available for use.
Restart the DNS server or reboot the computer.

Then they repeat a couple of times  and end with ID 4013

4013 — The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.

Источник

Hi Experts,

Attempting to solve a slow network issue I have now stuffed up the DNS server!!!
Would appreciate help on how to correct.

Following error received when attempting to access the DC  — Windows cannot access error code 0x80070035

IN the DNS event log — errors 404 & 408

This happened after I performed the below steps of a MS Forum
—————————————————————————————————————————-
Please do as follows to remove the ‘::1’ DNS Server IP address:

 

1.    At a command prompt, type the following: netsh interface ipv6 show interfaces

 

2.    Make a note of the number shown in the Idx column of the output for your network adapter corresponding to the network adapter for which you wish to change DNS Server IP address.

 

3.    At the command prompt, type: netsh interface ipv6 delete dnsserver name=»ID» address=::1 (Where ID is the number from step 2.)

—————————————————————————————————————————-

 TIA

Andrew

Источник

I’m trying to setup AD/DNS on my new server running Windows 2012 R2. I’ve installed the roles, configured a static ip, made forward and reverse zones, etc. In the events list I see 408, 407, and 404 errors. When running dcdiag it fails on the connectivity test:

Testing server: Default-First-Site-NameDCName
   Starting test: Connectivity
      The host <numbers>._msdcs.domain.foo could not be resolved to an IP address. Check
      the DNS server, DHCP, server name, etc.
      Got error while checking LDAP and RPC connectivity. Please check your firewall settings.
      ......................... DCName failed test Connectivity

I’m concerned that perhaps the ip address is not configured correctly should the static ip and «DNS server» be the same?

Could it perhaps have something to do with the fact this is running as a virtual machine isolated from the internet?

EDIT

Event Text:
407 The DNS server could not bind a User Datagram Protocol (UDP) socket to <server ip>. The event data is the error code. Restart the DNS server or reboot your computer.

408 

The DNS server could not open socket for address <server ip>. 
Verify that this is a valid IP address for the server computer.  If it is NOT valid use the Interfaces dialog under Server Properties in the DNS Manager to remove it from the list of IP interfaces.  Then stop and restart the DNS server. (If this was the only IP interface on this machine and the DNS server may not have started as a result of this error.  In that case remove the DNSParameters ListenAddress value in the services section of the registry and restart.) 

If this is a valid IP address for this machine, make sure that no other application (e.g. another DNS server) is running that would attempt to use the DNS port. 

For more information, see "DNS server log reference" in the online Help.

404 

The DNS server could not bind a Transmission Control Protocol (TCP) socket to address <server ip>.  The event data is the error code.  An IP address of 0.0.0.0 can indicate a valid "any address" configuration in which all configured IP addresses on the computer are available for use. 
Restart the DNS server or reboot the computer.

Источник

Понравилась статья? Поделить с друзьями:
  • Dns сервер ошибка 4013
  • Dns сервер обнаружил ошибку при попытке загрузить зону
  • Dns сервер обнаружил ошибку 9002
  • Dns сервер обнаружил критическую ошибку active directory 4015
  • Dns сервер недоступен как исправить ошибку