Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

Can't Resolve domain.local

Posted on 2010-08-25
8
Medium Priority
?
642 Views
Last Modified: 2012-05-10
I can't resolve domain.local from clients or the server.  I have a single server/dc environment.  Server 2003 R2.  NetDiag and DCDiag passes without error.  nslookup and ping can't resolve domain.local  Any ideas?
0
Comment
Question by:kcartwri
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
  • 2
  • +2
8 Comments
 
LVL 3

Expert Comment

by:omnimaven
ID: 33526467
In a command window, type in
     ipconfig/all
* Make sure that the value of "DNS Servers" is the IP address of your server.
==========================
In the command window, try:
     nslookup
The first line in the response should be:
     Default Server: <the name of your server>
==========================
On your DNS server, in the property pages, in the "Interfaces" tab, make sure that your DNS server is listening on "All IP addresses".
==========================
Do you have any firewall software running on your server?
0
 
LVL 10

Expert Comment

by:honestman31
ID: 33526470
make sure u have  Active Directory-integrated zone:
more info
http://www.tech-faq.com/dns-and-active-directory-integration.html
0
 
LVL 59

Expert Comment

by:Darius Ghassem
ID: 33526659
Make sure your clients and servers are only pointing to internal DNS servers in their TCP\IP settings. So, you should only be pointing to your DCs for DNS
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
LVL 2

Expert Comment

by:cnemcse1
ID: 33526662
Your DNS server IP address is wrong. You are pointing to your ISP DNS serve. Change the DNS address in your client computers to the same DNS server that your domain controllers are pointing to, which must be one of your servers, more likely the DC.
0
 

Author Comment

by:kcartwri
ID: 33531298
I'm trying to resolve from the DC.  The DC is server01.office.local  I can resolve server01.office.local but I can't resolve office.local.  This is the same for all client PCs as well.  The DNS server for the DC is set to itself so that isn't the issue.  The zone is active directory integrated.
0
 
LVL 3

Expert Comment

by:omnimaven
ID: 33531514
If you can resolve server01.office.local but not office.local then you need to add an A record in your DNS and leave the Host field blank.
0
 
LVL 59

Expert Comment

by:Darius Ghassem
ID: 33531854
Here are 2 things that can affect this problem you do not have an SOA record or record in DNS for your domain which would be odd. Second you do not have a DNS Suffix setup for the DC which would be odd. Or you can not  pointing to the correct DNS servers.

Run dcdiag /fix

Run dcdiag /test:dns
0
 

Accepted Solution

by:
kcartwri earned 0 total points
ID: 33532276
For some reason it just started working again.  Thanks to all for your replies
0

Featured Post

WEBINAR - Latest Cyber Tips for Defense

Join the WatchGuard Threat Research Team on October 26th for an informative webinar featuring expert tips and tricks for defending your organization from today's latest cyber threats. Don't leave yourself vulnerable to attack. Register for the webinar today!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Always backup Domain, SYSVOL etc.using processes according to Microsoft Best Practices. This is meant as a disaster recovery process for small environments that did not implement backup processes and did not run a secondary domain controller that ne…
It’s time for spooky stories and consuming way too much sugar, including the many treats we’ve whipped for you in the world of tech. Check it out!
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…

610 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question