DNS NET logon 5781

Posted on 2011-04-22
Last Modified: 2012-05-11
I have a single W2K3 domain server. I had an issue with my modem and had it swapped by a tech and he gave me new dns entries. I made what I thought were the right modifications... now I keep getting the 5781 error and cant figure out why. I called the ISP and they switched me back to my original dns entries. I know that both forward and reverse zone are both running. I have also ran nltest /dsregdns and it returned no flags. I cant figure out what needs to be changed.... any help would be greatly appreciated!
Question by:cwest420
    LVL 59

    Accepted Solution

    If you are running in a domain you should only be pointing to Domain Controllers for DNS in your TCP\IP properties. You should be using DNS Forwarders for your ISP DNS servers

    Author Comment

    First and foremost.. thanks for your quick reply! ok. On my tcp/ip setting on the DC the are set to my ISP's DNS servers. I followed the link but it looks like they use root hints as well. I went ahead and added both DNS entries into the forwarding zone. Same error.
    LVL 59

    Expert Comment

    by:Darius Ghassem
    Again you should NOT have your ISP DNS servers in your DC's TCP\IP settings you should only have DCs listed here for DNS only internal DNS servers this is your problem right here.

    Once you changed the DNS settings on your TCP\IP settings run ipconfig /flushdns, ipconfig /registerdns, and dcdiag /fix on your domain controller

    Second make sure you clients are only pointing to your DC for DNS in  their TCP\IP setting as well

    Author Comment

    AND.... your AWESOME!!! Thanks for your help.

    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

    Join & Write a Comment

    ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
    This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
    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 …

    728 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

    17 Experts available now in Live!

    Get 1:1 Help Now