Solved

Can't Resolve domain.local

Posted on 2010-08-25
8
626 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
 
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
What Security Threats Are You Missing?

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

 

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

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Join & Write a Comment

Suggested Solutions

Title # Comments Views Activity
Lockdown of laptops 10 38
Problem with configuring nic with powershell 5 19
Question on security Audit 2 49
DNS Woes 7 0
Mapping Drives using Group policy preferences Are you still using old scripts to map your network drives if so this article will show you how to get away for old scripts and move toward Group Policy Preference for mapping them. First things f…
BIND is the most widely used Name Server. A Name Server is the one that translates a site name to it's IP address. There is a new bug in BIND (https://kb.isc.org/article/AA-01272), affecting all versions of BIND 9 from BIND 9.1.0 (inclusive) thro…
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…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

705 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

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now