도메인명으로 IP 확인

1 개요

도메인명으로 IP 확인
도메인명으로 IP 주소 찾기
도메인 이름으로 IP 알아내기
  • 윈도우에서는 nslookup, ping, tracert와 같은 명령어로 간단히 알 수 있다.

2 윈도우

2.1 방법 1: ping

C:\Users\zetawiki>ping google.com

Ping google.com [173.194.38.83] 32바이트 데이터 사용:
173.194.38.83의 응답: 바이트=32 시간=34ms TTL=50
173.194.38.83의 응답: 바이트=32 시간=32ms TTL=50
173.194.38.83의 응답: 바이트=32 시간=32ms TTL=50
173.194.38.83의 응답: 바이트=32 시간=32ms TTL=50

173.194.38.83에 대한 Ping 통계:
    패킷: 보냄 = 4, 받음 = 4, 손실 = 0 (0% 손실),
왕복 시간(밀리초):
    최소 = 32ms, 최대 = 34ms, 평균 = 32ms

2.2 방법 2: nslookup

C:\Users\zetawiki>nslookup google.com
서버:    google-public-dns-a.google.com
Address:  8.8.8.8

권한 없는 응답:
이름:    google.com
Addresses:  173.194.38.83
          173.194.38.84
          173.194.38.80
          173.194.38.81
          173.194.38.82
→ google.com은 5개의 IP로 분산처리(Load Balancing)되며 내 요청에 응답하는 IP는 173.194.38.83이다.
→ 필자는 DNS를 구글 것으로 사용하며, 구글 DNS의 IP는 8.8.8.8이다.

2.3 방법 3: tracert

C:\Users\zetawiki>tracert kt928.com

최대 30홉 이상의
google.com [173.194.38.83](으)로 가는 경로 추적:

  1     2 ms   154 ms     1 ms  192.168.0.1
...(중략)...

추적을 완료했습니다.

3 리눅스

3.1 방법 1: host

[root@zetawiki ~]# host yahoo.com
yahoo.com has address 98.139.183.24
yahoo.com has address 206.190.36.45
yahoo.com has address 98.138.253.109
yahoo.com mail is handled by 1 mta5.am0.yahoodns.net.
yahoo.com mail is handled by 1 mta6.am0.yahoodns.net.
yahoo.com mail is handled by 1 mta7.am0.yahoodns.net.

3.2 방법 2: ping

[root@zetawiki ~]# ping google.com -c 1
PING google.com (173.194.127.110) 56(84) bytes of data.
64 bytes from hkg03s12-in-f14.1e100.net (173.194.127.110): icmp_seq=1 ttl=52 time=68.7 ms

--- google.com ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 133ms
rtt min/avg/max/mdev = 68.767/68.767/68.767/0.000 ms
→ 173.194.127.110

3.3 방법 3: nslookup

[root@zetawiki ~]# nslookup google.com
Server:		8.8.8.8
Address:	8.8.8.8#53

Non-authoritative answer:
Name:	google.com
Address: 173.194.127.102
Name:	google.com
Address: 173.194.127.103
Name:	google.com
Address: 173.194.127.98
Name:	google.com
Address: 173.194.127.110
Name:	google.com
Address: 173.194.127.99
Name:	google.com
Address: 173.194.127.104
Name:	google.com
Address: 173.194.127.101
Name:	google.com
Address: 173.194.127.97
Name:	google.com
Address: 173.194.127.105
Name:	google.com
Address: 173.194.127.100
Name:	google.com
Address: 173.194.127.96

3.4 방법 4: dig

[root@zetawiki ~]# dig any google.com
;; Truncated, retrying in TCP mode.

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6 <<>> any google.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21523
;; flags: qr rd ra; QUERY: 1, ANSWER: 24, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com.			IN	ANY

;; ANSWER SECTION:
google.com.		300	IN	A	173.194.127.103
google.com.		300	IN	A	173.194.127.98
google.com.		300	IN	A	173.194.127.99
google.com.		300	IN	A	173.194.127.96
google.com.		300	IN	A	173.194.127.100
google.com.		300	IN	A	173.194.127.110
google.com.		300	IN	A	173.194.127.105
google.com.		300	IN	A	173.194.127.104
google.com.		300	IN	A	173.194.127.101
google.com.		300	IN	A	173.194.127.97
google.com.		300	IN	A	173.194.127.102
google.com.		300	IN	AAAA	2404:6800:4005:803::1005
google.com.		21600	IN	NS	ns2.google.com.
google.com.		21600	IN	NS	ns4.google.com.
google.com.		600	IN	MX	50 alt4.aspmx.l.google.com.
google.com.		21600	IN	SOA	ns1.google.com. dns-admin.google.com. 2013100300 7200 1800 1209600 300
google.com.		21600	IN	NS	ns1.google.com.
google.com.		600	IN	MX	10 aspmx.l.google.com.
google.com.		3600	IN	TXT	"v=spf1 include:_spf.google.com ip4:216.73.93.70/31 ip4:216.73.93.72/31 ~all"
google.com.		600	IN	MX	30 alt2.aspmx.l.google.com.
google.com.		21600	IN	TYPE257	\# 19 0005697373756573796D616E7465632E636F6D
google.com.		600	IN	MX	20 alt1.aspmx.l.google.com.
google.com.		600	IN	MX	40 alt3.aspmx.l.google.com.
google.com.		21600	IN	NS	ns3.google.com.

;; Query time: 78 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sat Dec  7 08:48:50 2013
;; MSG SIZE  rcvd: 577

4 같이 보기

문서 댓글 ({{ doc_comments.length }})
{{ comment.name }} {{ comment.created | snstime }}