[Last Call] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1772
  • Last Modified:

Computers not showing up in DNS, but are showing in AD

We just installed a new server 2003. I set up AD and DNS at the same time. We have joined all computers to the domain, but no forward DNS records are showing for the computers. Should I just manually add the records? This is the first time forward DNS has done this to me. Any help would be greatly appreciated.
1 Solution
Is the DHCP server configured to update host and PTR records in DNS? Is the forward lookup zone configured properly?
shiffejrAuthor Commented:
Yes, I believe DNS and forward lookup is configured correctly. However, DHCP is not configured on the server. I have a router that does DHCP. Should I add the DHCP role? Would that cause and issue.
You do not have Active Directory Integration activated.  You must do this in order for the DNS server to be able to interact with AD.  To do this, you must go to the DNS mmc by typing dnsmgmt.msc at the run window.  Expand your DNS server and find you forward zone.  Right click on it and select Properties.  Go to where it says Type and click on the CHANGE button to its right.  Click on Primary and put a checkmark next to where it says STORE THE ZONE IN ACTIVE DIRECTORY.

Do the same for you Reverse-Lookup Zones.  

Also, make sure that the Dynamic Updates are set to secure only (at the CHANGE ZONE TYPE screen.

Good Luck
 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

Also, don't worry about the DHCP server.  If you router is taking care of that, never mind.  However, I like to leave that role to my server because in that way, I can configure it so it assigns the domain name, default gateway, primary and secondary name servers, among other things, to the computers in the lan.  You can always manually configure your default gateways and such, or through a group policy.

Again, good luck
Normally, DNS will configure itself while installing AD unless you have an error that hindered that from happening.

If thats the case and you have no zones in place currently:

Create a forward lookup zone, making it your primary zone.  Then create a reverse lookup zone making that your primary also.

After you do that, if you do NOT have an DHCP servers running on your router or firewall (Sometimes the hardware can be its own DHCP server), on the server itself, install DHCP.  You can do that with Add/Remove Software > Add/Remove Windows Components, or just go to Manage your Server.  

When thats installed, specify a range of your IP addresses and also configure your default gateway (The router).

Go to the workstations when completed and do an ipconfig to see if it's picking up the assigned addresses.  If its not, in the command prompt do an: ipconfig /release and then ipconfig /renew.

If you get any type of error while doing those commands, make sure you have Dynamic IP addresses assigned instead of static.  Open your network connections, click on the LAN properties, go to the TCP/IP Properties, then check "Obtain Automatically"

I hope this helps you somewhat.
Malli BoppeCommented:
If your domain name is single label then you need to make registry changes on each computer for it to register in the DNS


Featured Post

Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now