- Oct 10, 1999
- 31,392
- 12,872
- 136
Originally posted by: JMWarren
It's been up and down for me for the past few days. In London like you...you on Rogers?
I'm on Rogers too.Originally posted by: JSFLY
Originally posted by: JMWarren
It's been up and down for me for the past few days. In London like you...you on Rogers?
Im on rogers and it doesnt work for me.
Originally posted by: Iron Woode
I need the ip address of pics.bbzzdd.com to do some diagnostic checks.
I would be very thankful.
thanks.Originally posted by: Chronoshock
Originally posted by: Iron Woode
I need the ip address of pics.bbzzdd.com to do some diagnostic checks.
I would be very thankful.
72.232.196.98
Originally posted by: Iron Woode
thanks.Originally posted by: Chronoshock
Originally posted by: Iron Woode
I need the ip address of pics.bbzzdd.com to do some diagnostic checks.
I would be very thankful.
72.232.196.98
I can ping it no problem.
Here is what I got:
Pinging 72.232.196.98 with 32 bytes of data:
Reply from 72.232.196.98: bytes=32 time=42ms TTL=50
Reply from 72.232.196.98: bytes=32 time=43ms TTL=50
Reply from 72.232.196.98: bytes=32 time=43ms TTL=50
Reply from 72.232.196.98: bytes=32 time=42ms TTL=50
Ping statistics for 72.232.196.98:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 43ms, Average = 42ms
>tracert 72.232.196.98
Tracing route to gravity.hostingthing.us [72.232.196.98]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms rtsnet [192.168.1.1]
2 * * * Request timed out.
3 7 ms 8 ms 7 ms gw03.lndn.phub.net.cable.rogers.com [66.185.90.6
5]
4 10 ms 8 ms 8 ms gw01.lndn.phub.net.cable.rogers.com [66.185.93.1
77]
5 12 ms 11 ms 10 ms 64.71.241.105
6 13 ms 15 ms 19 ms 66.185.80.46
7 20 ms 21 ms 21 ms igw01.chcrmk.phub.net.cable.rogers.com [66.185.8
1.190]
8 21 ms 22 ms 21 ms 66.185.92.42
9 21 ms 21 ms 21 ms core-01-so-0-1-0-0.chcg.twtelecom.net [66.192.24
4.21]
10 41 ms 41 ms 40 ms core-01-so-1-0-0-0.dlfw.twtelecom.net [66.192.25
5.92]
11 44 ms 48 ms 42 ms hagg-02-ge-0-2-0-505.dlfw.twtelecom.net [66.192.
246.214]
12 43 ms 41 ms 41 ms 209.163.157.254
13 44 ms 42 ms 42 ms lt-pod1a.lt.com [63.164.96.230]
14 * * * Request timed out.
15 42 ms 44 ms 41 ms gravity.hostingthing.us [72.232.196.98]
Trace complete.
YGPMOriginally posted by: DeviousTrap
Originally posted by: Iron Woode
thanks.Originally posted by: Chronoshock
Originally posted by: Iron Woode
I need the ip address of pics.bbzzdd.com to do some diagnostic checks.
I would be very thankful.
72.232.196.98
I can ping it no problem.
Here is what I got:
Pinging 72.232.196.98 with 32 bytes of data:
Reply from 72.232.196.98: bytes=32 time=42ms TTL=50
Reply from 72.232.196.98: bytes=32 time=43ms TTL=50
Reply from 72.232.196.98: bytes=32 time=43ms TTL=50
Reply from 72.232.196.98: bytes=32 time=42ms TTL=50
Ping statistics for 72.232.196.98:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 43ms, Average = 42ms
>tracert 72.232.196.98
Tracing route to gravity.hostingthing.us [72.232.196.98]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms rtsnet [192.168.1.1]
2 * * * Request timed out.
3 7 ms 8 ms 7 ms gw03.lndn.phub.net.cable.rogers.com [66.185.90.6
5]
4 10 ms 8 ms 8 ms gw01.lndn.phub.net.cable.rogers.com [66.185.93.1
77]
5 12 ms 11 ms 10 ms 64.71.241.105
6 13 ms 15 ms 19 ms 66.185.80.46
7 20 ms 21 ms 21 ms igw01.chcrmk.phub.net.cable.rogers.com [66.185.8
1.190]
8 21 ms 22 ms 21 ms 66.185.92.42
9 21 ms 21 ms 21 ms core-01-so-0-1-0-0.chcg.twtelecom.net [66.192.24
4.21]
10 41 ms 41 ms 40 ms core-01-so-1-0-0-0.dlfw.twtelecom.net [66.192.25
5.92]
11 44 ms 48 ms 42 ms hagg-02-ge-0-2-0-505.dlfw.twtelecom.net [66.192.
246.214]
12 43 ms 41 ms 41 ms 209.163.157.254
13 44 ms 42 ms 42 ms lt-pod1a.lt.com [63.164.96.230]
14 * * * Request timed out.
15 42 ms 44 ms 41 ms gravity.hostingthing.us [72.232.196.98]
Trace complete.
That looks ok, the last hop prior the server is not supposed to resolve. PM me your IP address so I can check it from our end.
Using my company's DNS server address:$ dig pics.bbzzdd.com @24.153.23.66
; <<>> DiG 9.2.4 <<>> pics.bbzzdd.com @24.153.23.66
;; global options: printcmd
;; connection timed out; no servers could be reached
$ dig pics.bbzzdd.com @dns01.xxxxxxx.biz
; <<>> DiG 9.2.4 <<>> pics.bbzzdd.com @dns01.xxxxxxx.biz
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48944
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;pics.bbzzdd.com. IN A
;; ANSWER SECTION:
pics.bbzzdd.com. 300 IN A 72.232.196.98
;; Query time: 44 msec
;; SERVER: 10.x.xx.x#53(dns01.xxxxxxx.biz)
;; WHEN: Wed Jan 3 12:49:04 2007
;; MSG SIZE rcvd: 49
