Discussion in 'Microsoft Windows 2000 DNS' started by systems admin, Aug 12, 2003.

  1. I am having probels with replication between two windows
    2000 servers. The replication fails with the error

    failure code - 8524

    failure reason - the dsa operation is unable to proceed
    due to a dns lookup failure.

    Can anyone please advise

    systems admin, Aug 12, 2003
    1. Advertisements

  2. It sounds like the DNS zone may have incorrect info listed and since replication isn't working, AD is unable to replicate the correct info. To fix this, make the
    zone a standard primary on one of the DNS servers. Point all the DCs to this one DNS server only for DNS. Make sure the zone is configured to allow
    dynamic updates. On each DC run "ipconfig /flushdns" and then run "ipconfig /registerdns". Lastly, restart the netlogon service on each DC. Once the
    replication failures have stoped, make the zone AD integrated again. If the DCs are running DNS, they should then point at themselves for primary DNS and
    point at a central DNS server as secondary. This configuration will help avoid this problem in the future.

    Thank you,
    Mike Johnston
    Microsoft Network Support

    This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at

    Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
    Michael Johnston [MSFT], Aug 12, 2003
    1. Advertisements

  3. Hello All,

    Some things to look into.

    Active Directory with DNS on the same server.

    TCP/IP settings

    1.)Right click "My network places" and select properties.
    2.)For the LAN connection right click and select properties.
    3.)On the properties page double click TCP/IP
    4.)At the bottom of the protocols page select Preferred DNS Server option
    and enter the IP address for the server itself.
    5.)Click the advanced button. In the advanced setting make sure the
    "Register this connection's address in DNS" selection is checked at the
    bottom of the display.

    DNS settings

    1.)Open up the DNS console.
    2.)Once opened, right click on the server in the right hand pane and select
    3.)Once the properties page is up, select the "Forwarders" tab.
    4.)Check the "Enable forwarders" selection at the top.
    5.)Add the IP address of the DNS in which to forward requests. If this is
    the only DNS , add the IP address for the ISP's DNS. (note- In the TCP/IP
    settings, we selected the choice for DNS to point to itself. If name
    resolution cannot be resolved then a request is made to the forwarders. If
    resolution cannot be made via the internal DNS and there are no forwarders
    listed, then no resolution will be made at all.)
    6.)Click OK.
    7.)Expand the "Forward Lookup Zones"
    8.)If there is a folder with a dot "." listed then delete it. (note- This
    indicates to the server that it is the root server, which means do not go
    beyond this server for name resolution.)
    9.)Right click the domain folder and select properties. Make sure that
    "Allow dynamic updates is selected."

    Close out the DNS console.

    Open up a command prompt and type the following:

    1.)At the prompt type ipconfig /flushdns and wait for the services to
    2.)ipconfig /registerdns wait for the services to regiser.
    3.)net stop netlogon
    4.)net start netlogon

    If you receive an error during this process go to control panel, admin.
    tools, services. Make sure the DHCP client service is started, even if
    they are not using DHCP they still need the service started. Once all of
    this is done. Open the DNS console again. Expand the forward lookup zones,
    then expand the domain folder. You should see the underscore folders below:


    If you see these, then all is right with the world.

    Shane Brasher
    MCSE (2000,NT),MCSA, A+
    Microsoft Platforms Support
    Windows NT/2000 Networking
    Larry Brasher, Aug 20, 2003
    1. Advertisements

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.
Similar Threads
  1. Ed

    DHCP failure caused by RPC service failure

    Ed, Sep 16, 2003, in forum: Microsoft Windows 2000 DNS
    Ace Fekay [MVP]
    Sep 18, 2003
  2. Bob Doyle
    Dean Wells [MVP]
    Sep 27, 2003
  3. Joe Worley

    DNS Failure for Yahoo Search

    Joe Worley, Oct 26, 2003, in forum: Microsoft Windows 2000 DNS
    Kevin D. Goodknecht
    Oct 26, 2003
  4. Greg

    DNS Recursive Query Failure

    Greg, Jan 20, 2004, in forum: Microsoft Windows 2000 DNS
    Jonathan de Boyne Pollard
    Nov 24, 2004
  5. Guest

    Active Directory Synch, DNS lookup failure

    Guest, Mar 21, 2004, in forum: Microsoft Windows 2000 DNS
    Kevin D. Goodknecht [MVP]
    Mar 21, 2004
  6. Mrfixit

    dns lookup failure

    Mrfixit, Mar 23, 2004, in forum: Microsoft Windows 2000 DNS
    Kevin D. Goodknecht [MVP]
    Mar 24, 2004
  7. Crownu

    DNS service Failure Error 6

    Crownu, Apr 15, 2004, in forum: Microsoft Windows 2000 DNS
    Ace Fekay [MVP]
    Apr 16, 2004
  8. Replies:
    Ace Fekay [MVP]
    Sep 26, 2005