Can't Resolve domain.local

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?
kcartwriAsked:
Who is Participating?
 
kcartwriConnect With a Mentor Author Commented:
For some reason it just started working again.  Thanks to all for your replies
0
 
omnimavenCommented:
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
 
honestman31Commented:
make sure u have  Active Directory-integrated zone:
more info
http://www.tech-faq.com/dns-and-active-directory-integration.html
0
The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

 
Darius GhassemCommented:
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
 
cnemcse1Commented:
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
 
kcartwriAuthor Commented:
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
 
omnimavenCommented:
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
 
Darius GhassemCommented:
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
All Courses

From novice to tech pro — start learning today.