Ping me please :)

Toggle sidebar Toggle sidebar
V

vexcom

Junior Member
Apr 24, 2003
21
0
0
edit: OK THANKS FOR THE PINGS, BUT I HAVE ENOUGH NOW.
I need to know why my secondary nameserver (NS2) is responding when my primary (NS1) is up and fine


Any ideas???

THANKS!


 
A

amnesiac

Lifer
Oct 13, 1999
15,781
1
71
C:\Documents and Settings\Administrator>ping www.vexcom.com

Pinging vexcom.com [207.44.234.119] with 32 bytes of data:

Reply from 207.44.234.119: bytes=32 time=98ms TTL=44
Reply from 207.44.234.119: bytes=32 time=98ms TTL=44
Reply from 207.44.234.119: bytes=32 time=98ms TTL=44
Reply from 207.44.234.119: bytes=32 time=98ms TTL=44

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

Nohr

Diamond Member
Jan 6, 2001
7,302
32
101
www.flickr.com
Pinging www.vexcom.com [207.44.234.119] with 32 bytes of data:

Reply from 207.44.234.119: bytes=32 time=102ms TTL=46
Reply from 207.44.234.119: bytes=32 time=98ms TTL=46
Reply from 207.44.234.119: bytes=32 time=112ms TTL=46
Reply from 207.44.234.119: bytes=32 time=91ms TTL=46

Approximate round trip times in milli-seconds:
Minimum = 91ms, Maximum = 112ms, Average = 100ms
 

radioouman

Diamond Member
Nov 4, 2002
8,632
0
0
Pinging www.vexcom.com [207.44.234.119] with 32 bytes of data:

Reply from 207.44.234.119: bytes=32 time=62ms TTL=50
Reply from 207.44.234.119: bytes=32 time=47ms TTL=50
Reply from 207.44.234.119: bytes=32 time=47ms TTL=50
Reply from 207.44.234.119: bytes=32 time=47ms TTL=50

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

nsafreak

Diamond Member
Oct 16, 2001
7,093
3
81
Let's see I get this from a nslookup:

Non-authoritative answer:
Name: vexcom.com
Address: 207.44.234.119
Aliases: www.vexcom.com

And I get this from a traceroute (might help a lil more possibly than a ping):


1 20 ms 20 ms 20 ms res-adsl.idcomm.com [216.98.199.1]
2 20 ms 20 ms 30 ms cortex-eth2.idcomm.com [216.98.192.65]
3 20 ms 20 ms 30 ms sprint-ds3.idcomm.com [207.40.197.39]
4 30 ms 30 ms 20 ms sl-gw11-che-3-0-TS10.sprintlink.net [144.232.139
.53]
5 30 ms 20 ms 30 ms sl-bb20-che-3-1.sprintlink.net [144.232.15.149]

6 40 ms 50 ms 40 ms sl-bb23-chi-6-0.sprintlink.net [144.232.19.194]

7 40 ms 51 ms 40 ms 144.232.10.10
8 240 ms 280 ms 291 ms sl-abovenet-21-0.sprintlink.net [144.228.207.54]

9 290 ms 291 ms 310 ms so-2-2-0.cr1.ord2.us.mfnx.net [208.185.0.189]
10 551 ms 651 ms 500 ms pos5-0.mpr1.dfw2.us.mfnx.net [208.184.233.149]
11 460 ms 441 ms 461 ms so-3-0-0.cr1.dfw2.us.mfnx.net [216.200.127.213]

12 441 ms 581 ms 651 ms so-4-0-0.mpr1.iah1.us.mfnx.net [64.125.31.37]
13 60 ms 70 ms 80 ms 216.200.251.29.ev1.net [216.200.251.29]
14 60 ms 71 ms 70 ms 207.218.245.41
15 70 ms 70 ms 80 ms 207.44.234.119


 

BigSmooth

Lifer
Aug 18, 2000
10,484
12
81
Pinging vexcom.com [64.246.22.46] with 32 bytes of data:

Reply from 64.246.22.46: bytes=32 time=187ms TTL=240
Reply from 64.246.22.46: bytes=32 time=141ms TTL=240
Reply from 64.246.22.46: bytes=32 time=110ms TTL=240
Reply from 64.246.22.46: bytes=32 time=172ms TTL=240

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

Nohr

Diamond Member
Jan 6, 2001
7,302
32
101
www.flickr.com
Start menu > Run > type in "command" > hit OK

At the prompt type "ping <address>".

<address> can either be a name or ip address.
 
V

vexcom

Junior Member
Apr 24, 2003
21
0
0
Originally posted by: Nohr
www.vexcom.com = 207.44.234.119
vexcom.com = 64.246.22.46
Click to expand...


207 is the failover mirror server, 64 is the main server >=(

doesnt make sense


I query NS1, i get:


HEADER:
opcode = QUERY, id = 29620, rcode = NOERROR
header flags: reply, auth. answer, want recursion, recursion avail.
questions = 1, answers = 1, auth. records = 2, additional = 2
QUESTIONS:
vexcom.com., type = A, class = 1
ANSWERS:
-> vexcom.com.
type = A, class = 1, ttl = 86400, dlen = 4
IP address = 64.246.22.46
AUTHORITY RECORDS:
-> vexcom.com.
type = NS, class = 1, ttl = 86400, dlen = 18
nameserver = ns1.hosting2020.com.
-> vexcom.com.
type = NS, class = 1, ttl = 86400, dlen = 6
nameserver = ns2.hosting2020.com.
ADDITIONAL RECORDS:
-> ns1.hosting2020.com.
type = A, class = 1, ttl = 86400, dlen = 4
IP address = 64.246.22.46
-> ns2.hosting2020.com.
type = A, class = 1, ttl = 86400, dlen = 4
IP address = 207.44.234.119

**complete**

Same with WWW:

HEADER:
opcode = QUERY, id = 29651, rcode = NOERROR
header flags: reply, auth. answer, want recursion, recursion avail.
questions = 1, answers = 2, auth. records = 2, additional = 2
QUESTIONS:
www.vexcom.com., type = A, class = 1
ANSWERS:
-> www.vexcom.com.
type = CNAME, class = 1, ttl = 86400, dlen = 2
alias = vexcom.com.
-> vexcom.com.
type = A, class = 1, ttl = 86400, dlen = 4
IP address = 64.246.22.46
AUTHORITY RECORDS:
-> vexcom.com.
type = NS, class = 1, ttl = 86400, dlen = 18
nameserver = ns2.hosting2020.com.
-> vexcom.com.
type = NS, class = 1, ttl = 86400, dlen = 6
nameserver = ns1.hosting2020.com.
ADDITIONAL RECORDS:
-> ns1.hosting2020.com.
type = A, class = 1, ttl = 86400, dlen = 4
IP address = 64.246.22.46
-> ns2.hosting2020.com.
type = A, class = 1, ttl = 86400, dlen = 4
IP address = 207.44.234.119

**complete**


Now I query NS2 (which is - i htought anyway, only supposed to respond if NS1 is down, but it looks like its load balancing or something >=E )

HEADER:
opcode = QUERY, id = 29716, rcode = NOERROR
header flags: reply, auth. answer, want recursion, recursion avail.
questions = 1, answers = 1, auth. records = 2, additional = 1
QUESTIONS:
www.vexcom.com., type = A, class = 1
ANSWERS:
-> www.vexcom.com.
type = A, class = 1, ttl = 86400, dlen = 4
IP address = 207.44.234.119
AUTHORITY RECORDS:
-> vexcom.com.
type = NS, class = 1, ttl = 3600, dlen = 18
nameserver = ns2.hosting2020.com.
-> vexcom.com.
type = NS, class = 1, ttl = 3600, dlen = 6
nameserver = ns1.hosting2020.com.
ADDITIONAL RECORDS:
-> ns1.hosting2020.com.
type = A, class = 1, ttl = 86400, dlen = 4
IP address = 64.246.22.46

**complete**
HEADER:
opcode = QUERY, id = 29748, rcode = NOERROR
header flags: reply, auth. answer, want recursion, recursion avail.
questions = 1, answers = 1, auth. records = 2, additional = 1
QUESTIONS:
vexcom.com., type = A, class = 1
ANSWERS:
-> vexcom.com.
type = A, class = 1, ttl = 86400, dlen = 4
IP address = 207.44.234.119
AUTHORITY RECORDS:
-> vexcom.com.
type = NS, class = 1, ttl = 3600, dlen = 18
nameserver = ns2.hosting2020.com.
-> vexcom.com.
type = NS, class = 1, ttl = 3600, dlen = 6
nameserver = ns1.hosting2020.com.
ADDITIONAL RECORDS:
-> ns1.hosting2020.com.
type = A, class = 1, ttl = 86400, dlen = 4
IP address = 64.246.22.46

**complete**




This is nucking futz

Or maybe i dont really understand DNS? can anyone shed some light ion this???
 
T

txxxx

Golden Member
Feb 13, 2003
1,700
0
0
Tracing route to vexcom.com [207.44.234.119]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 18 ms 18 ms 19 ms lon1-adsl6.nildram.net [213.208.106.124]
3 19 ms 20 ms 20 ms lon1-9.nildram.net [213.208.106.194]
4 35 ms 20 ms 21 ms lndnuk1icx1.wcg.net [195.66.224.105]
5 93 ms 92 ms 93 ms nycmny2wcx2-oc12.wcg.net [64.200.87.153]
6 127 ms 127 ms 126 ms hrndva1wcx2-oc48.wcg.net [64.200.240.46]
7 126 ms 128 ms 127 ms hrndva1wcx3.oc48.wcg.net [64.200.95.78]
8 126 ms 129 ms 128 ms drvlga1wcx2-pos.wcg.net [64.200.210.57]
9 127 ms 126 ms 127 ms drvlga1wcx1-oc48.wcg.net [64.200.127.29]
10 128 ms 126 ms 126 ms dllstx1wcx3-oc48.wcg.net [64.200.240.21]
11 124 ms 124 ms 125 ms dllstx1wcx2-pos9-0.wcg.net [64.200.110.129]
12 129 ms 130 ms 130 ms dllstx1wcx2-intcomm-pos.wcg.net [64.200.111.178]

13 130 ms 130 ms 130 ms ev1.net-icc-gateway-64.200.162.2.ic2net.net [64.
200.162.2]
14 129 ms 125 ms 127 ms 207.218.245.41
15 128 ms 125 ms 127 ms 207.44.234.119

nslookup :
Server: radius.nildram.co.uk
Address: 195.112.4.4

Non-authoritative answer:
Name: www.vexcom.com
Address: 207.44.234.119
 
E

Ernieb

Senior member
Jan 13, 2002
880
0
0
Pinging www.vexcom.com [207.44.234.119] with 32 bytes of dat

Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

Anubis

No Lifer
Aug 31, 2001
78,712
427
126
tbqhwy.com

Pinging www.vexcom.com [207.44.234.119] with 32 bytes of data:

Reply from 207.44.234.119: bytes=32 time=133ms TTL=49
Reply from 207.44.234.119: bytes=32 time=66ms TTL=49
Reply from 207.44.234.119: bytes=32 time=62ms TTL=49
Reply from 207.44.234.119: bytes=32 time=62ms TTL=49

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

vexcom

Junior Member
Apr 24, 2003
21
0
0
Originally posted by: Ernieb
Pinging www.vexcom.com [207.44.234.119] with 32 bytes of dat

Request timed out.
Request timed out.
Request timed out.
Request timed out.

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

was rebooting...

Does anyone have a clue as to why the 2nd DNS server is giving out addresses?
 
D

dighn

Lifer
Aug 12, 2001
22,820
4
81
contacting my bots

going to ping in a sec

j/k



Pinging vexcom.com [207.44.234.119] with 32 bytes of data:

Reply from 207.44.234.119: bytes=32 time=82ms TTL=51
Reply from 207.44.234.119: bytes=32 time=81ms TTL=51
Reply from 207.44.234.119: bytes=32 time=82ms TTL=51
Reply from 207.44.234.119: bytes=32 time=83ms TTL=51

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

dakata24

Diamond Member
Aug 7, 2000
6,366
0
76
Pinging vexcom.com [207.44.234.119] with 32 bytes of data:

Reply from 207.44.234.119: bytes=32 time=50ms TTL=48
Reply from 207.44.234.119: bytes=32 time=50ms TTL=48
Reply from 207.44.234.119: bytes=32 time=50ms TTL=48
Reply from 207.44.234.119: bytes=32 time=60ms TTL=48

Ping statistics for 207.44.234.119:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 50ms, Maximum = 60ms, Average = 52ms
 
You must log in or register to reply here.

TRENDING THREADS

COMPANY
RESOURCES
FOLLOW
Top Bottom
sale-70-410-exam    | Exam-200-125-pdf    | we-sale-70-410-exam    | hot-sale-70-410-exam    | Latest-exam-700-603-Dumps    | Dumps-98-363-exams-date    | Certs-200-125-date    | Dumps-300-075-exams-date    | hot-sale-book-C8010-726-book    | Hot-Sale-200-310-Exam    | Exam-Description-200-310-dumps?    | hot-sale-book-200-125-book    | Latest-Updated-300-209-Exam    | Dumps-210-260-exams-date    | Download-200-125-Exam-PDF    | Exam-Description-300-101-dumps    | Certs-300-101-date    | Hot-Sale-300-075-Exam    | Latest-exam-200-125-Dumps    | Exam-Description-200-125-dumps    | Latest-Updated-300-075-Exam    | hot-sale-book-210-260-book    | Dumps-200-901-exams-date    | Certs-200-901-date    | Latest-exam-1Z0-062-Dumps    | Hot-Sale-1Z0-062-Exam    | Certs-CSSLP-date    | 100%-Pass-70-383-Exams    | Latest-JN0-360-real-exam-questions    | 100%-Pass-4A0-100-Real-Exam-Questions    | Dumps-300-135-exams-date    | Passed-200-105-Tech-Exams    | Latest-Updated-200-310-Exam    | Download-300-070-Exam-PDF    | Hot-Sale-JN0-360-Exam    | 100%-Pass-JN0-360-Exams    | 100%-Pass-JN0-360-Real-Exam-Questions    | Dumps-JN0-360-exams-date    | Exam-Description-1Z0-876-dumps    | Latest-exam-1Z0-876-Dumps    | Dumps-HPE0-Y53-exams-date    | 2017-Latest-HPE0-Y53-Exam    | 100%-Pass-HPE0-Y53-Real-Exam-Questions    | Pass-4A0-100-Exam    | Latest-4A0-100-Questions    | Dumps-98-365-exams-date    | 2017-Latest-98-365-Exam    | 100%-Pass-VCS-254-Exams    | 2017-Latest-VCS-273-Exam    | Dumps-200-355-exams-date    | 2017-Latest-300-320-Exam    | Pass-300-101-Exam    | 100%-Pass-300-115-Exams    |
http://www.portvapes.co.uk/    | http://www.portvapes.co.uk/    |