DNS not working properly on the WIN 2003

Posted on 2007-10-04
Last Modified: 2010-04-20
Hey Guys I have a wierd problem. DNS is not working properly on my Network. When I try to resolve another servers address, it says server does not exist (using NSLOOKUP). When I run an NSLOOKUP on the servers IP address, it return the name of the server, there by meaning the server exist. I checked the the forward and reverse dns table on the DNS server which is also the DC and both show the correct A record and the PTR record. Now this doesnt happen every time, it happens on sometimes and on random computer on our network

What could this mean???  
Question by:judeadesouza
    LVL 33

    Accepted Solution

    If I understood.  
    1) DNS is hosted on Windows 2003 DC (myserver1)
    2) Checking the DNS table for the mydomain.local zone, you see an A Record for myserver2 with its IP address.  
    3) At random times from a 3rd workstation. NSlookup to myserver2.mydomain.local returns no server found, but all other times it functions correctly.

    If all those are correct, I would start with the DNS server's event viewer and look for any service restarts, dns errors.  It almost sounds like at times the dns service is unavailable.  

    Some other things to check, look for bad lmhosts or hosts file entries that *Might* be messing with resolution.   Are the Workstations on DHCP, make sure your DHCP settings are correct(related to dns server addresses) and that there are no other DHCP servers on the network .  

    LVL 70

    Assisted Solution

    Some basic things to check.

    First check the clients. The clients should have their "Preferred DNS server" set to point to your Windows DNS server (normally the DC). No other DNS should be specified on the clients.

    The Windows DNS server (Normally the DC) should point to itself as "Preferred DNS server", again no thther DNS should be specified.

    In the DNS console, forwarding should be enabled and the address(es) of your ISPs DNS servers entered on the forwarders tab.

    Clear the DNS server cache (on the DNS console) - right click and select clear cache
    and the client cache (ipconfig /flushdns) before re-testing.

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    How to run any project with ease

    Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
    - Combine task lists, docs, spreadsheets, and chat in one
    - View and edit from mobile/offline
    - Cut down on emails

    [b]Ok so now I will show you how to add a user name to the description at login. [/b] First connect to your DC (Domain Controller / Active Directory Server) SET PERMISSIONS FOR SCRIPT TO UPDATE COMPUTER DESCRIPTION TO USERNAME 1. Open Active …
    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…
    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 …

    737 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

    22 Experts available now in Live!

    Get 1:1 Help Now