Attn Admin

Their appears to be an image missing from the top left of the screen.
My browser seems to take ages trying to load something that is not there and finally gives me a frame with a missing image.
This also seems to hinder editing, I could not use the insert hyperlink unitll I hit my escape key to stop downloading this missing image.
Been like this for a few days now.

Feel free to delete this post

Colin

 

It shoud be better now. That image is server from the Clipsal web server (different to the C-Bus Forums websever) and I think it was offline or broken in someway (I'm still in the office and we had a Internet outage and I suspect that the servers were affected).

Anyway, it's working fine for me now, and hopefully for you as well.

 

Exactly the same problem for me a while back
http://www.cbusforums.com/forums/showthread.php?t=1622&highlight=admin

I solved it by holding SHIFT + clicking REFRESH, then holding CTRL + clicking REFRESH of the page. What that does is force a full reload of everything from the servers, which clears the cache of the browser and also any proxy servers (eg: ISP) also in the route from Clipsal server to you.

Cheers, John

 

Sorry to say it is still missing.

www.clipsal.com - www.clipsal.co.nz - etc, have been unreachable for over a week now.

Colin

 

I see both these domains fine from Browsers located both outside the Clipsal network and inside.. If you can't see these then your ISP may have a DNS issue or you have some sort of cache or proxy issue, either way, a call to your ISP's help desk may be in order.

 

Hey, did someone ask for my two cents?

I can access them without problems.

 

My ISP help desk is having difficulty seeing you as well.
They are going to trace the fault.
Colin

 

OK, let us know what they find.

 

DNS Health Check....


I have just looked up the clipsal.com.au domain name records

Your NS records at the parent servers are:

indom20.indomco.net. [128.121.244.236] [US]
indom30.indomco.fr. [213.205.102.3] [FR]
indom10.indomco.com. [217.174.200.97] [FR]

[These were obtained from ns2.ausregistry.net]

213.205.102.3 this name server does not respond to queries about clipsal.com.au




Now clipsal.com

indom20.indomco.net. [128.121.244.236] [TTL=7200]
indom30.indomco.fr. [213.205.102.3] [TTL=7200]
indom10.indomco.com. [217.174.200.97] [TTL=7200]

all 3 respond fine





Now cbusforums.com

ns1.audelegation.com. [69.56.142.2] [TTL=172800] [US]
ns2.audelegation.com. [69.56.145.245] [TTL=172800] [US]

[These were obtained from m.gtld-servers.net]

All respond fine






Now www.clipsal.co.nz

ns.win.co.nz. [210.55.105.193] [NZ]
ns2.win.co.nz. [210.55.230.1] [NZ]
ns3.win.co.nz. [209.123.221.169] [US]

[These were obtained from ns7.dns.net.nz]

All respond fine.




Charles

 

Howdi all,
213.205.102.3. has on 2 occasions returned a response as a lame nameserver. This has been the cause of the problems, in my opinion. This has now settled down and is resolving correctly. So other than a few minor issues as listed below things appear to be ok.

clipsal.com.au

indom30.indomco.fr. [213.205.102.3 (NO GLUE)] [FR]
indom10.indomco.com. [217.174.200.97 (NO GLUE)] [FR]
indom20.indomco.net. [128.121.244.236 (NO GLUE)] [US]

Glue name at parent:
The parent servers (I checked with ns-au.ripe.net.) are not providing glue for all your nameservers. This means that they are supplying the NS records (host.example.com), but not supplying the A records (192.0.2.53), which can cause slightly slower connections, and may cause incompatibilities with some non-RFC-compliant programs. This is perfectly acceptable behavior per the RFCs. This will usually occur if your DNS servers are not in the same TLD as your domain (for example, a DNS server of "ns1.example.org" for the domain "example.com"). In this case, you can speed up the connections slightly by having NS records that are in the same TLD as your domain.


SOA REFRESH value:
Your SOA REFRESH interval is : 86400 seconds. This seems high. You should consider decreasing this value to about 3600-7200 seconds (or higher, if using DNS NOTIFY). RFC1912 2.2 recommends a value between 1200 to 43200 seconds (20 minutes to 12 hours, with the longer time periods used for very slow Internet connections), and if you are using DNS NOTIFY the refresh value is not as important (RIPE recommend 86400 seconds if using DNS NOTIFY). This value determines how often secondary/slave nameservers check with the master for updates. A value that is too high will cause DNS changes to be in limbo for a long time. This has probably been the cause of the lame server listing.

SPF record:
Your domain does not have an SPF record. This means that spammers can easily send out E-mail that looks like it came from your domain, which can make your domain look bad (if the recipient thinks you really sent it), and can cost you money (when people complain to you, rather than the spammer). You may want to add an SPF record ASAP, as 01 Oct 2004 was the target date for domains to have SPF records in place (Hotmail, for example, started checking SPF records on 01 Oct 2004).
This can be done in a few seconds by following this link. http://www.openspf.org/
I highly recommend adding a record for all your domains.

 

Just to keep you updated.
Still no access. My ISP (paradise.net.nz) is (still) looking into the problem. They can see clipsal.com & .com.au & .co.nz from the help desk and their test machine.
However when I have completely disconnected my adsl modem from the network and they have logged in on my account they get the same results as myself.
They believe it may be routing problems.

As an aside I attempted to get to your site from a client's PC and still could not reach any of the sites. This clients ISP is xtra.co.nz.
I have just spoken with Clipsal IT here in Auckland, they are having no issues and they are also with xtra.co.nz, - go figure!

Colin

 

That does sound weird. Sorry to hear you are still having so much trouble. Thank god you can still access the forums thou.