Milan Mihajlov

IT Engineer by vocation and currently works as System Administrator in an international school. By contributing to this blog, his aim is to provide valuable information to all interested visitors how to better utilize technology. Follow him on Google+

18 Comments

  1. Autumn Haynes
    January 21, 2015 @ 4:46 pm

    Hi Milan Mihajlov,
    Nice Post
    thanks For guide about DNs settings it is very helpful .

    Reply

  2. Jon Giles
    July 29, 2015 @ 11:37 pm

    This post has been a life save!!! i have been scratching my head for days knowing I have a niggling DNS problem somewhere after adding my first 2012 R2 DC to a 2003 domain with a single DC…. should have known it would be something so stupidly simple (setting the preffered DNS server address on the old DC to the new DC and loopback address for the second one!!)

    Thanks for a great post!!!

    Reply

    • Milan Mihajlov
      August 3, 2015 @ 11:11 pm

      Thanks Jon! If you have any other issue that could convert into a good article, let me know.

      Reply

  3. Mike
    September 30, 2015 @ 11:27 pm

    Great article Milan!
    I ran into a strange forwarder configuration the other day – need your oppinion:
    2 DCs working as DNS:
    DC1 has external forwarders like Googles 8.8.8.8
    DC2 has DC1 as forwarder!
    I do not see any sense in that – completely faulty configuration!

    Reply

    • Milan Mihajlov
      October 8, 2015 @ 9:26 pm

      Hi Mike. Did you try to configure DNS settings as it was explained in the article or you kept the mentioned configuration with DC1 configured as forwarder for DC2? Another thing, did you review the Event Viewer logs, especially the DNS logs? What do they say?

      Reply

  4. Tan
    October 16, 2015 @ 12:10 am

    Hi Milan,
    Great post! Thanks.
    I am running 2 DCs, and wondering on setting up forwarders for my domain controllers. I am using opendns ip address as external forwarders, and setup all the workstations for automatically get DNS server address. It works fine, except the workstations can’t access the network files. When I changed the DNS server address on the workstation to point to the 2 domain controllers ip addresses, it works great. My question is, what setting should I use for forwarders on my domain controller, so I can keep the setting on the workstations to get DNS address automatically?
    Thanks!

    Reply

    • Milan Mihajlov
      November 3, 2015 @ 8:53 pm

      Hello Tan. I apologize for replying a bit later. In my opinion, if I understood your question well, you should configure your internal DHCP server to assign the IP addresses of your DC’s as DNS setting on all workstations, and on the other side configure external forwarders on your DNS servers (the 2 DC’s) with IP addresses of OpenDNS. Because, in your case the workstations couldn’t resolve internal network resources because they were pointing outside of your network (OpenDNS).

      Reply

  5. Tobi
    January 21, 2016 @ 11:04 am

    You shouldn’t use the loopback address 127.0.0.1 on your DC’s network settings. This is the old way. Since Windows 2012 you should use the private IP of the DC here. I know there is a lot of discussion about this point but round about 80% of all administrators agree with this opinion.

    Reply

  6. Colin
    April 11, 2016 @ 4:58 pm

    Bit late on the reply, but in my defence I’ve only just had reason to scour through all the docs available on DNS and the loopback argument.

    The link Tobi provided only mentions this shouldn’t be done, but didn’t provide any reasons for not doing so: “modern Windows networks do not like to see this” doesn’t explain anything other than the authors opinion on the subject. Does anyone have anything else on the should v shouldn’t of loopback in DNS settings?

    Reply

  7. Stefan Nonchev
    June 20, 2016 @ 12:31 pm

    Officially from the vendor:
    https://technet.microsoft.com/en-us/library/ff807362(WS.10).aspx

    For me using loopback as a second DNS has been the way to go for the last 15 years. It is faster also…

    Reply

  8. sajid
    July 28, 2016 @ 12:15 pm

    Please confirm in order to perform external resolution using conditional forwarding method to google dns, 8.8.8.8. Does internet connectivity require to have in the DC system? Currently my domain is not having internet connectivity and are in secure sub net.

    If I want to achieve, this, how I can do this? My all the request is being resolved internally. But our requirement is to resolve externally to one particular domain as it has a VPN tunnel dependency.

    Reply

    • Milan Mihajlov
      September 24, 2016 @ 8:35 pm

      Hi, I apologize for replying later than usual. I assume you don’t want to connect your DC to internet but it would be hard to achieve DNS resolution without Internet link. Except if you consider to deploy something like “DNS relay”. In that case you may continue to use your DC without internet but it should be connected to the DNS relay. You will need an experienced network engineer to configure this solution, depending on your network settings.

      Reply

  9. Ramazan
    October 26, 2016 @ 8:01 am

    Hi, Dear
    Help me
    I have installed and configured server 2012 R2 with kerio control as firewall
    just MY WEBSITE (LIVE DOMAIN) DO NOT WORK , its message: “This site can’t be reached, http://www.MYDOMAIN.gov.af’s server DNS address could not be found.”

    Reply

    • Milan Mihajlov
      October 28, 2016 @ 8:41 am

      Hi. This problem description is way too general.

      Reply

  10. Tharuth Perera
    February 22, 2017 @ 6:04 am

    Thanks a lot for the article, this become handy for my problem.

    Reply

    • Milan Mihajlov
      March 9, 2017 @ 9:32 am

      Glad to help

      Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

0 Shares
Tweet
Pin
Share
+1