no DNS entry for desktop

I am finding a lot of workstations that have no DNS entry in the dns manager. These workstations appear to be working just fine so I am not sure what is causing this. All systems get the same image via WDS and I can't seem to find the anomaly that is causing it since it seems so random. Only one thing I have found in common is network sharing, under the domain profile network discovery is turned off so I am not sure if this has anything to do with it.
LVL 2
stlhostAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

JohnBusiness Consultant (Owner)Commented:
Network Discovery has nothing to do with DNS so far a I know. I always keep Discovery turned ON for all Windows 7 and 8 machines.

If your Network Card is set for DHCP (normal) then your machine will get DNS from the DNS server and you do not need it set on the workstation.
0
stlhostAuthor Commented:
All workstations get a DHCP IP. They should report back to the DNS server at least so it can write an A record. However when no A record exists this makes it difficult for remote managing, asset tracking, and other various things.
0
JohnBusiness Consultant (Owner)Commented:
Run IPCONFIG /ALL and that will report your DNS server. It will be there, it just does not need to be set in the NIC setup.
0
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

Andy MIT Systems ManagerCommented:
Check the Properties for your IPv4 connection - under advanced there is a dns tab and to the bottom of this there's a checkbox for "Register this connection's address in DNS" - I believe if this is unchecked the computer will not register itself with dns.
0
JohnBusiness Consultant (Owner)Commented:
The setting mentioned is default (and Microsoft has made it default for a while). Please let us know if a number of your machines need the setting. Thanks.
0
stlhostAuthor Commented:
Andy, It's checked
0
JohnBusiness Consultant (Owner)Commented:
So what does IPCONFIG /ALL tell you?
0
stlhostAuthor Commented:
It tells me the IP configuration of the workstation, DNS server. But I'm not sure what I am looking for here?
0
JohnBusiness Consultant (Owner)Commented:
So it is there. DNS Server is just an IP address. Windows (or any other OS) knows to look to the DNS server to interpret google.com. DNS servers mean we do not type in IP addresses to get to web pages.

What are you needing that is not already there?
0
stlhostAuthor Commented:
I need the workstations to register a DNS suffix, in short if I ping the workstation, I get no reply because no A record exists in the DNS manager on the server.
0
JohnBusiness Consultant (Owner)Commented:
I always ping workstation by IP address. Does that work?  It should .
0
stlhostAuthor Commented:
Yes
0
JohnBusiness Consultant (Owner)Commented:
I would say your workstations are working correctly and completely normally. You would apparently have to register the names in your DNS server which is probably not practical or necessary.
0
stlhostAuthor Commented:
If I have to do that manually this does not provide a solution if the IP changes again, and this is a lot of man hours to do this for the workstations that are not reporting back to the DNS server. Thanks anyway but this does not help my situation.
0
JohnBusiness Consultant (Owner)Commented:
So far as I know for workstations they do not report back DNS.
0
Peter HutchisonSenior Network Systems SpecialistCommented:
1 Make sure that the Forward Lookup zone on DNS server is configured for Dynamic updates so machines can automatically register with the DNS sever.
2. Make sure that the machines has the DNS suffix set to the same as the DNS server. See System control panel, Advanced Settings, Computer.
3. On DHCP console, open properties of the Scope and click on the DNS tab and make sure 'Enable DNS Dynamic updates according to the settings below' and select Dynamically update DNS A and PTR records.
0
stlhostAuthor Commented:
1) and 2) are good. I have Dynamic on Nonsecure and Secure though but shouldnt matter. 3) DHCP is handled by sonicwall or an adtran (hardware controlled)
0
JohnBusiness Consultant (Owner)Commented:
Why DHCP on your router?  Try using Server managed DHCP and that may help.
0
Andy MIT Systems ManagerCommented:
3) DHCP is handled by sonicwall or an adtran (hardware controlled)

I suspect there will be a setting on that somewhere that will need amending to allow dns to be updated accordingly. Unfortunately I don't have a lot of experience with those devices but hopefully one of the other experts will know where to look.

Just a thought - does the router device have any reference to the server for it's dns at all? If it's not using the server's dns then I doubt it will even know to try and update it with the dhcp leases.

When you do IPconfig on the workstations does the dns server address match your server or the router's IP? If it's the router's IP that may be the reason why it's not updating the server's dns records.
0
stlhostAuthor Commented:
John, our current situation is not ready for server software controlled DHCP it is on our to do list but far down the road.

Andy, yes the hardware routers you can specifiy the DNS entries. Lets take one machine for example here. The DNS showing in IPCONFIG

 DNS Servers . . . . . . . . . . . : 10.1.1.7
                                     10.1.1.2
                                     10.2.2.5

In the router we see the same entries and in the same order.
0
JohnBusiness Consultant (Owner)Commented:
I just verified at a client that from a Command Prompt on the Server (responsible for DHCP and DSS) that we CAN ping a workstation by name.

A non-domain laptop CANNOT ping a workstation by name.

The workstation DNS addresses are part of the server setup.

So you cannot do what you are trying to do and then either (a) wait until your server does DHCP or (b) ping by IP address (which is what I do anyway).
0
stlhostAuthor Commented:
I dont think we are on the same page.
0
JohnBusiness Consultant (Owner)Commented:
As I noted, your setup will not work and a server DHCP will work. I am not sure what you do not understand about this.
0
stlhostAuthor Commented:
A non-domain laptop CANNOT ping a workstation by name.   I have a laptop right beside me that is not on the domain and I can ping my workstation so I have no idea how this helps my current problem?

If I look in my DNS server and I see no A record for a machine that is on another subnet, I will be unable to talk to that machine by netbios name, ergo ping will fail
0
stlhostAuthor Commented:
My problem is resolved. The DNS Client service was not running on these machines.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
stlhostAuthor Commented:
Figured it out on my own
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 7

From novice to tech pro — start learning today.