Question : DNS and Active Directory Help With Crashed Server

Alright I took over as system admin for a small company.  Right before I did they ran two servers - Trust and P.  P crashed due to hard drive failure and I did a complete re install of Windows 2000 server.  Before the crash, P ran DNS and acted as a file server.  Trust, which is still up and doing just fine also runs DNS and runs the active directory.  Since I don't have P back up as a DNS server, I'm using an outside server for my secondary DNS.  Primary DNS is set to Trust on all machines.  If I look in the AD on Trust, I can see where P is a domain controller.  I'm getting two primary serious errors in Event Viewer on Trust:

Dynamic registration or deregistration of one or more DNS records failed because no DNS servers are available. - 5781

No Windows NT or Windows 2000 Domain Controller is available for domain PL. The following error occurred:
There are currently no logon servers available to service the logon request.  - 5719

I get these errors constantly all through the day.  Where do I even begin with this problem?  I have tried the Microsoft Knowledge Base, but nothing fixed the problems.  After I re installed 2000 server on P, I have not re setup the DNS or anything.  I'd basically like to put the network back to how it used to be, with P and Trust running the DNS.  However, do I need to re setup P as a domain controller?  If so, got any links for that?  Attached is my NetDiag report for Trust also - I'm failing on DNS and trust relationship.



    Computer Name: TRUST
    DNS Host Name: trust.PL
    System info : Windows 2000 Server (Build 2195)
    Processor : x86 Family 6 Model 8 Stepping 6, GenuineIntel
    List of installed hotfixes :
        KB329115
        KB820888
        KB822343
        KB822831
        KB823182
        KB823559
        KB824105
        KB825119
        KB826232
        KB828035
        KB828741
        KB828749
        KB830352
        KB832353
        KB832359
        KB834707-IE6SP1-20040929.091901
        KB835732
        KB837001
        KB839643
        KB839645
        KB840315
        KB840987
        KB841356
        KB841533
        KB841872
        KB841873
        KB842526
        KB842773
        KB867282-IE6SP1-20050127.163319
        KB870763
        KB871250
        KB873333
        KB873339
        KB885250
        KB885834
        KB885835
        KB885836
        KB888113
        KB889293-IE6SP1-20041111.235619
        KB890046
        KB890047
        KB890175
        KB890859
        KB890923-IE6SP1-20050225.103456
        KB891711
        KB891781
        KB892944
        KB893066
        KB893086
        KB893756
        KB893803
        KB893803v2
        KB894320
        KB896358
        KB896422
        KB896423
        KB896727-IE6SP1-20050719.165959
        KB897715-OE6SP1-20050503.210336
        KB899587
        KB899588
        KB899591
        KB901214
        Q147222
        Q828026
        Update Rollup 1


Netcard queries test . . . . . . . : Passed



Per interface results:

    Adapter : Local Area Connection

        Netcard queries test . . . : Passed

        Host Name. . . . . . . . . : trust
        IP Address . . . . . . . . : xxx.xxx.x.x
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : xxx.xxx.x.x
        Dns Servers. . . . . . . . : xxx.xxx.x.x
                                     xxx.xxx.x.x


        AutoConfiguration results. . . . . . : Passed

        Default gateway test . . . : Passed

        NetBT name test. . . . . . : Passed
            No remote names have been found.

        WINS service test. . . . . : Skipped
            There are no WINS servers configured for this interface.


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
        NetBT_Tcpip_{204D6273-B69C-4957-9129-BD398D602C07}
    1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Passed
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'trust.PLTDOMAIN.'. [RCODE_SERVER_FAILURE]
            The name 'trust.PL.' may not be registered in DNS.
    PASS - All the DNS entries for DC are registered on DNS server 'xxx.xxx.xxx.xxx' and other DCs also have some of the names registered.
    [WARNING] The DNS entries for this DC are not registered correctly on DNS server 'xxx.xxx.xxx.xxx'. Please wait for 30 minutes for DNS server replication.


Redir and Browser test . . . . . . : Passed
    List of NetBt transports currently bound to the Redir
        NetBT_Tcpip_{204D6273-B69C-4957-9129-BD398D602C07}
    The redir is bound to 1 NetBt transport.

    List of NetBt transports currently bound to the browser
        NetBT_Tcpip_{204D6273-B69C-4957-9129-BD398D602C07}
    The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Failed
    [FATAL] Secure channel to domain 'PL' is broken. [ERROR_NO_LOGON_SERVERS]


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
    No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Passed
    IPSec policy service is active, but no policy is assigned.


The command completed successfully


Thanks
Derek

Answer : DNS and Active Directory Help With Crashed Server

trust is the name of the server going by your first comments

ptldomain. (is that it?!?!?!) is your domain name

Create the ForestDNSZones.ptldomain. and DomainDNSZones.ptldomain. forward lookup zones.

Could you check the other zones and make sure that your existing domain controller is listed under pdc, gc and dc.

If not, you need to make the server a global catalog under AD Sites and Services and also sieze the fsmo roles

I think at this point I need to reccomend to try and enlist some dedicated external support.  The state of your AD indicates that a lot of functionality was provided by the DC that failed.  You therefore have a lot of work to do ensuring that all FSMO roles, DNS, the GC and so on are all being performed by your remaining DC.  Once that is all verified and you have a nice clean event log on this remaining serve, you can promote the rebuilt machine and have a nice stable network again.

I think we've provided enough information to indicate the source of your problems.  However, tinkering at this point is not advisable.