Server Not Found message

[The Voice]

Dear Gurus' ..

I use Mozilla as my browser, and have AVG/Zonealarms running as AV and firewall. Also have spyware doctor tootling around as well as hubby thought he was doing the right thing when he found a problem!

I have always been able to get onto a site "owner.com.au" without any issue, however in the last few days, I have not, and am getting "the server not found" message.

I have asked a friend if they were also having the same problem, but lo and behold - they are able to acces the site, so back I went and - nada, azip zero zilch ..

I tried IE - same result.

My logical brain decided that perhaps something somewhere has picked this site as being a baddy (it isn't - it is a real estate site). I have been into Firefox/ZA and ticked and unticked everything that I could think of, and have included the site in the trusted zone/white lists .. and it still doesn't want to load.

Anyone got any thoughts as to what may be blocking this site?

[Silverspoonaviator]

sounds like Zone Alarm

Ensure zone alarm open, the try to reload web site, this should offer you the option to accept web site.

[The Voice]

Thanks for that .. I tried that didn't work, I turned off the f/wall - the page still wouldn't load ..

[Saab Dastard]

Voice,

Interesting - both "owner.com.au" and "www.owner.com.au" resolve to 202.4.232.132.

But if I enter http://202.4.232.132 as the address I get "www.tangy.com", which is a domain name hosting site, with a banner ad for owner.com.au at the bottom.

What happens if you enter http://202.4.232.132 in your browser?

Also what do you get when you PING owner.com.au, www.owner.com.au and 202.4.232.132?

SD

[Keef]

Same as SD. According to the registration site, owner.com.au is:


Domain Name: owner.com.au
Last Modified: 27-Feb-2006 22:10:26 UTC
Registrar ID: R00007-AR
Registrar Name: Bottle Domains
Status: OK

Registrant: owner.com
Registrant ID: OTHER None given

Eligibility Type: Other

Eligibility Name: owner.com
Eligibility ID: BN7225908 (QLD)

Registrant ROID: C3662819-AR
Registrant Contact Name: Philip Doble
Registrant Email: Visit whois.ausregistry.com.au for Web based WhoIs

Tech ID: C3662819-AR
Tech Name: Philip Doble
Tech Email: Visit whois.ausregistry.com.au for Web based WhoIs

Name Server: ns1.telstra.net
Name Server: granite.datahost.com.au

- in other words, it's not in use.

I can't finger it, traceroute it, or ping it. I think your computer is being very honest with you.

[matt_hooks]

And yet it definitely IS in use. I have typed the address in and got the real estate website.

Have you tried clearing down cookies and temp internet files? Are you having trouble accessing any other sites?

Also try running full spyware/adware scans and antivirus.

Don't forget to make sure you can remember all your passwords for sites etc. as deleting the cookies might stop auto logins to pw protected sites working.

See if any of that helps. If the spyware/adware scans come up with anything note the names and put them up here.

Good luck and happy hunting!

Matt

[Saab Dastard]

keef,

I have no problem pinging OR tracerting to it.
It definitely IS in use.

Tracing route to owner.com.au [202.4.232.132]
over a maximum of 30 hops:

*****
*****
*****
*****
5 12 ms 13 ms 14 ms bcs1-so-2-2-0.londonlnx.savvis.net 206.24.169.169]
6 118 ms 84 ms 84 ms bcs2-so-0-0-0.NewYork.savvis.net [204.70.192.121]
7 86 ms 84 ms 92 ms bcs1-so-6-0-0.NewYork.savvis.net [204.70.192.37]
8 126 ms 106 ms 108 ms dcr2-so-3-0-0.Chicago.savvis.net [204.70.192.101]
9 131 ms 156 ms 132 ms dcr2-so-0-0-0.dallas.savvis.net [204.70.192.98]
10 134 ms 133 ms 162 ms dcr1-so-4-3-0.losangeles.savvis.net [204.70.192.249]
11 161 ms 162 ms 160 ms ber1-tenge-2-1.losangeles.savvis.net [204.70.193.106]
12 162 ms 158 ms 171 ms ber1-tenge-3-1.losangeles.savvis.net [204.70.193.50]
13 168 ms 310 ms 167 ms 208.172.44.138
14 323 ms 435 ms 310 ms 203.208.148.18
15 320 ms 321 ms 321 ms 61.88.179.106
16 322 ms 321 ms 322 ms vl178.agg1.mil100.uecomm.net.au [218.185.80.58]
17 336 ms 321 ms 321 ms vl182.agg1.cla55.uecomm.net.au [218.185.80.17]
18 321 ms 321 ms 323 ms vl170.agg1.har400.uecomm.net.au [218.185.80.30]
19 320 ms 322 ms 365 ms 186.gi0-1.ar1.har400.uecomm.net.au [218.185.80.74]
20 323 ms 333 ms 323 ms 186.gi0-1.ar1.har400.uecomm.net.au [218.185.80.74]
21 322 ms * 323 ms 218.185.71.190
22 323 ms 322 ms * 202.4.232.132
23 321 ms 325 ms 323 ms 202.4.232.132

Trace complete.

SD

[Keef]

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.

[Oceanz]

Don't worry about the way the IP resolves - it is W3C practice these days to share IP addresses amongst many websites - basically there are not enough IP's to go around. For those interested there are several RFC's on the subject you can read on the w3c website. In my case I have over 60 domains/websites using the same IP.

The IP address will direct the viewer to the DNS server for the webhost, and it will send the viewer to the correct website.

If other people are reaching the site OK then the problem is not the webhost's DNS records. Most likely culprit is either a bad cached address on your computer or a bad record in your ISP's DNS server.

Oceanz

[The Voice]

Hey guys .. thanks for taking the time to have a look.

SD .. if I put the 202 address in, I get tangy.com etc .. I don't get the banner add for the site.

I'm not sure how I would ping something, but I still cannot get onto the site either way ..

damn it!

update: have spoken to my ISP (Iprimus) who have begun an investigation ...