How to solve DNS 101.101.2.1 can't find ping: Non-existent domain

NNZS
NNZS used Ask the Experts™
on
Hi Experts,

I can ping to domain with IP and FQDN.
But I used with nslookup, can ping with IP , success fully reply but I can pin with FQDN that say 101.101.2.1 can't find ping: Non-existent domain.

Pls advice to me

Regards,
SOE



REF: FYI
PING WITH IPCONFIG /ALL

C:\Documents and Settings\nnzs>ipconfig /all
Windows IP Configuration
        Host Name . . . . . . . . . . . . : SOE-LAPTOP
        Primary Dns Suffix  . . . . . . . : NETLINK-PDC.local
        Node Type . . . . . . . . . . . . : Unknown
        IP Routing Enabled. . . . . . . . : Yes
        WINS Proxy Enabled. . . . . . . . : Yes
        DNS Suffix Search List. . . . . . : NETLINK-PDC.local

Ethernet adapter Bluetooth Network Connection:

        Media State . . . . . . . . . . . : Media disconnected
        Description . . . . . . . . . . . : Bluetooth Device (Personal Area Netw
ork)
        Physical Address. . . . . . . . . : 00-16-AA-5B-66-57

Ethernet adapter Wireless Network Connection:

        Connection-specific DNS Suffix  . :
        Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Networ
k Connection
        Physical Address. . . . . . . . . : 00-13-AA-81-A7-E6
        Dhcp Enabled. . . . . . . . . . . : No
        IP Address. . . . . . . . . . . . : 101.101.2.109
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 101.101.2.100
        DNS Servers . . . . . . . . . . . : 101.101.2.1

Ethernet adapter Local Area Connection 2:

        Media State . . . . . . . . . . . : Media disconnected
        Description . . . . . . . . . . . : TAP-Win32 Adapter OAS
        Physical Address. . . . . . . . . : 00-FF-AA-7B-2E-26


PING CMD

C:\Documents and Settings\nnzs>ping 101.101.2.1
Pinging 101.101.2.1 with 32 bytes of data:
Reply from 101.101.2.1: bytes=32 time=2ms TTL=128
Reply from 101.101.2.1: bytes=32 time=16ms TTL=128
Reply from 101.101.2.1: bytes=32 time=1ms TTL=128
Reply from 101.101.2.1: bytes=32 time=2ms TTL=128
Ping statistics for 101.101.2.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 16ms, Average = 5ms

C:\Documents and Settings\nnzs>ping sl-pdc.netlink-pdc.local
Pinging sl-pdc.NETLINK-PDC.local [101.101.2.1] with 32 bytes of data:
Reply from 101.101.2.1: bytes=32 time=12ms TTL=128
Reply from 101.101.2.1: bytes=32 time=8ms TTL=128
Reply from 101.101.2.1: bytes=32 time=10ms TTL=128
Reply from 101.101.2.1: bytes=32 time=7ms TTL=128
Ping statistics for 101.101.2.1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 7ms, Maximum = 12ms, Average = 9ms


NSLOOKUP

C:\Documents and Settings\nnzs>nslookup
Default Server:  sl-pdc.netlink-pdc.local
Address:  101.101.2.1
> ping 101.101.2.1
Server:  [101.101.2.1]
Address:  101.101.2.1
*** 101.101.2.1 can't find ping: Non-existent domain

> ping sl-pdc.netlink-pdc.local
Server:  sl-pdc.netlink-pdc.local
Address:  101.101.2.1
*** sl-pdc.netlink-pdc.local can't find ping: Non-existent domain


 

Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Check your reversed lookup zone if it is populated, ip to dns resolving finds place in the reverse lookup zone
PowerShell Developer
Top Expert 2010
Commented:

This puts you inside the nslookup prompt:

> C:\Documents and Settings\nnzs>nslookup

You cannot use Ping once you're inside there, it makes no sense to nslookup at all.

You can do this:


C:\Documents and Settings\nnzs>nslookup
Default Server:  sl-pdc.netlink-pdc.local
Address:  101.101.2.1
> 101.101.2.1
> sl-pdc.netlink-pdc.local


And it will show you the same information as it just printed out in the Default Server statement.

Chris

Author

Commented:
I do this, result show below


Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\nnzs>nslookup
Default Server:  sl-pdc.netlink-pdc.local
Address:  101.101.2.1

> 101.101.2.1
Server:  sl-pdc.netlink-pdc.local
Address:  101.101.2.1

Name:    sl-pdc.netlink-pdc.local
Address:  101.101.2.1

> sl-pdc.netlink-pd.local
Server:  sl-pdc.netlink-pdc.local
Address:  101.101.2.1

*** sl-pdc.netlink-pdc.local can't find sl-pdc.netlink-pd.local: Non-exist
ent domain



SOE
Exploring SQL Server 2016: Fundamentals

Learn the fundamentals of Microsoft SQL Server, a relational database management system that stores and retrieves data when requested by other software applications.

Chris DentPowerShell Developer
Top Expert 2010

Commented:

You have a typo, you missed the c off pdc.

It can find sl-pdc.netlink.pdc.local, it does that as soon as you start nslookup. It's only the last attempt, where you miss out the c that fails.

Chris

Author

Commented:


ip to dns resolving, I can be find  in the reverse lookup zone.

SOE
Chris DentPowerShell Developer
Top Expert 2010

Commented:

Are you all set now? None of the issues mentioned above point to a problem.

Chris

Author

Commented:
sorry about that I miss C,


C:\Documents and Settings\nnzs>nslookup
Default Server:  sl-pdc.netlink-pdc.local
Address:  101.101.2.1

> sl-pdc.netlink-pdc.local
Server:  sl-pdc.netlink-pdc.local
Address:  101.101.2.1

Name:    sl-pdc.netlink-pdc.local
Address:  101.101.2.1


SOE
Chris DentPowerShell Developer
Top Expert 2010

Commented:

Much better :)

Chris

Author

Commented:
Thank Chris

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial