Different ISPs doing things differently, I reckon, SD.
It's not a "live" address, per the lookup I used. I normally use the Pipex DNS, cos it comes with the turf.
I can ping 202.4.232.132 and get replies - 306ms round trip.
That IP resolves as Anchorhosting, in Sydney.
If I try a tracert on it, then I get a no, even in the most basic format:
C
>tracert owner.com.au
Unable to resolve target system name owner.com.au.
If I run a fast tracert on the IP address you have, and using Pipex "as is" then I get:
12/06/06 01:08:21 Fast traceroute 202.4.232.132
Trace 202.4.232.132 ...
1 192.168.8.1 0ms 0ms 0ms TTL: 0 (my.router bogus rDNS: host not found [authoritative])
2 62.241.161.244 12ms 12ms 12ms TTL: 0 (l1.ar02.gs1.dsl.pipex.net ok)
3 62.241.161.102 12ms 11ms 12ms TTL: 0 (ge-1-1-0-0.cr01.gs1.dsl.pipex.net ok)
4 146.188.53.221 25ms 12ms 12ms TTL: 0 (GigabitEthernet4-0.GW4.LND2.ALTER.NET ok)
5 158.43.233.118 13ms 11ms 35ms TTL: 0 (so-0-0-0.xr2.lnd2.alter.net ok)
6 146.188.7.234 12ms 13ms 12ms TTL: 0 (so-1-1-0.TR2.LND2.ALTER.NET ok)
7 146.188.8.169 86ms 88ms 87ms TTL: 0 (so-6-0-0.IR1.DCA4.ALTER.NET ok)
8 146.188.13.33 87ms 86ms 88ms TTL: 0 (0.so-0-0-0.IL1.DCA6.ALTER.NET ok)
9 152.63.42.185 89ms 89ms 89ms TTL: 0 (g3-22-3802.cr05.tn5.bb.pipex.net fraudulent rDNS)
10 152.63.43.169 93ms 93ms 93ms TTL: 0 (g3-22-3802.cr05.tn5.bb.pipex.net fraudulent rDNS)
11 204.255.168.98 91ms 120ms 90ms TTL: 0 (No rDNS)
12 209.244.11.9 91ms 92ms 89ms TTL: 0 (so-2-1-0.bbr1.Washington1.Level3.net ok)
13 64.159.1.157 158ms 155ms 156ms TTL: 0 (as-0-0.bbr1.LosAngeles1.Level3.net ok)
14 4.68.102.141 158ms 157ms 159ms TTL: 0 (g3-22-3802.cr05.tn5.bb.pipex.net fraudulent rDNS)
15 4.78.195.202 154ms 154ms 162ms TTL: 0 (g3-22-3802.cr05.tn5.bb.pipex.net fraudulent rDNS)
16 203.208.148.18 304ms 304ms 305ms TTL: 0 (No rDNS)
17 61.88.179.106 306ms 305ms 304ms TTL: 0 (g3-22-3802.cr05.tn5.bb.pipex.net fraudulent rDNS)
18 203.202.87.2 306ms 307ms 307ms TTL: 0 (BusinessNetworks.o2occ76f01.optus.net.au ok)
19 218.185.80.58 307ms 306ms 305ms TTL: 0 (vl178.agg1.mil100.uecomm.net.au ok)
20 218.185.80.17 306ms 305ms 305ms TTL: 0 (vl182.agg1.cla55.uecomm.net.au ok)
21 218.185.80.30 305ms 305ms 307ms TTL: 0 (vl170.agg1.har400.uecomm.net.au ok)
22 218.185.80.74 310ms 305ms 306ms TTL: 0 (186.gi0-1.ar1.har400.uecomm.net.au ok)
23 218.185.71.190 310ms 311ms 310ms TTL: 0 (No rDNS)
24 No Response * * *
25 202.4.232.132 308ms 308ms 308ms TTL: 44 (g3-22-3802.cg3-22-3802.cr05.tn5.bb.pipex.net fraudulent rDNS)
So I ran the DNS looker-upper
here
and got a very interesting report, telling me about the things that are wrong, but agreeing that the bottom line is indeed 202.4.232.132
There were some FAIL items in there, which may be why Pipex doesn't like it.
That's probably also why some folks can connect, and some can't.