Looking for good DNS document.

  • Thread starter Thread starter wdsnews
  • Start date Start date
Hello,

Below is a simple walkthrough.

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.

Shane Brasher
MCSE (2000,NT),MCSA, A+
Microsoft Platforms Support
Windows NT/2000 Networking
 
In
Larry Brasher said:
Hello,

Below is a simple walkthrough.

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.

Shane Brasher
MCSE (2000,NT),MCSA, A+
Microsoft Platforms Support
Windows NT/2000 Networking
Click to expand...

Hi Larry or Shane,

Thanks for the walkthrough, but I believe the original poster asked for them
(you replied to my post).

:-)


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Larry, thank you for the detailed walk through. I suppose I should have
given as much attention to my question as you did to your reply.

What I'm really asking about is DNS service to the public. This server has
always provided DNS during the various versions of SBS and hardware that
I've used. Now, after reinstalling SBS2K, it is no longer able to provide
DNS to the outside world. I've read and adjusted everything I can find, but
surely there is something basic I've missed. So I'm looking for some hand
holding to make this server once again provide DNS to the outside.
 
I found it.

I needed to recheck the server properties in the DNS console. For what-ever
reason, the external requests got turned off. hmmm. I don't know why.
Anyway, I've been so busy checking and rechecking the lower-level settings
in ISA and DNS, I never rechecked the higher-level settings that effect ALL
forward lookup zones.

Thanks for your help.


"Ace Fekay [MVP]"
 
In
wdsnews said:
I found it.

I needed to recheck the server properties in the DNS console. For
what-ever reason, the external requests got turned off. hmmm. I
don't know why. Anyway, I've been so busy checking and rechecking the
lower-level settings in ISA and DNS, I never rechecked the
higher-level settings that effect ALL forward lookup zones.

Thanks for your help.
Click to expand...


Glad you figured it out.
:-)

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top