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

  • 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

Источник


Posted: November 28, 2014 in Windows

Symptoms:

You are unable to query a Microsoft Windows 2000-based DNS server, and the following errors are reported in the application event log for DNS Server:

Event ID: 407
Source: DNS
Description: DNS server could not bind a datagram (UDP) socket to
IP_address. The data is the error.

Event ID: 408
Source: DNS
Description: DNS Server could not open socket for address [IP_address]. Verify that this is a valid IP address on this machine. 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 DNS\Parmeters\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.

Cause:

These errors can occur on computers that have both of the following services installed on the same server:

  • Network Address Translation (NAT)
  • DNS Server

NAT has a DNS proxy setting that enables Dynamic Host Configuration Protocol (DHCP) clients to direct DNS queries to the NAT server. The client DNS queries are then forwarded to the NAT server’s configured DNS server. DNS proxy and the DNS Server service cannot coexist on the same host if the host is using the same interface and Internet protocol (IP) address with the default settings.

Resolution:

To resolve this issue, use any of the following methods:

  • Use a different server for DNS Server, instead of installing NAT and DNS Server on the same host.
  • Do not use the DHCP allocator and DNS proxy functionality in NAT (use the DHCP Server service instead).
  • Configure DNS Server so that it does not listen on the IP address of the network adaptor that is functioning as the private interface for NAT. To do this, follow these steps:
    1. Start the DNS snap-in in the Microsoft Management Console (MMC), right-click the DNS server, and then clickProperties.
    2. Click the Interfaces tab, and then in the Listen on section, click to select the Only the following IP addressescheck box.
    3. Click the IP address that you do not want the server to listen on, and then click Remove.
    4. Click OK and close the DNS snap-in.

NOTE: When an IP address is removed from the Interfaces list on the DNS server, the DNS Server service does not respond to DNS queries that are directed to that IP address. DNS queries that need to be resolved by DNS Server must be directed to other interfaces that DNS Server is listening on.

Источник

Could you provide a screenshot of the issue or maybe explain it a little more? Just posting the technet article doesn’t really explain your precise issue, and may not even be the root cause. The more info you provide, the more help you can get.


Was this post helpful?
thumb_up
thumb_down

Author Victor Serafim

Basically can’t connect to internet via server. 
I’ve done tracert on both server and pc to which both completed and are identical just when loading a browser it won’t load anything.  


Was this post helpful?
thumb_up
thumb_down

nathan7757 wrote:

Basically can’t connect to internet via server. 
I’ve done tracert on both server and pc to which both completed and are identical just when loading a browser it won’t load anything.  

What is the IP config of the server? Have you checked your DNS forwarders?


Was this post helpful?
thumb_up
thumb_down

Author Victor Serafim

Microsoft Windows [Version 6.1.7601]

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Administrator>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : FIN@@@@@

Primary Dns Suffix . . . . . . . : fins@@@@@

Node Type . . . . . . . . . . . . : Hybrid

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

DNS Suffix Search List. . . . . . : fins@@@@@

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller

Physical Address. . . . . . . . . : 10-C3-7B-4A-27-E5

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Link-local IPv6 Address . . . . . : fe80::4041:5412:c8fd:3087%11(Preferred)

IPv4 Address. . . . . . . . . . . : 10.1.1.2(Preferred)

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . : 10.1.1.1

DHCPv6 IAID . . . . . . . . . . . : 235979643

DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-32-50-64-10-C3-7B-4A-27-E5

DNS Servers . . . . . . . . . . . : ::1

127.0.0.1

NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{3BCB48DA-317E-4183-ABCA-E242F1B74318}:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft ISATAP Adapter

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Media State . . . . . . . . . . . : Media disconnected

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0

DHCP Enabled. . . . . . . . . . . : No

Autoconfiguration Enabled . . . . : Yes

C:\Users\Administrator>


Was this post helpful?
thumb_up
thumb_down

I see a problem already. Look at your DNS config. It’s wrong.

How many DNS servers do you have? one, two, or more?


Was this post helpful?
thumb_up
thumb_down

Author Victor Serafim

Only one DNS server


Was this post helpful?
thumb_up
thumb_down

nathan7757 wrote:

Only one DNS server

The config is still wrong. The DNS is pointing to itself, and this is expected. However, if your forwarders are not set up correctly in DNS, then your server is not going to know who www.google.com Opens a new window is because it has no record locally when doing the lookup and no server to send the request on to.

Read this:

http://technet.microsoft.com/en-us/library/cc754941.aspx Opens a new window


Was this post helpful?
thumb_up
thumb_down

Author Joel Wilcox

Joelw23


This person is a Verified Professional

This person is a verified professional.

Verify your account
to enable IT peers to see that you are a professional.

serrano

Pretty sure Bill nailed this one.  try an actual server address rather than the local


Was this post helpful?
thumb_up
thumb_down

Author Joel Wilcox

Joelw23


This person is a Verified Professional

This person is a verified professional.

Verify your account
to enable IT peers to see that you are a professional.

serrano

you can try googles 8.8.8.8 and 8.8.4.4


Was this post helpful?
thumb_up
thumb_down

Author Victor Serafim

thanks guys for the help


Was this post helpful?
thumb_up
thumb_down

Источник

Skip to content

Situation: The client keeps having a DNS problem. Sometimes, users have a problem to access some LAN resources.

Troubleshooting: We find there is Event error relate to DNS.

Log Name: DNS Server
Event ID: 408
Description:
The DNS server could not open socket for address 10.0.0.84.
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 DNS\Parameters\ 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.

In checking DNS, we find one DC uses two IP addresses. One of IP address belongs to another DC. In the IPv4 Property>Advanced>IP Settings, we find there are two IP addresses. We assume they want to enter two DCs’ IP addresses but put them in wrong place. Removing another IP address fixes the problem.

Bob Lin

Bob Lin, Chicagotech-MVP, MCSE & CNE
Data recovery, Windows OS Recovery, Networking, and Computer Troubleshooting on
http://www.ChicagoTech.net
How to Install and Configure Windows, VMware, Virtualization and Cisco on
http://www.HowToNetworking.com
View all posts by Bob Lin

Источник

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/

Источник

Понравилась статья? Поделить с друзьями:
  • Does he studies in switzerland где ошибка
  • Dns сервер ошибка 4013
  • Dors 750 ошибка связи как исправить
  • Does he got a new car где ошибка
  • Dns сервер ошибка 4004