Windows server 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

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.

Есть сервер с Windows Server 2008R2 в роли контроллера домена с DNS-сервером.

Сетевая конфигурация выглядит так:

IP-адрес: 172.17.1.3

Маска сети: 255.255.255.0

Шлюз: 172.17.1.1 (роутер)

В логах все время появляются следующие ошибки:

Код ошибки: 407

DNS-серверу не удалось связать сокет для работы по протоколу UDP с 172.17.1.3. В данных события содержится код ошибки. Перезапустите DNS-сервер или перезагрузите компьютер.

Код ошибки: 408

DNS-серверу не удалось открыть сокет для адреса «172.17.1.3».
Убедитесь, что данный адрес является допустимым IP-адресом компьютера сервера. Если он не является допустимым, используйте диалог «Интерфейсы» на вкладке «Свойства сервера» диспетчера DNS для удаления его из списка IP-интерфейсов. После этого остановите и снова запустите DNS-сервер. (Если этот IP-интерфейс единственный на компьютере, DNS-сервер может не запуститься по причине описанной ошибки. В этому случае удалите значение DNSParameters ListenAddress в разделе служб реестра и перезапустите сервер.)

Если указанный IP-адрес является допустимым для данного компьютера, убедитесь, что не запущены другие приложения (например, другой DNS-сервер), которые могут использовать DNS-порт.

Код ошибки: 404

DNS-серверу не удалось связать сокет для работы по протоколу TCP с адресом 172.17.1.3. В данных события содержится код ошибки. IP-адрес 0.0.0.0 может означать допустимый «любой адрес», в котором все настроенные IP-адреса для компьютера доступны для использования.
Перезапустите DNS-сервер или перезагрузите компьютер.

Другие компьютеры, подключенные к домену, и с настройками DNS 172.17.1.3, могут открывать страницы Интернет (хотя, может из-за того, что в качестве шлюза указан 172.17.1.1?)

Собственно вопрос: страшны ли ошибки, и если да, то как лечить?

Или мне не надо указывать в сетевых настройках компьютера-сервера с установленным DNS-сервером в качестве DNS адрес 172.17.1.3, а вписать только петлевой (127.0.01) ?

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:UsersAdministrator>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:UsersAdministrator>


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

dears,

kindly note the below.

i had 2 2012r2 dcs and upgraded them to 2019.

2019 dcs took the ips of 2012r2 and the 2012r2 dcs are demoted.

ipconfig /registerdns was used on the new servers.

DNS a record is showing that the new servers has the old ips which is true.

deleted all records pointing to old dcs from my dns.

the issue is the following: i;m receiving errors on my new dcs: 

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

event 408: he DNS server could not open socket for address ( its own 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.

i searched for some troubleshooting tips:

and i checked i only have on interface in each dc.

NS Manager -> Expand Forward Lookup Zones->right click _msdcs.domain.foo-> properties-> Name Servers-> point to itself.

the above was verified: on each dc the name server point to its ip address.

what could it be dears>

any idea

best regards,

Есть сервер с Windows Server 2008R2 в роли контроллера домена с DNS-сервером.

Сетевая конфигурация выглядит так:

IP-адрес: 172.17.1.3

Маска сети: 255.255.255.0

Шлюз: 172.17.1.1 (роутер)

В логах все время появляются следующие ошибки:

Код ошибки: 407

DNS-серверу не удалось связать сокет для работы по протоколу UDP с 172.17.1.3. В данных события содержится код ошибки. Перезапустите DNS-сервер или перезагрузите компьютер.

Код ошибки: 408

DNS-серверу не удалось открыть сокет для адреса «172.17.1.3».
Убедитесь, что данный адрес является допустимым IP-адресом компьютера сервера. Если он не является допустимым, используйте диалог «Интерфейсы» на вкладке «Свойства сервера» диспетчера DNS для удаления его из списка IP-интерфейсов. После этого остановите и снова запустите DNS-сервер. (Если этот IP-интерфейс единственный на компьютере, DNS-сервер может не запуститься по причине описанной ошибки. В этому случае удалите значение DNSParameters ListenAddress в разделе служб реестра и перезапустите сервер.)

Если указанный IP-адрес является допустимым для данного компьютера, убедитесь, что не запущены другие приложения (например, другой DNS-сервер), которые могут использовать DNS-порт.

Код ошибки: 404

DNS-серверу не удалось связать сокет для работы по протоколу TCP с адресом 172.17.1.3. В данных события содержится код ошибки. IP-адрес 0.0.0.0 может означать допустимый «любой адрес», в котором все настроенные IP-адреса для компьютера доступны для использования.
Перезапустите DNS-сервер или перезагрузите компьютер.

Другие компьютеры, подключенные к домену, и с настройками DNS 172.17.1.3, могут открывать страницы Интернет (хотя, может из-за того, что в качестве шлюза указан 172.17.1.1?)

Собственно вопрос: страшны ли ошибки, и если да, то как лечить?

Или мне не надо указывать в сетевых настройках компьютера-сервера с установленным DNS-сервером в качестве DNS адрес 172.17.1.3, а вписать только петлевой (127.0.01) ?

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.

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:UsersAdministrator>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:UsersAdministrator>


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

  • Remove From My Forums
  • Question

  • The DNS server could not open socket for address 192.168.0.2.
    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.
    Event Xml:
    <Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
      <System>
        <Provider Name=»Microsoft-Windows-DNS-Server-Service» Guid=»{71A551F5-C893-4849-886B-B5EC8502641E}» EventSourceName=»DNS» />
        <EventID Qualifiers=»49152″>408</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime=»2011-09-13T11:16:30.000000000Z» />
        <EventRecordID>264</EventRecordID>
        <Correlation />
        <Execution ProcessID=»0″ ThreadID=»0″ />
        <Channel>DNS Server</Channel>
        <Computer>DCSRV.parkergroup.com</Computer>
        <Security />
      </System>
      <EventData Name=»DNS_EVENT_OPEN_SOCKET_FOR_ADDRESS»>
        <Data Name=»param1″>192.168.0.2</Data>
        <Binary>
        </Binary>
      </EventData>
    </Event>


    Arvind

Answers

  • Hello,

    please proceed like mentioned.

    Use DNS manager and remove the IP address 192.168.0.2 from the list of interfaces that are listening to DNS clients. Once done, restart DNS.


    This
    posting is provided «AS IS» with no warranties or guarantees , and confers no rights.

    Microsoft Student
    Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator:
    Security
    Microsoft Certified Systems Engineer:
    Security
    Microsoft Certified Technology Specialist:
    Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist:
    Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist:
    Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist:
    Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise
    Administrator
    Microsoft Certified IT Professional: Server Administrator

    • Marked as answer by

      Tuesday, September 20, 2011 2:16 AM

  • Hi Arvind,

    Thank you for your post.

    As MrX posted, DNS server use invalid IP address to listen DNS traffic. Please refer to

    Event ID 408 article to resolve your issue.

    If there are more inquiries on this issue, please feel free to let us know.


    Regards,
    Rick Tan

    • Marked as answer by
      Rick Tan
      Tuesday, September 20, 2011 2:16 AM
  • Remove From My Forums
  • Question

  • The DNS server could not open socket for address 192.168.0.2.
    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.
    Event Xml:
    <Event xmlns=»http://schemas.microsoft.com/win/2004/08/events/event»>
      <System>
        <Provider Name=»Microsoft-Windows-DNS-Server-Service» Guid=»{71A551F5-C893-4849-886B-B5EC8502641E}» EventSourceName=»DNS» />
        <EventID Qualifiers=»49152″>408</EventID>
        <Version>0</Version>
        <Level>2</Level>
        <Task>0</Task>
        <Opcode>0</Opcode>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime=»2011-09-13T11:16:30.000000000Z» />
        <EventRecordID>264</EventRecordID>
        <Correlation />
        <Execution ProcessID=»0″ ThreadID=»0″ />
        <Channel>DNS Server</Channel>
        <Computer>DCSRV.parkergroup.com</Computer>
        <Security />
      </System>
      <EventData Name=»DNS_EVENT_OPEN_SOCKET_FOR_ADDRESS»>
        <Data Name=»param1″>192.168.0.2</Data>
        <Binary>
        </Binary>
      </EventData>
    </Event>


    Arvind

Answers

  • Hello,

    please proceed like mentioned.

    Use DNS manager and remove the IP address 192.168.0.2 from the list of interfaces that are listening to DNS clients. Once done, restart DNS.


    This
    posting is provided «AS IS» with no warranties or guarantees , and confers no rights.

    Microsoft Student
    Partner 2010 / 2011
    Microsoft Certified Professional
    Microsoft Certified Systems Administrator:
    Security
    Microsoft Certified Systems Engineer:
    Security
    Microsoft Certified Technology Specialist:
    Windows Server 2008 Active Directory, Configuration
    Microsoft Certified Technology Specialist:
    Windows Server 2008 Network Infrastructure, Configuration
    Microsoft Certified Technology Specialist:
    Windows Server 2008 Applications Infrastructure, Configuration
    Microsoft Certified Technology Specialist:
    Windows 7, Configuring
    Microsoft Certified IT Professional: Enterprise
    Administrator
    Microsoft Certified IT Professional: Server Administrator

    • Marked as answer by

      Tuesday, September 20, 2011 2:16 AM

  • Hi Arvind,

    Thank you for your post.

    As MrX posted, DNS server use invalid IP address to listen DNS traffic. Please refer to

    Event ID 408 article to resolve your issue.

    If there are more inquiries on this issue, please feel free to let us know.


    Regards,
    Rick Tan

    • Marked as answer by
      Rick Tan
      Tuesday, September 20, 2011 2:16 AM

  • Windows server 2016 код ошибки 41
  • Windows server 2012 ошибка загрузки
  • Windows server 2012 dism исправление ошибок системы
  • Windows server 2008 r2 ошибка 1111
  • Windows server 2003 ошибка 333