Your DNS is broken and nobody can reach your site. I'm only reaching here because I've found the direct IP address.
$ dig @e.gtld-servers.net aneros.com ns
; <> DiG 9.8.4-P1 <> @e.gtld-servers.net aneros.com ns
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16404
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;aneros.com. IN NS
;; AUTHORITY SECTION:
aneros.com. 172800 IN NS ns75.domaincontrol.com.
aneros.com. 172800 IN NS ns76.domaincontrol.com.
;; ADDITIONAL SECTION:
ns75.domaincontrol.com. 172800 IN A 216.69.185.48
ns76.domaincontrol.com. 172800 IN A 208.109.255.48
;; Query time: 97 msec
;; SERVER: 192.12.94.30#53(192.12.94.30)
;; WHEN: Wed Mar 6 00:14:40 2013
;; MSG SIZE rcvd: 112
$ dig @ns75.domaincontrol.com www.aneros.com
; <> DiG 9.8.4-P1 <> @ns75.domaincontrol.com www.aneros.com
; (2 servers found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 37516
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;www.aneros.com. IN A
;; Query time: 175 msec
;; SERVER: 2607:f208:206::30#53(2607:f208:206::30)
;; WHEN: Wed Mar 6 00:15:38 2013
;; MSG SIZE rcvd: 32
$ host www.aneros.com
Host www.aneros.com not found: 2(SERVFAIL)
@twlltin - Congratulations on being the first non-staff carbon based unit to find your way back to the Aneros Forum without any help from the DNS servers. After @CT and his crew fix the more pressing concern of name resolution, you really should be presented with an award of some sort.
The only reason I found my way here was because of the information you placed on the "Aneros Unofficial Chat" webpage that I googled. My other attempts at finding out the IP address of the Aneros Forum, failed.
I am so glad that Aneros.com has finally come back online after a good day's downtime.
Thom./BigGlansDC
I now know the reason why it failed. aneros.com and highisland.com domains were shifted from one DNS provider to another. The old one "switched off" their service before the new one's could be listed in the master .com domain tables. They're now with MojoHost (Moniker). All fixed now.
Ahhhwondered what the issue was, got worried after last year....
I am glad the forum is back. Missed my new friends.
Hey Guys,
Sorry for the downtime we had. There was in fact an issue with our DNS (Domain Name System) servers that took much longer to resolve than we had hoped.
All is well now and we really appreciate your patience!
-CT
This might help others in a similar situation
As of 17:35 PST:
The earlier certificate issues appear to have been fixed.
Still having issues using Cox Communications as ISP. URL has not yet filtered down to Cox's DNS environment. Able to use twlltin's work around with a 32bit dotted IP address. ( https://199.182.104.123/forum/ ). That results in Cox intercepting the request and responding that it crosses back to a non-existant URL. They do have a "Proceed Anyway" button on that page. Clicking that leads to the Aneros Forum where one can log in.
Clicking on takes one to an HTML page (no formatting or other evidence of CSS)... about3/4 of the way down that page is a link to "CHAT NOW" Clicking on that html link leads to the usual page and one is in Chat.
Am hoping that Cox's DNS servers and security monitors are updated soon.
rook
Was getting worried! cant use my aneros coz of my mishap witn progasm ice and then cant have my forum fix either. So glad we are back and running. :-SS
@rook: That "proceed anyway" page is a function of your browser (Chrome), not your ISP (Cox). It's caused by the URL you entered not matching the hostname in the SSL certificate of the site.
I must have missed the down time, as I never noticed any problems.
Taffy
What a relief we are back on line! I dont understand1% of Twlltin's info but very glad he had the technical insight to get things moving.
I didn't do anything. I did alert the people at Aneros to the problem. But (and it's a big butt) the problem would have resolved (sic) itself within a day or two anyway.