RE: SBS 2003 DNS problems

Tech-Archive recommends: Fix windows errors by optimizing your registry

In the DNS console, you should have two forward lookup zones:
_msdcs.mecstl.local
mecstl.local

If not, add the missing zones. Then right-click the first zone and choose
properties.
Make sure the type is "Active Directory integrate," and that Dynamic updates
is set to "secure only."

Repeat this for the second zone. Reboot the server and see if the zones get
repopulated. If not, post any event log errors.

TM

"JoeG" wrote:

Hi,

We recently completed a fresh install of SBS 2003 on a client's
network. We successfully connected most of the desktops on the local
network, but when we began connecting machines over their WAN link (on
a different subnet), we noticed we were having DNS problems. When
looking at the DNS snap-in, we noticed that none of the computers were
checking in -- even on the local side. There weren't A records for
anything except the server. We went through a lot of troubleshooting -
and eventually ended up deleting the zones (forward & reverse) and
re-creating them to try and fix the problem (bad idea).

It seems the computers are properly checking into WINS, but not DNS.
All of the services were starting properly, without any errors. When
we re-created the DNS zones, we are now getting an error relating to
the _msdcs zone. I followed directions from an MS support tech
(another post found in this newsgroup) to re-create the zone. We are
getting this error right now in event viewer:

-----
Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 4010
Date: 2/17/2006
Time: 12:30:57 AM
User: N/A
Computer: HPSERVER1
Description:
The DNS server was unable to create a resource record for
4eee0d6c-e181-4f87-9080-be12fc92d9cf._msdcs.mecstl.local. in zone
mecstl.local. The Active Directory definition of this resource record
is corrupt or contains an invalid DNS name. The event data contains the
error.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 00 00 00 {...
-------

Is their an any way to rebuild the DNS configuration from scratch
properly? Any ideas on why the cleints weren't checking in? The
client machines were configured properly as far as DNS servers go (and
we were using the "Connect Computer" wizard).

Also, if we have DNS functioning properly, can we disable WINS? WINS
installed by default. There aren't any legacy (98 or older) machines
on the network. All XP.

Thanks,
Joe Gadell


.

Relevant Pages

  • Re: DCDIAG DNS Failure
    ... so the sddcsrv03 is a DC and DNS server right? ... My Forward zones are as follows: ... Without advance view I have 4 forward lookup zones and 7 ...
    (microsoft.public.windows.server.dns)
  • Re: DNS Zone merge
    ... > I understand how to migrate over the DNS zones. ... >> hosting the transferred zones so DNS server on W2k machine would be ... If your child zones are being hosted by the child domain's respective DNS ...
    (microsoft.public.win2000.dns)
  • Re: DNS Recommendations w/ Active Directory & (2) DNS Servers
    ... DNS, and others stating better to use Second Server with Secondary ... while another post specifies that Stub Zones ... and the need for backup 2nd DNS server in the event our Primary Domain ... Unnecessary if you have no Secondaries -- these settings only affect ...
    (microsoft.public.windows.server.dns)
  • Re: DCDIAG DNS Failure
    ... Without advance view I have 4 forward lookup zones and 7 reverse ... My DNS server is not multihomed. ...
    (microsoft.public.windows.server.dns)
  • Re: DCDIAG DNS Failure
    ... so the sddcsrv03 is a DC and DNS server right? ... also describe your actual reverse ... and forward zones. ...
    (microsoft.public.windows.server.dns)