none
UnKnown can't find: Non-existent domain RRS feed

  • Question

  • Hi,

    I've setup my own virtual lab for my own learning and training purposes. I'm using Hyper-V on a Windows 10 host. I've created two VM on my Hyper-V, which was my DC (AD/DNS/DHCP) and a client machine (Windows 10). My virtual switch for this lab is a external switch, and no changes on that virtual NIC, it is configured as obtained.

    Now on my VM setup, for my Windows Server 2016:

    I already promoted my Server as my DC, created my own OU's in AD for my local domain.

    The ip configuration for my DC is:

    IP: 192.168.254.200

    Subnet: 255.255.255.0

    Gateway: 192.168.254.254

    DNS1: 192.168.254.200

    For my DHCP: 

    I only created a scope for my server, and my Windows 10 client is already getting an IP from my DHCP.

    For the DNS: 

    I have only configured my reverse lookup zone and already created a Pointer for that.


    In my Windows 10 client, I was able to join it to my local domain and logon using the account that I created in AD. My ip configuration for my client is in obtained and then the DNS is pointed to my DC ip which is 192.168.254.200.

    Now the question is when I do try to nslookup in my server, this is the result:

    C:\Users\Administrator>nslookup
    DNS request timed out.
        timeout was 2 seconds.
    Default Server:  UnKnown
    Address:  ::1

    > cat.local
    Server:  UnKnown
    Address:  ::1

    Name:    cat.local
    Address:  192.168.254.200

    > catad01.cat.local
    Server:  UnKnown
    Address:  ::1

    Name:    catad01.cat.local
    Address:  192.168.254.200

    > 192.168.254.200
    Server:  UnKnown
    Address:  ::1

    Name:    CATAD01.cat.local
    Address:  192.168.254.200


    When I do try to nslookup on my Windows 10 client, this is the result:

    C:\Windows\system32>nslookup
    Default Server:  UnKnown
    Address:  fe80::5ea8:6aff:fe7b:96d5

    > 192.168.254.200
    Server:  UnKnown
    Address:  fe80::5ea8:6aff:fe7b:96d5

    *** UnKnown can't find 192.168.254.200: Non-existent domain
    > cat.local
    Server:  UnKnown
    Address:  fe80::5ea8:6aff:fe7b:96d5

    *** UnKnown can't find cat.local: Non-existent domain
    > catad01.cat.local
    Server:  UnKnown
    Address:  fe80::5ea8:6aff:fe7b:96d5

    *** UnKnown can't find catad01.cat.local: Non-existent domain
    >

    What would be the cause of this? did I miss something on my configuration particularly in DNS? Any help and suggestion that could help me and improve would be appreciated. I'm fairly new in server as I'm only watching tutorials online. Thanks.
    Wednesday, June 26, 2019 2:20 AM

All replies

  • Hello,

    Thank you for posting in this forum.

    Can you show this interface of your DNS server?

    Best Regards,

    Leon


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, June 27, 2019 7:00 AM
  • Hi Leon,

    Thanks for the response, as of the moment I can't post any images as my account needs to be verified first, hopefully it will be verified soon. In the mean time, is there any other way I can show you my DNS interface? I mean in a form of copy/paste the info that you need perhaps?

    I actually did some workaround in my client, I untick/disable the IPv6 from the network adapter of my client computer then suddenly when I do tried to nslookup, it gives me a response, I know it's not normal to disable the IPv6 of the client.

    C:\Users\dwest>nslookup
    Default Server:  MYLABAD01.mylab.local
    Address:  192.168.254.200

    > mylabad01.mylab.local
    Server:  MYLABAD01.mylab.local
    Address:  192.168.254.200

    Name:    mylabad01.mylab.local
    Address:  192.168.254.200

    > 192.168.254.200
    Server:  MYLABAD01.mylab.local
    Address:  192.168.254.200

    Name:    MYLABAD01.mylab.local
    Address:  192.168.254.200

    >

    Just an FYI, I setup a new lab environment in my Hyper-V, I changed my domain name from cat.local to mylab.local.

    Thanks.

    Friday, June 28, 2019 3:02 AM
  • Hi neophyte_J,

    " I know it's not normal to disable the IPv6 of the client. "

    In fact, it is normal to use this method.

    When using nslookup, it will not only look up the relevant records in the reverse area, but also query the IPv6 information of the record first if IPv6 is checked on client's NIC.

    Best Regards,

    Leon


    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, June 28, 2019 8:38 AM
  • Hi,

    Just checking in to see if the information provided was helpful. 
    Please let us know if you would like further assistance.

    Best Regards,
    Leon

    Please remember to mark the replies as answers if they help and unmark them if they provide no help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Tuesday, July 2, 2019 7:17 AM