One site is invisible

S

sarahk

Verified User
Joined
May 11, 2006
Messages
29
Location
Auckland, New Zealand
Last edited:
Just thought I'd post how the DNS settings look.
 

Attachments

  • propertyi.jpg
    propertyi.jpg
    49.9 KB · Views: 284
if ns1.propertyinvestor.info is a nameserver on your machine you will have to add the right A record for it:
ns1.propertyinvestor.info. A xxx.xxx.xxx.xxx

Ed,
 
thanks for the speedy reply

So this should look be right?
I just have to wait for the settings to propogate?

I tried using a surfing proxy and that still got a timeout.
 

Attachments

  • propertyi2.jpg
    propertyi2.jpg
    46.5 KB · Views: 241
no , still dont see it ??
on what line doe you see ns1.propertyinvestor.info.
between the A records ?

Ed,
 
The A records only let me use the IP and I've got those all set for the dedicated IP.

ns1.hostingdirect.co.nz is on 60.234.71.66
 

Attachments

  • propertyi3.jpg
    propertyi3.jpg
    33.9 KB · Views: 236
Something is wrong with your server, I guess...

If we take a look at the dnsreport for the domain:
http://www.dnsreport.com/tools/dnsreport.ch?domain=http://www.propertyinvestor.info

The first thing you notice is open dns server. Well, this can 'support' ddos attacks, but is not related to this problem.

Secondly we find that your IP 60.234.71.70 is not responding to DNS calls. Not unusual, but still bad and could be a beginning of understanding the problem.

Thirdly there's a few warnings, of which 'TCP allowed' means that the TCP connection to the IP of the nameserver (that .70 IP) failed.
So both UDP and TCP failed. That's bad, although could mean a few things.

But we're not there yet:
Your MX record states:
10 mail.propertyinvestor.info. [TTL=14400] IP=60.234.71.70
Which means, it will use .70 to deliver mail to. But then another error, it's unable to connect there.

Which was the last real error. If you look at all of this, you can come to the following conclusion:
The IP 60.234.17.70 is totally not responding to any requests. Which is bad, as this makes your website unavailable.
Furthermore, when trying to confirm this with a portscan, I got:
Note: Host seems down.

If the host is NOT down, you should contact the provider to confirm the IP is actually bound to the server. If you yourself manage this server, login as root (ssh) and type: "ifconfig<enter>", and check to see if there's something like:
Code: 
eth0      Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx
          inet addr:<the .70 ip>  Bcast:<some ip>  Mask:<some subnet>

If this is the case, there's something wrong, which I am unable to explain just yet. Unless you're next to the server, and there's a firewall between Internet and the server, or you've used iptables to make sure no one can access the server...


If it's not listed, you should try to find out why, as DA should write the config data to bring up and interface when the system is rebooted.


The reason DNS still works is due to the fact it solely depends on the second DNS server at the moment. Which will dump it's record after 14 day's of being unable to connect to you server.

So, can you confirm the .70 IP is actually working?
 
Thanks for your help, guys, I really appreciate it.

If I put the ip into my browser I get the site, as expected (see screenshot) and I can't see why I would if you can't.

I'll send your feedback to the host but it's getting critical.

We've used the direct admin tools to add the IP but the hosting company setup the IP address itself. I'll see what they say

thanks so much

Sarah
 

Attachments

  • propertyi5.jpg
    propertyi5.jpg
    60.6 KB · Views: 240
Hmm, by the looks you can actually see the site in real time. I get connection problems when I try to traceroute to it.

Can you provide a traceroute from your Windows computer to the ip?
tracert <ip> in a command window :).
 
I have the same problem. take a look:

teamterreur.com doesn't work

j-fbedardinc.com work

Same server, same ip, same configuration ???
 
You must log in or register to reply here.
Back
Top