W2K AS DNS

  • Thread starter Thread starter Steve
  • Start date Start date
S

Steve

Question,

I have an Advance Server set up for a medium office. 1 server 14 w/s.
I am using my Linksys router as DHCP I also am using the ISP's DNS
servers for resolution. I am getting a lot of DNS 5774 and 5775 errrs
reported every second hour for 15 mins etc. Although they don't seem
to be effecting anything I would like to resolve this problem. I
understand I need DNS on the server for active directory? is this true
and if so what would be the best way to set this so things will be
resolved? one article stated to set it a a simple DNS but I would
have thought that was the way it was by default?
 
In
Steve said:
Question,

I have an Advance Server set up for a medium office. 1 server 14 w/s.
I am using my Linksys router as DHCP I also am using the ISP's DNS
servers for resolution.
Click to expand...
You should actually use DHCP in Win2k, it supports Active Directory
functions
I am getting a lot of DNS 5774 and 5775 errrs
reported every second hour for 15 mins etc. Although they don't seem
to be effecting anything I would like to resolve this problem.
Click to expand...

Oh really? So when you logon it does not take ten minutes? You cannot use
your ISP's DNS in an AD enviorment, unless they are actually hosting your AD
domain zone. DNS is how Members find the DC, except for Win9x which cannot
be domain members, uses the NetBIOS name and NTLM.
I understand I need DNS on the server for active directory?
Click to expand...

DNS is required for AD, not an option.
is this true and if so what would be the best way to set this so things will be
resolved?
Click to expand...

Simple, point all DCs and members only to your local DNS address (usually
your DC) then use the DNS snap in to connect to your DNS server, open
Forward Lookup Zones, you should see a zone with the name of your AD Domain,
in the zone properties the "Allow dynamic updates" should say "Yes"

All machines must point to this server's address for internet access you
need to configure your DNS as per the below article making sure you have
deleted the "." forward lookup zone if there is one in place.
300202 - HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/?id=300202&FR=1
 
DNS should be installed on your AD DC. A zone needs to exist in this DNS server that matches that of the AD domain name.
This zone should also be configured to allow dynamic updates. The server and all clients should ONLY point at this DNS
server for DNS. In the properties of the DNS server you have the option of using forwarders to your ISP but this isn't a
requirement as root hints will also give you Internet name resolution.

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
http://www.microsoft.com/info/cpyright.htm

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.
 
Thanks for all the advise, here is the resolution I used and it has
resolved my issues.

Thanks again.


General setup for 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
properties.
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
flush.
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:

_msdcs
_sites
_tcp
_udp

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


Hope this helps.


Shane Brasher
MCSE (2000,NT),MCSA, A+
Microsoft Platforms Support
Windows NT/2000 Networking
 
Back
Top