none
How to Refresh my DNS server on AD?

    Question

  • Hi all,

    I have a DNS server installed on AD Server. How can I refresh it or made sure that records are updated?

    I use lync 2010 with office 365 , I was having some sign-in problems. They asked me to change my DNS on my hosting site which I already did since yesterday.

    I noticed that if change the DNS in my network card to 8.8.8.8 I can sign- in but my current local DNS is not updated, is there a way to refresh it?


    • Edited by Sub-Zero99 Wednesday, February 06, 2013 3:10 PM
    • Moved by Santosh BhandarkarMVP Wednesday, February 06, 2013 5:09 PM Moved from Server General Forum
    Wednesday, February 06, 2013 2:54 PM

Answers

  • Do you have a forwarder set? If not, configure a Forwarder (DNS server properties, Forwarders tab). I suggest to NOT use Google's DNS - 8.8.8.8, because it does not support EDNS0, which in this day and age is extremely beneficial.

    What is EDNS0? (Extension mechanisms for DNS)
    http://msmvps.com/blogs/acefekay/archive/2010/10/11/edns0-extension-mechanisms-for-dns.aspx

    .

    What operating system is your DC? Install the following DNS hotfixes that apply to your DC/DNS server. Try them all., If they don't apply, believe me, it will tell you it doesn't and won't install.

    DNS Server service does not use root hints to resolve external names in Windows Server 2008 R2 - Post Windows 2008 R2 SP1 HOTFIX available.
    Requires a restart.
    http://support.microsoft.com/kb/2616776

    Windows 2008 -
    Requires a restart.
    http://support.microsoft.com/kb/2625735/

    DNS server stops responding to DNS queries from client computers in in Windows Server 2003, in Windows Server 2008 or in Windows Server 2008 R2 - Post Service Pack Hotfix available.
    Does not require a restart.
    http://support.microsoft.com/kb/2655960

    DNS Server service does not resolve some external DNS names after it works for a while in Windows Server 2008 R2
    Hotfix release - (released 4/15/2011)
    http://support.microsoft.com/kb/2508835


    Ace Fekay
    MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/

    This post is provided AS-IS with no warranties or guarantees and confers no rights.

    FaceBook Twitter LinkedIn

    • Marked as answer by Sub-Zero99 Thursday, February 07, 2013 3:03 PM
    Thursday, February 07, 2013 12:24 AM

All replies

  • do a nslookup to you dns server that is in your dns server as forwarding server. Make sure this dns has updated records. When this dns server has the updated records clear the cache of your dns server by right clicking your dns server in dns manager. Just to make sure do a ipconfig /flushdns on you client.
    Wednesday, February 06, 2013 3:05 PM
  • Do you have a forwarder set? If not, configure a Forwarder (DNS server properties, Forwarders tab). I suggest to NOT use Google's DNS - 8.8.8.8, because it does not support EDNS0, which in this day and age is extremely beneficial.

    What is EDNS0? (Extension mechanisms for DNS)
    http://msmvps.com/blogs/acefekay/archive/2010/10/11/edns0-extension-mechanisms-for-dns.aspx

    .

    What operating system is your DC? Install the following DNS hotfixes that apply to your DC/DNS server. Try them all., If they don't apply, believe me, it will tell you it doesn't and won't install.

    DNS Server service does not use root hints to resolve external names in Windows Server 2008 R2 - Post Windows 2008 R2 SP1 HOTFIX available.
    Requires a restart.
    http://support.microsoft.com/kb/2616776

    Windows 2008 -
    Requires a restart.
    http://support.microsoft.com/kb/2625735/

    DNS server stops responding to DNS queries from client computers in in Windows Server 2003, in Windows Server 2008 or in Windows Server 2008 R2 - Post Service Pack Hotfix available.
    Does not require a restart.
    http://support.microsoft.com/kb/2655960

    DNS Server service does not resolve some external DNS names after it works for a while in Windows Server 2008 R2
    Hotfix release - (released 4/15/2011)
    http://support.microsoft.com/kb/2508835


    Ace Fekay
    MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/

    This post is provided AS-IS with no warranties or guarantees and confers no rights.

    FaceBook Twitter LinkedIn

    • Marked as answer by Sub-Zero99 Thursday, February 07, 2013 3:03 PM
    Thursday, February 07, 2013 12:24 AM
  • I have two DNS servers , one as 2003 and other as 2008 R2

    In my 2003 DNS properties , I have the following value as Forwarder :


    • Edited by Sub-Zero99 Thursday, February 07, 2013 11:32 AM
    Thursday, February 07, 2013 11:32 AM
  • Remove 8.8.8.8 from the NIC. 

    Post an ipconfig /all from the two DCs, please. We can help guide you with the correct DNS entries for the DCs.

    Forwarders on both DCs: enter 4.2.2.2 & 4.2.2.3.

    Retry Office365 sign on.


    Ace Fekay
    MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/

    This post is provided AS-IS with no warranties or guarantees and confers no rights.

    FaceBook Twitter LinkedIn

    Thursday, February 07, 2013 12:17 PM
  • Also, please install the hotfixes on Windows 2008 R2.

    Ace Fekay
    MVP, MCT, MCITP/EA, MCTS Windows 2008/R2 & Exchange 2007, Exchange 2010 EA, MCSE & MCSA 2003/2000, MCSA Messaging 2003
    Microsoft Certified Trainer
    Microsoft MVP - Directory Services
    Technical Blogs & Videos: http://www.delawarecountycomputerconsulting.com/

    This post is provided AS-IS with no warranties or guarantees and confers no rights.

    FaceBook Twitter LinkedIn

    Thursday, February 07, 2013 12:18 PM
  • The problem is solved now , my hosting site contacted me and told me that they had mistyped the SRV used for Lync2010 and that they fixed yesterday and it needs at least 72 hours to take effects.But actually it already did because I am able to sign in now will all users without the need of 8.8.8.8 as DNS.

    Thanks a lot guys.

    Thursday, February 07, 2013 2:56 PM