Windows caching DNS cannot resolve particular "external" record RRS feed

  • Question

  • Hi,
    I have situation here that many MS DNSes (2008, 2012, 2016) configured for AD and caching resolving (NO FORWARDERS) cannot resolve :

    Server:  XYZ
    ***XYZ can't find Non-existent domain

    Cleared cache, restarted DNS ... no difference. OTHER (such as bind) DNSes in the SAME network can resolve (record is actually CNAME pointing at

    The only suspition is weird capitalization (bold). If I happen to find working MS DNS resolving the record, it returns it WITHOUT the capitals. But this shouldn't really matter, should it!?

    Thanks for ANY ideas, getting out of ammo.


    Saturday, February 10, 2018 7:45 AM

All replies

  • Hi,
    Thank you for your question. 
    I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
    Thank you for your understanding and support.
    Best Regards,


    Please remember to mark the replies as an answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    Monday, February 12, 2018 8:12 AM
  • Thanks a lot. The sooner the better.

    Not that I'm in such a hurry, but these probs tend to quietly disappear / are hard to reproduce.


    Monday, February 12, 2018 8:32 AM
  • Any news please?



    Thursday, February 15, 2018 12:44 PM
  • bounce ... ?


    Wednesday, March 21, 2018 8:57 PM