DNS Conditional Forwarder returns name without IP address or error RRS feed

  • Question

  • Hi,

     I have a conditional forwarder on my DC (DC1, IP = pointing at for DNS zone "", I've noticed some odd behaviour:

    -If I do an nslookup on DC1 for I get a response  as follows:



    In fact, I get the same response if I do an nslookup for any sub domain of that domain, e.g.



    I would have expected the conditional forwarder to error and respond no domain, but that doesn't happen. Why doesn't the forwarding DNS server respond with an IP address or error for the query?

    The reason why I'm asking is that we use mail checking to check for existent SMTP domains, some valid domains are being accepted such as "" other domains are not e.g. "", I'm thinking of creating a new internal DNS zone called "" with an SOA record of my DNS server and an Nameserver record of to ensure my mail appliance check passes on the domain lookup.

    Thank you

    • Edited by EuroTechie2013 Monday, January 30, 2017 11:46 AM more info
    Monday, January 30, 2017 11:17 AM

All replies

  • Hi Euro,

    >>Why doesn't the forwarding DNS server respond with an IP address or error for the query?

    Have you tried to ping to check if could be ping correctly?

    You could use Debug Logging tools that was in DNS server to check if DNS server has accepted query result from conditional forwarder.

    Here is information about Debug Logging for your reference:

    DNS Logging and Diagnostics

    Best Regards


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

    Tuesday, January 31, 2017 8:36 AM
  • Hi,

     The server isn't pingable, only port 53 is open. The DNS debug logs are partially helpful, maybe I'm just not good at interpreting the results

    I do see NXDOMAIN in the detailed logs and searches for AAA, A, plus multiple DNS lookups such as, as well as and

    I'm still not sure why the standard nslookup doesn't return an IP address or error though.

    Thursday, February 2, 2017 1:13 PM