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

problems getting non-domain PC's to show up in windows DNS

clients have the right dns suffix and are set to "register in DNS" and have the domain server set as their dns server.

The zone on the server is set to allow secure and non-secure updates - but still having issues.  

Does it take time for them to show up?  Do I have to force communication with the server?  (i.e. by pinging the internet and thus forcing the client to talk to the dns server for the address? (my thinking is that might prompt it to go ahead and register at that time))

Also - does the domain server have to be the ONLY DNS on the client?  Or can it just be the primary?

Anyway -- nothing seems to work - any ideas?
0
Xetroximyn
Asked:
Xetroximyn
  • 3
  • 2
1 Solution
 
XetroximynAuthor Commented:
also do I have to check the box for "include this connections dns suffic in dns registration on the client?
0
 
Rob WilliamsCommented:
On the server, in the DHCP console, on the DNS tab of properties of IPv4, , you should also check the boxes:
-Enable DNS dynamic updates according to the settings below
-Always dynamically update DNS A and PTR records
-Discard A and PTR records when lease is deleted
-[ If you have old clients (pre 2003/XP also check ] Dynamically update DNS A and PTR records for client that do not request updates
0
Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

 
XetroximynAuthor Commented:
FYI - most of these clients get DHCP from firewall -- not the domain server.  I seem to have it working.  It seems like I had to force netbios over tcpip to be enabled, and I think I had to check the box on the client for "include this connections dns suffix in dns registration on the client?"
0
 
Rob WilliamsCommented:
Glad to hear you have it working.  Sorry, didn't realize; "clients get DHCP from firewall".
Cheers!
0
 
XetroximynAuthor Commented:
this is what I did to fix
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improved Protection from Phishing Attacks

WatchGuard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. Learn more about our newest service included in Total Security Suite today!

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