troubleshooting Question

Setting up DNS on a non-domain controller server.

Avatar of cdharris2005
cdharris2005Flag for United States of America asked on
Windows Server 2003DHCPDNS
9 Comments1 Solution4482 ViewsLast Modified:
This problem is one I inherited, and my client informed me that it's been going on for awhile before I came along.  I have a non-domain controller Windows Server (Standard) that has the terminal services, and dhcp roles assigned.  There are others that I can't recall, but those matter.  Anyway, users on the network can't resolve the server's ip through the hostname.  The IP is accessible, but the name won't resolve.  After looking at the roles on the server, I added DNS...went through the setup, and added an A record to the forward lookup zone.  I even added the DNS server in the DHCP role thinking it would propagate out but it's not.  When I release and renew IP's on the network, those host names don't come up under the DNS record entries when it's refreshed. do I set this up to be taken seriously by client's on the network, and how can I make network clients register on the DNS as well?  

Our community of experts have been thoroughly vetted for their expertise and industry experience.

Join our community to see this answer!
Unlock 1 Answer and 9 Comments.
Start Free Trial
Learn from the best

Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.

Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 1 Answer and 9 Comments.
Try for 7 days

”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.

-Mike Kapnisakis, Warner Bros