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
Solved

Can't Resolve domain.local

Posted on 2010-08-25
8
629 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
  • 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
Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
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

Ransomware: The New Cyber Threat & How to Stop It

This infographic explains ransomware, type of malware that blocks access to your files or your systems and holds them hostage until a ransom is paid. It also examines the different types of ransomware and explains what you can do to thwart this sinister online threat.  

Question has a verified solution.

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

Suggested Solutions

Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
This article outlines the process to identify and resolve account lockout in an Active Directory environment.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …

856 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