Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

DNS Error 4015

5 views
Skip to first unread message

Chris Dove

unread,
Apr 11, 2005, 5:44:22 AM4/11/05
to
At 3.17pm on Sunday afternoon our DNS seems to have had major problems.

The error message states.

"The DNS server has encountered a critical error from the Active Directory.
Check that the Active Directory is functioning properly. The extended error
debug information (which may be empty) is "%1". The event data contains the
error."

The explanation states
"The DNS Server service uses Active Directory to store DNS data, and it
encountered a Lightweight Directory Access Protocol (LDAP) error while
querying the directory. This error could be caused by either a time-out or a
temporary interruption of service."

Can anyone give me any help on why this may have occured?

TIA


Chris Dove

unread,
Apr 11, 2005, 10:38:20 AM4/11/05
to
Thanks for that.

All i get is

Default Server: corellia.epc-domain.local
Address: 192.168.1.3

Not really used NSlookup, do i need to add a switch.

Thanks again

Chris

"Nirmal" <Nir...@discussions.microsoft.com> wrote in message
news:A95D8018-445F-4810...@microsoft.com...
> Hi,
>
> There is some problem with your LDAP records in DNS Zone. DC SRVs must be
> registered in DNS zone to find domain controllers in the network or by
> Directory Service Agent. DSA is used by all AD Tools to query DNS for DC
> Service Location records. Use Nslookup command to test the DC SRV
> registration.
>
> Let me know.

Nirmal

unread,
Apr 11, 2005, 9:43:01 AM4/11/05
to
Hi,

There is some problem with your LDAP records in DNS Zone. DC SRVs must be
registered in DNS zone to find domain controllers in the network or by
Directory Service Agent. DSA is used by all AD Tools to query DNS for DC
Service Location records. Use Nslookup command to test the DC SRV
registration.

Let me know.

Kevin D. Goodknecht Sr. [MVP]

unread,
Apr 11, 2005, 11:40:10 AM4/11/05
to

Use nslookup epc-domain.local
This should return the LDAP IP addresses, which are the IP addresses for
DCs.
Make sure the DC is using only the internal DNS server for the AD domain, no
ISP DNS servers allowed in any psostion.

--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================


Chris Dove

unread,
Apr 12, 2005, 3:32:08 AM4/12/05
to
This is what it returns

> nslookup epc-domain.local
Server: epc-domain.local
Addresses: 192.168.1.3, 192.168.1.2

although checking the 192.168.1.2 server it looks as though it was also
pointing to an old internal DNS server as its secondary which no longer
exists. The errors seem to have started on this server initially. Could this
have been the problem?

*** epc-domain.local can't find nslookup: Non-existent domain
"Kevin D. Goodknecht Sr. [MVP]" <ad...@nospam.WFTX.US> wrote in message
news:e1u%23$yqPFH...@TK2MSFTNGP15.phx.gbl...

Nirmal

unread,
Apr 12, 2005, 4:38:01 AM4/12/05
to
>>>although checking the 192.168.1.2 server it looks as though it was also
pointing to an old internal DNS server as its secondary which no longer
exists. The errors seem to have started on this server initially. Could this
have been the problem?

Open DNS Management console.
Right Click on Server > Property > Interface tab > check the IP Address
listed.

Nirmal

unread,
Apr 12, 2005, 4:36:03 AM4/12/05
to
For DC SRVs registration.

nslookup

After the previous command completes, at the nslookup (">") prompt type:

set q= rr_type

After the previous command completes, type:

_ldap._tcp.dc._msdcs. Active_Directory_domain_name

Review the output of the previous SRV query and determine if further action
is needed based on whether the previous query succeeded or failed:

Let me know.

Thanks
Nirmal

Chris Dove

unread,
Apr 12, 2005, 5:30:20 AM4/12/05
to
Hi Nirmal,

It says unrecognised command when I type this.. The IP's on the listeners
show the IP of the server. ie
192.168.1.2 shows 192.168.1.2
192.168.1.3 shows 192.168.1.3

Thanks

Chris

"Nirmal" <Nir...@discussions.microsoft.com> wrote in message

news:74422AE0-F166-4717...@microsoft.com...

Chris Dove

unread,
Apr 12, 2005, 5:49:57 AM4/12/05
to
Hi Nirmal,

It says unrecognised command when I type this.. The IP's on the listeners
show the IP of the server. ie
192.168.1.2 shows 192.168.1.2
192.168.1.3 shows 192.168.1.3

Thanks

Chris

"Nirmal" <Nir...@discussions.microsoft.com> wrote in message

news:F01994B4-0F5C-4542...@microsoft.com...

Nirmal

unread,
Apr 12, 2005, 6:10:02 AM4/12/05
to

How many NICs you have in server? and which one is pointing to DNS server
address? Let me know. Reload DNS zone from DNS Console.

Cheers Chris

SystmProg

Chris Dove

unread,
Apr 12, 2005, 6:42:35 AM4/12/05
to
Each Server has only 1 NIC, I reloaded the DNS zone and it did it OK.

Thanks again

Chris

"Nirmal" <Nir...@discussions.microsoft.com> wrote in message

news:18EA7549-DE76-44C6...@microsoft.com...

Nirmal

unread,
Apr 12, 2005, 9:25:02 AM4/12/05
to
From the Interface tab remove the unnecessary IP Addresses and then restart
the DNS Server.

Chris Dove

unread,
Apr 13, 2005, 3:36:22 AM4/13/05
to
Hello again,

Not sure what you mean.

We have 2 DNS servers. Each only has it's own IP listed on the listeners
tab.

Thanks again for the continued help

Chris

"Nirmal" <Nir...@discussions.microsoft.com> wrote in message

news:DB0F6776-8C4B-4122...@microsoft.com...

Nirmal

unread,
Apr 13, 2005, 4:31:03 AM4/13/05
to
Hi Chris,

Please see this article: -
http://support.microsoft.com/kb/267855/EN-US/

Thanks again for your reply.

0 new messages