DNS and DHCP configuration

I have a question regarding DNS and setting it up on a Windows Server
2003 machine. I have a small network where I've implemented a new
Domain Server to replace a workgroup. I ran DCPROMO and installed DNS.
In addition to that the server is an Active Directory server as well
as DHCP.

My problem is this: The server is issuing IP's to the clients'
machines but the clients' machines are unable to resolve any DNS names
(i.e. cannot connect to the internet). The client and server are both
hooked up to a BEFSR41 router that has DHCP disabled. That router is
the primary LAN connection. I also have the WAN (internet) connection
plugged into that router as well. I tried putting my ISP's DNS servers
in the forwarding section of the DNS console but I receive the same
results. When I run NSLOOKUP on the clients machines it reports:

***Default Servers are not available
Default Server: UnKnown
Address: 127.0.0.1

>www.google.com
Server: UnKnown
Address: 127.0.0.1

***UnKnown can't find www.google.com: No response from server

Hope that helps

First off, on the 2003 box, in the DHCP scope properties i would make
sure that when a node in your network requests an IP address it also
receives the address of the in house DNS server, as well as the default
gateway (your router ip).

On the node that can't access the internet, if your in CMD and you do
IPCONFIG /ALL does it show an IP address, DNS address and a default
gateway? If your missing any of those then you wont be able access the
internet.

Do you have forward lookup zones and reverse lookup zones in your DNS?
If you ping server by name from the node, does it resolve the IP
address? Your ISP's DNS server's IP addresses are in the correct spot
for forwarding. If your server doesn't have the default gateway's
(your router) IP address, then it cant forward cause it doesnt know
where to look for the internet.

Hope this helps some.

Basic AD DNS set up is point the AD DNS server to itself in the properties
of TCP/IP for DNS (use the computer's actual IP address not 127..0.01)
Point all AD clients to the DNS server set up for the AD domain ONLY. For
Internet access, configure your AD DNS server to use forwarders and list
your ISP's DNS server(s) as the forwarder. This is the ONLY place on your
domain your ISP's DNS server should be listed, or use root hints.

hth
DDS W 2k MVP MCSE

<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
>I have a question regarding DNS and setting it up on a Windows Server
> 2003 machine. I have a small network where I've implemented a new
> Domain Server to replace a workgroup. I ran DCPROMO and installed DNS.
> In addition to that the server is an Active Directory server as well
> as DHCP.
>
> My problem is this: The server is issuing IP's to the clients'
> machines but the clients' machines are unable to resolve any DNS names
> (i.e. cannot connect to the internet). The client and server are both
> hooked up to a BEFSR41 router that has DHCP disabled. That router is
> the primary LAN connection. I also have the WAN (internet) connection
> plugged into that router as well. I tried putting my ISP's DNS servers
> in the forwarding section of the DNS console but I receive the same
> results. When I run NSLOOKUP on the clients machines it reports:
>
> ***Default Servers are not available
> Default Server: UnKnown
> Address: 127.0.0.1
>
>>www.google.com
> Server: UnKnown
> Address: 127.0.0.1
>
> ***UnKnown can't find www.google.com: No response from server
>
> Hope that helps
>

When I do IPCONFIG /ALL on the node it lists everything correctly:

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : sts02
Primary DNS Suffix . . . . . . . : Domain.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 3:

Connection-specific DNS Suffix . : 192.168.5.110
Description . . . . . . . . . . . : Realtek RTL8139(A) PCI Fast
Ether
Adapter
Physical Address. . . . . . . . . : 00-00-E8-9D-C6-72
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.5.112
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.5.1
DHCP Server . . . . . . . . . . . : 192.168.5.110
DNS Servers . . . . . . . . . . . :
Lease Obtained. . . . . . . . . . : Thursday, March 16, 2006
9:22:12
Lease Expires . . . . . . . . . . : Friday, March 24, 2006
9:22:12 AM

For my forward lookup zone I have: _msdcs.Domain.local and Domain.local
For my reverse lookup zones I have nothing (it says add a lookup zone).
Do I need to configure this?

Yes the node can successfully ping the server.

All the AD clients are set up on the network with DHCP, so they should
be configured correctly, right? They show up on the server's DHCP
client leases. As for the (on the server) TCP/IP properties of the NIC
card for DNS the first line says: DNS Server addreses, in order of
use: 192.168.5.110
That is the address of the server (itself). I have been searching on
the Internet for possible solutions, and what I came across was making
your server into a NAT router using two NIC cards. Essentially, this
is what I need to do but shouldn't the clients be able to resolve
internet addresses through the server with only one NIC? What's the
purpose of installing two, is it better performance?

Here is the website for the NAT:
http://www.windowsnetworking.com/art...AT-router.html

> All the AD clients are set up on the network with DHCP, so they should
> be configured correctly, right?

If you set the options in DHCP correctly. You must enter the information
your DHCP server hands out.

> That is the address of the server (itself). I have been searching on
> the Internet for possible solutions, and what I came across was making
> your server into a NAT router using two NIC cards. Essentially, this
> is what I need to do but shouldn't the clients be able to resolve
> internet addresses through the server with only one NIC? What's the
> purpose of installing two, is it better performance?


Yes you need a second NIC. One NIC that is registered in your servers AD DNS
zone on the same network as your AD domain and a second NIC with a public IP
address given by your ISP. This would be the gateway for the first NIC.

See:
http://support.microsoft.com/kb/816581/en-us


hth
DDS W 2k MVP MCSE

"Sam" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> All the AD clients are set up on the network with DHCP, so they should
> be configured correctly, right? They show up on the server's DHCP
> client leases. As for the (on the server) TCP/IP properties of the NIC
> card for DNS the first line says: DNS Server addreses, in order of
> use: 192.168.5.110
> That is the address of the server (itself). I have been searching on
> the Internet for possible solutions, and what I came across was making
> your server into a NAT router using two NIC cards. Essentially, this
> is what I need to do but shouldn't the clients be able to resolve
> internet addresses through the server with only one NIC? What's the
> purpose of installing two, is it better performance?
>
> Here is the website for the NAT:
> http://www.windowsnetworking.com/art...AT-router.html
>