Windows 2000 DC DNS needs help

I am expereincing lots of connectivity issues in a small Win 2000 domain with Win XP Pro workstations.

The server has been in place for a long time and I do not have access to the individual who set it up, but it appears that the DNS server is the problem. The ISP is Birch and for some crazy reason the DC machine is named viper.birch.net, but the domain is named hance. DHCP is coming from the Birch DSL router, which I do not yet have a password for so that I could turn this off and use the DC server provide DHCP. In the meantime I have given the workstations static IP addresses and given them the DC server's IP for their DNS server.

When I look at the the DNS on the server there is one foward lookup zone, but it doesn't seem to have the records that should be there (services like kerberos, kpassword, ldap, etc. are missing) Accordingly, I don't think there is any way the workstations can access the Active Directory, and this is what is causing the connectivity problems.

I don't know if this is something that can be fixed at all due to the wierd naming of the machine, or if the DNS zone can be reconfigured to work. If it can be fixed does this mean manually adding the missing records, or is there something that will do this for me?

See dcdiag.exe /v below:

Domain Controller Diagnosis

Performing initial setup:
   * Verifying that the local machine viper, is a DC.
   * Connecting to directory service on server viper.
   * Collecting site info.
   * Identifying all servers.
   * Found 1 DC(s). Testing 1 of them.
   Done gathering initial info.

Doing initial required tests
   
   Testing server: Default-First-Site-Name\VIPER
      Starting test: Connectivity
         * Active Directory LDAP Services Check
         VIPER's server GUID DNS name could not be resolved to an
         IP address.  Check the DNS server, DHCP, server name, etc
         Although the Guid DNS name

         (2aad8f3a-7a0f-4c36-83d6-777487074608._msdcs.hance) couldn't be

         resolved, the server name (viper.birch.net) resolved to the IP address

         (192.168.1.3) and was pingable.  Check that the IP address is

         registered correctly with the DNS server.
         ......................... VIPER failed test Connectivity

Doing primary tests
   
   Testing server: Default-First-Site-Name\VIPER
      Skipping all tests, because server VIPER is
      not responding to directory service requests
      Test omitted by user request: Topology
      Test omitted by user request: CutoffServers
      Test omitted by user request: OutboundSecureChannels
   
   Running enterprise tests on : hance
      Starting test: Intersite
         Skipping site Default-First-Site-Name, this site is outside the scope

         provided by the command line arguments provided.
         ......................... hance passed test Intersite
      Starting test: FsmoCheck
         GC Name: \\viper.birch.net
         Locator Flags: 0xe00001fd
         PDC Name: \\viper.birch.net
         Locator Flags: 0xe00001fd
         Time Server Name: \\viper.birch.net
         Locator Flags: 0xe00001fd
         Preferred Time Server Name: \\viper.birch.net
         Locator Flags: 0xe00001fd
         KDC Name: \\viper.birch.net
         Locator Flags: 0xe00001fd
         ......................... hance passed test FsmoCheck