DNS 문제, nslookup 작동, ping 작동 안 함

DNS 문제, nslookup 작동, ping 작동 안 함

---

아파트에 개발 서버를 설치하고 있습니다. 나는 그것에 우분투 DNS 서버를 설정하고 영역 weddinglist 추가 한 (단지 weddinglist - 아니 TLD를 . 그것은 단지 내부 도메인입니다.)

이것은 내 Ubuntu 노트북에서 잘 작동합니다.

모든 Windows PC (Vista 및 XP)에서 명령 프롬프트에서 다음을 얻습니다.

C:\Users\Giles Roadnight>nslookup weddinglist
Server:  UnKnown
Address:  192.168.0.40

Name:    weddinglist
Address:  192.168.0.41


C:\Users\Giles Roadnight>ping 192.168.0.41

Pinging 192.168.0.41 with 32 bytes of data:
Reply from 192.168.0.41: bytes=32 time<1ms TTL=64
Reply from 192.168.0.41: bytes=32 time<1ms TTL=64
Reply from 192.168.0.41: bytes=32 time<1ms TTL=64
Reply from 192.168.0.41: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.0.41:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\Giles Roadnight>ping weddinglist
Ping request could not find host weddinglist. Please check the name and try again.

내 ipconfig :

C:\Users\Giles Roadnight>ipconfig -all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : Giles-Desktop
   Primary Dns Suffix  . . . . . . . :
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010 PCI Gigabit Ethernet Controller
   Physical Address. . . . . . . . . : **-**-**-**-**-**
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   Link-local IPv6 Address . . . . . : fe80::f179:680f:f313:5448%8(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.0.5(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : 192.168.0.1
   DNS Servers . . . . . . . . . . . : 192.168.0.40
   NetBIOS over Tcpip. . . . . . . . : Enabled

nslookup은 괜찮지 만 ping을 할 수없고 weddinglist에서 웹 페이지에 액세스 할 수 없기 때문에 DNS 설정이 정상이라고 확신합니다.

Windows PC에서 ping이 작동하도록하려면 어떻게해야합니까?

---

Windows 내부 확인자가 도메인 이름에 점이 없기 때문에 '.local'을 추가 할 수 있습니다. nslookup그렇게하지 않을 것입니다.

이 가능성을 확인하려면 클라이언트 컴퓨터에 'Wireshark'(이전 이름 ​​: Ethereal)를 설치하고 ping명령 을 실행할 때 나가는 DNS 요청 패킷을 관찰하십시오 .

---

좋습니다. 집에있는 내 XP 컴퓨터에 대한 추가 조사에 따르면 단일 레이블 이름 (예 : "foo"또는 "foo.")에 대해 시스템은 DNS를 전혀 사용하지 않고 대신 NBNS (NetBios 이름 서비스)를 사용합니다.

http://www.chicagotech.net/netforums/viewtopic.php?t=1476에 있는 힌트를 사용하여 ""라는 단일 항목을 입력하여 단일 레이블 도메인에 대한 DNS 조회를 강제 할 수 있음을 발견했습니다. 은 "에서 (순서대로) 추가] 다음 DNS 접미사 은"에서 " 고급 TCP / IP 설정 "대화 상자

---

다중 레이블 이름 즉 test.internal을 사용할 때 가끔이 문제가 발생했습니다.

나를위한 해결책은 Windows 7 컴퓨터에서 dnscache를 중지 / 시작하는 것이 었습니다. 관리자로 콘솔을 열고 입력하십시오.

net stop dnscache
net start dnscache

그런 다음 한숨을 쉬고 Mac을 주 데스크톱으로 사용할 방법을 찾으십시오.

---

내 홈 서버에서 실행되는 IIS와 동일한 문제가 있으며 클라이언트 컴퓨터에서 ipconfig /flushdns일반적으로 같은 명령 으로 문제를 해결합니다.

---

나는 같은 문제가 있었다. 다른 답변에서 지적했듯이 ping 및 nslookup은 다른 메커니즘을 사용하여 ip를 조회합니다.

동일한 도메인에 있지 않은 시스템에 ping을 시도 할 가능성이 있습니다. 서버의 정규화 된 이름을 ping하면 작동합니다.

nslookup 작동 :

PS C:\Users\Administrator> nslookup nuget
Server:  ad-01.docs.com
Address:  192.168.10.20

Name:    nuget.docs.com
Address:  192.168.10.17

Ping 실패 :

PS C:\Users\Administrator> ping nuget
Ping request could not find host nuget. Please check the name and try again.

FQDN을 사용하여 Ping이 작동합니다.

PS C:\Users\Administrator> ping nuget.docs.com

Pinging nuget.docs.com [192.168.70.17] with 32 bytes of data:
Reply from 192.168.10.17: bytes=32 time=1ms TTL=127
Reply from 192.168.10.17: bytes=32 time=2ms TTL=127
Reply from 192.168.10.17: bytes=32 time=2ms TTL=127
Reply from 192.168.10.17: bytes=32 time=2ms TTL=127

Ping statistics for 192.168.10.17:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 2ms, Average = 1ms

---

이 문제를 해결하려면 컴퓨터의 DNS 설정을 변경하고 조회 할 DNS 접미사를 추가해야합니다.

1. Control Panel\Network and Internet\Network Connections
2. Network adapter -> properties
3. IPV4 -> Properties
4. General tab -> Advanced
5. DNS Tab
6. Select "Append these DNS suffixes (in order)"
7. Add the required domain names
8. Disable, then enable your network adapter (don't do this on a VM, you'll loose your connection, instead try 'ipconfig /renew')

---

I think this behavior can be turned off, but Window's online help wasn't extremely clear:

If you disable NetBIOS over TCP/IP, you cannot use broadcast-based NetBIOS name resolution to resolve computer names to IP addresses for computers on the same network segment. If your computers are on the same network segment, and NetBIOS over TCP/IP is disabled, you must install a DNS server and either have the computers register with DNS (or manually configure DNS records) or configure entries in the local Hosts file for each computer.

In Windows XP, there is a checkbox:

Advanced TCP/IP Settings

[ ] Enable LMHOSTS lookup

There is also a book that covers this at length, "Networking Personal Computers with TCP/IP: Building TCP/IP Networks (old O'Reilly book)". Unfortunately, I cannot look it up because I disposed of my copy a while ago.

---

Do you have an entry for weddinglist in your hosts file? You can find this in:

C:\WINDOWS\system32\drivers\etc

nslookup always uses DNS whereas ping uses other methods for finding hostnames as well.

---

I found a little bug in windows Server 2003 R2 EE. you know that when you specify your IP address in the NIC (network connections), windows tells you that if you dont specify the preferred DNS server, it will put his own ip because it is an DNS server? well it doesn't do that...

I fixed my problem writing the dns adress manually, instead of letting windows do it for me.

---

Try ipconfig /displaydns and look for weddinglist. If it's cached as "name does not exist" (possibly because of a previous intermittent failed lookup), you can flush the cache with ipconfig /flushdns.

nslookup doesn't use the cache, but rather queries the DNS server directly.

It worked for me..

from https://superuser.com/a/507892

---

If you can ping the FQDN, look at how DNS devolution is set up the PC.

Winsock API which MS ping will automatically use the FQDN of the client PC if append primary and connection specific DNS suffix is checked in TCP/IP advanced DNS settings. If the host is in another domain, the client must perform DNS devolution.

Under XP TCP/IP advanced properties DNS, make sure append parent suffixes is checked so that the ping request traverses the domain back to the parent.

---

I think the problem can be because of the NAT. Normally the DNS clients make requests via UDP. But when the DNS server is behind the NAT the UDP requests will not work.

---

I know it's not your specific problem, but I faced the same symptoms when I configured a static IP address in the network adapter settings and forgot to enter a "Default Gateway".

Leaving the field blank, the network icon shows an Internet connection, and I could ping internal servers but not external ones, so I assumed it was a DNS problem. NSLookup still worked, but of course, ping failed to find the server (again, seemed like a DNS issue.) Anyway, one more thing to check. =P

---

FYI - I have been struggling with this issue for the past 3 hours. tried everything, flushing DNS, using a proxy, resetting catalog using netsh and clearing the routes. nothing worked so i decided to give windows restore a try, I did it using a windows cd -> repair -> system restore and it worked ! couldnt find any solutions online so i figured id post it

---

I also encountered this issue. No Windows application (except Chrome) could access the internet. I found it was a duplicate IP on the LAN. I changed the local IP, and everything, including ping, started working again.

I found the problem doing an

IPCONFIG /ALL

and it listed

IPv4 Address. . . . . . . . . . . : 10.10.0.20(Duplicate)

---

I also had this problem on a Server 2012 R2 VM joined to my local AD domain. I eventually solved the problem by taking the VM off the domain and re-joining it.

참고URL : https://stackoverflow.com/questions/330395/dns-problem-nslookup-works-ping-doesnt