Ошибка dns сервера 0x0000232a rcode server failure

  • Remove From My Forums

  • Вопрос

  • Вероятно, доменное имя «****» является NetBIOS-именем домена. Проверьте, что имя домена правильно зарегистрировано в WINS.

    Если это имя не является NetBIOS-именем домена, следующие сведения помогут исправить ошибку в конфигурации DNS.

    При запросе DNS записи ресурса размещения службы (SRV), используемой для выяснения размещения контроллера домена Active Directory для домена «****» произошла ошибка:

    Произошла ошибка: «Ошибка DNS-сервера.»
    (код ошибки: 0x0000232A RCODE_SERVER_FAILURE)

    Опрос проводился для SRV-записи для _ldap._tcp.dc._msdcs.****

    К возможным причинам ошибки относятся:

    — DNS-серверы, используемые этим компьютером содержат неправильные корневые ссылки. Этот компьютер настроен на использование DNS-серверов со следующими IP-адресами:

    192.168.***.***
    192.168.***.***

    — В одной или в нескольких зонах из указанных ниже содержится неверное делегирование:

    ****
    . (корневая зона)

    что с этим делать?

    • Изменено

      22 ноября 2016 г. 7:12

Ответы

  • Как и говорится в проблеме — ошибка связана с DNS. Начните с проверок:

    1. Контроллеры домена являются севрером DNS

    2. На контроллерах домена первым прописан DNS 127.0.0.1

    3. Выполните ipconfig /registerdns на контроллерах домена и выполните рестарт netlogon

    4. Проверьте, что вторым DNS прописан другой контроллер домена

    5. Проверьте, что это адреса контроллеров домена:

    192.168.***.***
    192.168.***.***

    6. Проверьте наличие в DNS записи «_ldap._tcp.dc._msdcs.****«

    7. Если не помогло, выполните dcdiag

    • Помечено в качестве ответа
      Petko KrushevMicrosoft contingent staff, Moderator
      29 ноября 2016 г. 7:46

Источник
  • Remove From My Forums

  • Вопрос

  • Вероятно, доменное имя «****» является NetBIOS-именем домена. Проверьте, что имя домена правильно зарегистрировано в WINS.

    Если это имя не является NetBIOS-именем домена, следующие сведения помогут исправить ошибку в конфигурации DNS.

    При запросе DNS записи ресурса размещения службы (SRV), используемой для выяснения размещения контроллера домена Active Directory для домена «****» произошла ошибка:

    Произошла ошибка: «Ошибка DNS-сервера.»
    (код ошибки: 0x0000232A RCODE_SERVER_FAILURE)

    Опрос проводился для SRV-записи для _ldap._tcp.dc._msdcs.****

    К возможным причинам ошибки относятся:

    — DNS-серверы, используемые этим компьютером содержат неправильные корневые ссылки. Этот компьютер настроен на использование DNS-серверов со следующими IP-адресами:

    192.168.***.***
    192.168.***.***

    — В одной или в нескольких зонах из указанных ниже содержится неверное делегирование:

    ****
    . (корневая зона)

    что с этим делать?

    • Изменено

      22 ноября 2016 г. 7:12

Ответы

  • Как и говорится в проблеме — ошибка связана с DNS. Начните с проверок:

    1. Контроллеры домена являются севрером DNS

    2. На контроллерах домена первым прописан DNS 127.0.0.1

    3. Выполните ipconfig /registerdns на контроллерах домена и выполните рестарт netlogon

    4. Проверьте, что вторым DNS прописан другой контроллер домена

    5. Проверьте, что это адреса контроллеров домена:

    192.168.***.***
    192.168.***.***

    6. Проверьте наличие в DNS записи «_ldap._tcp.dc._msdcs.****«

    7. Если не помогло, выполните dcdiag

    • Помечено в качестве ответа
      Petko KrushevMicrosoft contingent staff, Moderator
      29 ноября 2016 г. 7:46
  • Remove From My Forums

  • Question

  • Hi,

    I am testing my virtual machine which runs on windows server 2008 Datacenter edition. I am trying to add my host computer to the virtual machine which is a domain controller. But i get an error which reads something like:

    An active directory domain controller (AD DC)for the domain «Sharkie.com» could not be contacted. here are the details:

    The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain «Sharkie.com»:

    The error was: «DNS server failure.»
    (error code 0x0000232A RCODE_SERVER_FAILURE)

    The query was for the SRV record for _ldap._tcp.dc._msdcs.Sharkie.com

    Common causes of this error include the following:

    — The DNS servers used by this computer contain incorrect root hints. This computer is configured to use DNS servers with the following IP addresses:

    192.168.1.1

    — One or more of the following zones contains incorrect delegation:

    Sharkie.com
    com
    . (the root zone)

    Where have i gone wrong & if you could clarify me that there is an option to add my host client computer as a Domain member to the Server which runs on VM.

    Your help would be appreciated.

    Regards,

    Vignesh

    Vignesh

Answers

  • Hello,

    An active directory domain controller (AD DC)for the domain «Sharkie.com» could not be contacted. here are the details:

    The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain «Sharkie.com»:

    The error was: «DNS server failure.»
    (error code 0x0000232A RCODE_SERVER_FAILURE)

    you have DNS problems.

    Please make sure that:

    • the DC is not multihomed and that RRAS is not enabled on it
    • the DC is a DNS server
    • The DC points to its private IP address and 127.0.0.1 as secondary one
    • Each public DNS server is set as a forwarder and not added in IP settings of the DC

    Once done, run ipconfig /registerdns and restart netlogon on the DC you have.

    For servers / client computers, make sure that they are pointing to your internal DNS servers as primary and secondary DNS servers.

    Also, make sure that needed ports for authentication are not blocked: http://msmvps.com/blogs/rexiology/archive/2006/04/05/89389.aspx

    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

      Thursday, September 15, 2011 9:07 AM

  • Remove From My Forums

  • Question

  • Hi,

    I am testing my virtual machine which runs on windows server 2008 Datacenter edition. I am trying to add my host computer to the virtual machine which is a domain controller. But i get an error which reads something like:

    An active directory domain controller (AD DC)for the domain «Sharkie.com» could not be contacted. here are the details:

    The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain «Sharkie.com»:

    The error was: «DNS server failure.»
    (error code 0x0000232A RCODE_SERVER_FAILURE)

    The query was for the SRV record for _ldap._tcp.dc._msdcs.Sharkie.com

    Common causes of this error include the following:

    — The DNS servers used by this computer contain incorrect root hints. This computer is configured to use DNS servers with the following IP addresses:

    192.168.1.1

    — One or more of the following zones contains incorrect delegation:

    Sharkie.com
    com
    . (the root zone)

    Where have i gone wrong & if you could clarify me that there is an option to add my host client computer as a Domain member to the Server which runs on VM.

    Your help would be appreciated.

    Regards,

    Vignesh

    Vignesh

Answers

  • Hello,

    An active directory domain controller (AD DC)for the domain «Sharkie.com» could not be contacted. here are the details:

    The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain «Sharkie.com»:

    The error was: «DNS server failure.»
    (error code 0x0000232A RCODE_SERVER_FAILURE)

    you have DNS problems.

    Please make sure that:

    • the DC is not multihomed and that RRAS is not enabled on it
    • the DC is a DNS server
    • The DC points to its private IP address and 127.0.0.1 as secondary one
    • Each public DNS server is set as a forwarder and not added in IP settings of the DC

    Once done, run ipconfig /registerdns and restart netlogon on the DC you have.

    For servers / client computers, make sure that they are pointing to your internal DNS servers as primary and secondary DNS servers.

    Also, make sure that needed ports for authentication are not blocked: http://msmvps.com/blogs/rexiology/archive/2006/04/05/89389.aspx

    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

      Thursday, September 15, 2011 9:07 AM

I have a DC running on Windows Server 2012. As of yesterday,
I have been unable to join any Windows 10 workstations to the domain. I keep
seeing a DNS server failure error. I’m able to pickup a DHCP address from the
DC and my DNS is correct. I can ping the server just fine and ping the workstation
from the server. I have tested disabling AV on both the server and workstation but
no dice. Below is the error I’m seeing from the workstation side. 

The following error occurred when DNS was queried for the
service location (SRV) resource record used to locate an Active Directory
Domain Controller (AD DC) for domain «osbc.local»:

The error was: «DNS server failure.»

(error code 0x0000232A RCODE_SERVER_FAILURE)

The query was for the SRV record for
_ldap._tcp.dc._msdcs.osbc.local

Common causes of this error include the following:

— The DNS servers used by this computer contain incorrect
root hints. This computer is configured to use DNS servers with the following
IP addresses:

XXX.XXX.XXX.XXX

— One or more of the following zones contains incorrect
delegation:

osbc.local

local

. (the root zone)

23-Jan-2012 15:27:55.357 client 10.0.0.10#59250: query ‘local.ord.local/SOA/IN’ approved

23-Jan-2012 15:27:55.660 client 10.0.0.10#53101: query (cache) ‘./SOA/IN’ approved

23-Jan-2012 15:27:55.661 client 10.0.0.10#54128: query (cache) ‘./NS/IN’ approved

23-Jan-2012 15:27:55.662 client @0xb500c008: udprecv

и стартовый лог бинда

Jan 23 15:48:54 gate named[10497]: shutting down

Jan 23 15:48:54 gate named[10497]: no longer listening on 127.0.0.1#53

Jan 23 15:48:54 gate named[10497]: no longer listening on 10.0.0.1#53

Jan 23 15:48:54 gate named[10497]: exiting

Jan 23 15:48:54 gate start-stop-daemon: pam_unix(start-stop-daemon:session): session opened for user nobody by (uid=0)

Jan 23 15:48:54 gate named[10543]: starting BIND 9.7.4-P1 -u named -4 -d 1

Jan 23 15:48:54 gate named[10543]: built with ‘—prefix=/usr’ ‘—build=i686-pc-linux-gnu’ ‘—host=i686-pc-linux-gnu’ ‘—mandir=/usr/share/man’ ‘—infodir=/usr/share/info’ ‘—datadir=/usr/share’ ‘—sysconfdir=/etc’ ‘—localstatedir=/var/lib’ ‘—sysconfdir=/etc/bind’ ‘—localstatedir=/var’ ‘—with-libtool’ ‘—with-openssl’ ‘—without-idn’ ‘—enable-ipv6’ ‘—with-libxml2’ ‘—without-gssapi’ ‘—enable-linux-caps’ ‘—enable-threads’ ‘—with-randomdev=/dev/random’ ‘build_alias=i686-pc-linux-gnu’ ‘host_alias=i686-pc-linux-gnu’ ‘CFLAGS=-O2 -march=native -mtune=native -pipe’ ‘LDFLAGS=-Wl,-O1 -Wl,—as-needed’

Jan 23 15:48:54 gate named[10543]: adjusted limit on open files from 1024 to 1048576

Jan 23 15:48:54 gate named[10543]: found 2 CPUs, using 2 worker threads

Jan 23 15:48:54 gate named[10543]: using up to 4096 sockets

Jan 23 15:48:54 gate named[10543]: Using 101 tasks for zone loading

Jan 23 15:48:54 gate named[10543]: loading configuration from ‘/etc/bind/named.conf’

Jan 23 15:48:54 gate named[10543]: reading built-in trusted keys from file ‘/etc/bind/bind.keys’

Jan 23 15:48:54 gate named[10543]: using default UDP/IPv4 port range: [1024, 65535]

Jan 23 15:48:54 gate named[10543]: using default UDP/IPv6 port range: [1024, 65535]

Jan 23 15:48:54 gate named[10543]: no IPv6 interfaces found

Jan 23 15:48:54 gate named[10543]: listening on IPv4 interface lo, 127.0.0.1#53

Jan 23 15:48:54 gate named[10543]: binding TCP socket: address in use

Jan 23 15:48:54 gate named[10543]: listening on IPv4 interface eth0, 10.0.0.1#53

Jan 23 15:48:54 gate named[10543]: binding TCP socket: address in use

Jan 23 15:48:54 gate named[10543]: generating session key for dynamic DNS

Jan 23 15:48:54 gate named[10543]: zone ‘_msdcs.ord.local’ allows updates by IP address, which is insecure

Jan 23 15:48:54 gate named[10543]: zone ‘_tcp.ord.local’ allows updates by IP address, which is insecure

Jan 23 15:48:54 gate named[10543]: zone ‘_udp.ord.local’ allows updates by IP address, which is insecure

Jan 23 15:48:54 gate named[10543]: zone ‘_sites.ord.local’ allows updates by IP address, which is insecure

Jan 23 15:48:54 gate named[10543]: zone ‘DomainDNSZones.ord.local’ allows updates by IP address, which is insecure

Jan 23 15:48:54 gate named[10543]: zone ‘ForestDNSZones.ord.local’ allows updates by IP address, which is insecure

Jan 23 15:48:54 gate named[10543]: set up managed keys zone for view _default, file ‘/etc/bind/managed-keys.bind’

Jan 23 15:48:54 gate named[10543]: automatic empty zone: 0.IN-ADDR.ARPA

Jan 23 15:48:54 gate named[10543]: automatic empty zone: 254.169.IN-ADDR.ARPA

Jan 23 15:48:54 gate named[10543]: automatic empty zone: 2.0.192.IN-ADDR.ARPA

Jan 23 15:48:54 gate named[10543]: automatic empty zone: 100.51.198.IN-ADDR.ARPA

Jan 23 15:48:54 gate named[10543]: automatic empty zone: 113.0.203.IN-ADDR.ARPA

Jan 23 15:48:54 gate named[10543]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA

Jan 23 15:48:54 gate named[10543]: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA

Jan 23 15:48:54 gate named[10543]: automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA

Jan 23 15:48:54 gate named[10543]: automatic empty zone: D.F.IP6.ARPA

Jan 23 15:48:54 gate named[10543]: automatic empty zone: 8.E.F.IP6.ARPA

Jan 23 15:48:54 gate named[10543]: automatic empty zone: 9.E.F.IP6.ARPA

Jan 23 15:48:54 gate named[10543]: automatic empty zone: A.E.F.IP6.ARPA

Jan 23 15:48:54 gate named[10543]: automatic empty zone: B.E.F.IP6.ARPA

Jan 23 15:48:54 gate named[10543]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA

Jan 23 15:48:54 gate named[10543]: /etc/bind/named.conf:120: couldn’t add command channel 127.0.0.1#953: address in use

Jan 23 15:48:54 gate named[10543]: /etc/bind/named.conf:121: couldn’t add command channel 10.0.0.1#953: address in use

Jan 23 15:48:54 gate named[10543]: zone 0.10.in-addr.arpa/IN: loaded serial 122214468

Jan 23 15:48:54 gate named[10543]: zone 127.in-addr.arpa/IN: loaded serial 2008122601

Jan 23 15:48:54 gate named[10543]: zone ord.local/IN: loaded serial 122214468

Jan 23 15:48:54 gate named[10543]: zone _msdcs.ord.local/IN: loaded serial 20071033

Jan 23 15:48:54 gate named[10543]: zone _sites.ord.local/IN: loaded serial 20071033

Jan 23 15:48:54 gate named[10543]: zone _tcp.ord.local/IN: loaded serial 20071033

Jan 23 15:48:54 gate named[10543]: zone _udp.ord.local/IN: loaded serial 20071033

Jan 23 15:48:54 gate named[10543]: zone DomainDNSZones.ord.local/IN: loaded serial 20071033

Jan 23 15:48:54 gate named[10543]: zone ForestDNSZones.ord.local/IN: loaded serial 20071033

Jan 23 15:48:54 gate named[10543]: zone localhost/IN: loaded serial 2008122601

Jan 23 15:48:54 gate named[10543]: managed-keys-zone ./IN: loaded serial 0

Jan 23 15:48:54 gate named[10543]: zone 0.10.in-addr.arpa/IN: sending notifies (serial 122214468)

Jan 23 15:48:54 gate named[10543]: zone ord.local/IN: sending notifies (serial 122214468)

Jan 23 15:48:54 gate named[10543]: running

Источник

Hi,
I got a problem after replacing my network switch after the old one stopped working.

The new switch is a managed switch (HP ProCurve), I have set the switch on DHCP so it would receive ip, dns etc. automatically from my win2003 server.

I thought everything was good to go. But when I tried to reach my documents on the server from mypc (client) it wouldn’t show. I tried to ping the server 192.168.0.1 and bizon.mydomain.no, it responded to the ping.

So I tested the dns with nslookup and Set Type=SRV and _ldap._tcp.dc._msdcs.mydomain.no
The server responded with:

Server:  bizon.mydomain.no
Address:  192.168.0.1
DNS request timed out.
Timeout was two seconds.

So I tried to unjoin the workstation (my pc) from the server and rejoin it again to the domain mydomain.no

It wouldn’t rejoin with the domain, it is switching between two errors when I’m trying to rejoin the domain, these are:


The error was: This operation returned because the timeout period expired.
(error code 0x000005B4 ERROR_TIMEOUT)

The query was for the SRV record for _ldap._tcp.dc._msdcs.mydomain.no

DNS servers used by this computer for name resolution, not responding. This computer is configured to use DNS servers with following IP addresses:

192.168.0.1

Make sure your computer is connected to the network, that these are the correct IP addresses for the DNS server, and that at least one of the DNS servers are running.

And

The error was: Error in the DNS server.
(error code 0x0000232A RCODE_SERVER_FAILURE)

The query was for the SRV record for _ldap._tcp.dc._msdcs.mydomain.no

Common causes of this error include:

— DNS servers used by your computer has errors rottips. This computer is configured to use DNS servers with following IP addresses:

192.168.0.1

— One or more of the following zones contains incorrect delegation:

mydomain.no
no
. (root zone)

Is it my switch that is making all this trouble?

The server is not used external, ex.webpages and exchange etc.. But Lotus Domino server are running on this server and can be reached external.

This server is the only one with dns setup.

Here is my settings on the NIC through ipconfig:

Ethernet-kort Lokal tilkobling:

   Tilkoblingsspesifikt DNS-suffiks  : mydomain.no
   Beskrivelse   . . . . . . . . . . : Realtek RTL8168C(P)/8111C(P) Family PCI-E
 GBE NIC
   Fysisk adresse  . . . . . . . . . : 00-1E-33-1F-CC-D3
   DHCP aktivert . . . . . . . . . . : Yes
   Automatisk konfigurasjon aktivert : Yes
   Koblingslokal IPv6-adresse. . . . : fe80::a539:44c7:4d1b:58b9%11(Foretrukket)

   IPv4-adresse. . . . . . . . . . . : 192.168.0.111(Foretrukket)
   Nettverksmaske . . . . . . . . . .: 255.255.255.0
   Leieavtale inngått. . . . . . . . : 3. januar 2012 07:56:48
   Leieavtale utløper. . . . . . . . : 11. januar 2012 08:05:09
   Standard gateway . . . . . . . . .: 192.168.0.254
   DHCP-server . . . . . . . . . . . : 192.168.0.1
   DHCPv6-IAID . . . . . . . . . . . : 251665971
   DHCPv6 klient-DUID. . . . . . . . : 00-01-00-01-12-24-6B-2F-00-1E-33-1F-CC-D3

   DNS-servere . . . . . . . . . . . : 192.168.0.1
   NetBIOS over Tcpip. . . . . . . . : Aktivert

Источник

I have a DC running on Windows Server 2012. As of yesterday,
I have been unable to join any Windows 10 workstations to the domain. I keep
seeing a DNS server failure error. I’m able to pickup a DHCP address from the
DC and my DNS is correct. I can ping the server just fine and ping the workstation
from the server. I have tested disabling AV on both the server and workstation but
no dice. Below is the error I’m seeing from the workstation side. 

The following error occurred when DNS was queried for the
service location (SRV) resource record used to locate an Active Directory
Domain Controller (AD DC) for domain «osbc.local»:

The error was: «DNS server failure.»

(error code 0x0000232A RCODE_SERVER_FAILURE)

The query was for the SRV record for
_ldap._tcp.dc._msdcs.osbc.local

Common causes of this error include the following:

— The DNS servers used by this computer contain incorrect
root hints. This computer is configured to use DNS servers with the following
IP addresses:

XXX.XXX.XXX.XXX

— One or more of the following zones contains incorrect
delegation:

osbc.local

local

. (the root zone)

Источник

Понравилась статья? Поделить с друзьями:
  • Ошибка dns сервиса
  • Ошибка dns сервер не отвечает как исправить
  • Ошибка dns сервера что делать
  • Ошибка dns сервер недоступен ростелеком
  • Ошибка dns сервера при подключении через роутер