C:\>tracert lunatics.kwsn.net
Unable to resolve target system name lunatics.kwsn.net.

Oops! Google Chrome could not find lunatics.kwsn.net

Try reloading: lunatics.­kwsn.­net

:/

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

No problems here.

---

With each crime and every kindness we birth our future.

No problems here.

Hm, but I'm cut still. Ok, will try later, thanks for checking.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

No problems here.

Nor here.

"Unable to resolve" is a DNS problem, probably quite local to your computer/network. Try a different DNS server, or take it up with your ISP.

I've seen it twice since yesterday, no Lunatics when I refreshed, But there when I hit my bookmarked link.

Claggy

Lunatics is still OK, but BOINC has gone down instead.

http://www.downforeveryoneorjustme.com/boinc.berkeley.edu

Lunatics is still OK, but BOINC has gone down instead.

http://www.downforeveryoneorjustme.com/boinc.berkeley.edu

For me both sides are dead, even according to downforeveryoneorjustme.com!

---

Aloha, Uli

I was also cut off from lunatics.kwsn.net, the DNS servers for two different ISPs were not able to resolve it and at the time I checked yesterday downforeveryoneorjustme.com was also unable to. However, using a Google public DNS did work:

>nslookup lunatics.kwsn.net 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8

Non-authoritative answer:
Name: lunatics.kwsn.net
Address: 63.247.72.178

I already had the IP address in my hosts file but it was commented out. Enabling it restored my access to the site.

                                                                   Joe

I was also cut off from lunatics.kwsn.net, the DNS servers for two different ISPs were not able to resolve it and at the time I checked yesterday downforeveryoneorjustme.com was also unable to. However, using a Google public DNS did work:

>nslookup lunatics.kwsn.net 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8

Non-authoritative answer:
Name: lunatics.kwsn.net
Address: 63.247.72.178

I already had the IP address in my hosts file but it was commented out. Enabling it restored my access to the site.

                                                                   Joe

I had to change one of my DNS servers a couple of days ago as I was unable to load any sites except for a couple that I had in cache. Once I added back in the google DNS, all site worked just fine again.

---

Name: lunatics.kwsn.net
Address: 63.247.72.178

I already had the IP address in my hosts file but it was commented out. Enabling it restored my access to the site.

                                                                   Joe

Thanks for hint! I'm able to access from one location, but only from some of PCs, others showed same DNS error as PCs in another location.
Will see what new day brings, but havind IP address in hosts file is good idea anyway.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

Seemingly, it is due to the problem on the registered DNS data. The root DNS servers say that the name servers of kwsn.net are ns[1-3].2asc.com, but which don't exist.

$ nslookup -q=any kwsn.net. g.gtld-servers.net.
Server:		g.gtld-servers.net.
Address:	192.42.93.30#53

Non-authoritative answer:
*** Can't find kwsn.net.: No answer

Authoritative answers can be found from:
kwsn.net	nameserver = ns2.2asc.com.
kwsn.net	nameserver = ns1.2asc.com.
kwsn.net	nameserver = ns3.2asc.com.
ns2.2asc.com	internet address = 98.191.27.16
ns1.2asc.com	internet address = 63.146.4.70
ns3.2asc.com	internet address = 66.77.7.77

$ nslookup -q=ns 2asc.com. a.gtld-servers.net.
Server:		a.gtld-servers.net.
Address:	192.5.6.30#53

Non-authoritative answer:
*** Can't find 2asc.com.: No answer

Authoritative answers can be found from:
2asc.com	nameserver = ns1.americansystems.com.
2asc.com	nameserver = ns2.americansystems.com.
2asc.com	nameserver = ns3.americansystems.com.
ns1.americansystems.com	internet address = 216.200.164.135
ns2.americansystems.com	internet address = 98.191.27.16
ns3.americansystems.com	internet address = 66.77.7.77

$ nslookup -q=any ns2.2asc.com. 98.191.27.16
Server:		98.191.27.16
Address:	98.191.27.16#53

** server can't find ns2.2asc.com.: NXDOMAIN

I don't know how Google's server keeps valid data, but I afraid it may expire in a week.
Hoping the problem resolved by then.

$ nslookup -q=any kwsn.net. 8.8.8.8
Server:		8.8.8.8
Address:	8.8.8.8#53

Non-authoritative answer:
Name:	kwsn.net
Address: 63.247.72.178
kwsn.net	nameserver = ns2.americansystems.com.
kwsn.net	nameserver = ns1.americansystems.com.
kwsn.net	nameserver = ns3.americansystems.com.
kwsn.net
	origin = ns1.americansystems.com
	...
	expire = 604800
	...

Same procedure as last year?

Anybody told Tobias (?) yet? Remember Lunatics is just a part of kwsn - any queries as to why there is a problem need to be addressed by the KWSN Admin - and I think he hasn't been very active for quite a while. The other kwsn sites are down for me as well, so it is a global KWSN problem.
Nope this isn;t my two cents, it's just half a penny.

---

A person who won't read has no advantage over one who can't read. (Mark Twain)

Sent Toby an email.

Claggy

Not quite sure what is going on. I got some DNS errors at work today but looking now things seem to be working for me. I'm wondering if there is some weird routing problem that is preventing some parts of the internet from talking to our name servers or something.

---

A member of The Knights Who Say NI!
For rankings, history graphs and more, check out:
My BOINC stats site

After further review it seems more likely that something has changed with our name server setup and some ISPs are just caching the last known value longer than they technically should. Queries have been sent.

---

A member of The Knights Who Say NI!
For rankings, history graphs and more, check out:
My BOINC stats site

After five days same host still can't resolve lunatics host name :(

Adding direct map to hosts fixed issue.

---

SETI apps news
We're not gonna fight them. We're gonna transcend them.

It should actually be working again now. There was indeed a change in the DNS setup. We need to update the name servers but the old ones were put back in place until we can get that updated.

---

A member of The Knights Who Say NI!
For rankings, history graphs and more, check out:
My BOINC stats site

I still can't reach lunatics.kwsn.net from my home and isup.me also reports it unreachable. Strangely i can access the site from my work in the same city! :?

---

Aloha, Uli

... but different ISPs and so normaly different DNS-servers.
I changed "my" DNS-server manualy to a different one than the provider sets up, because other services where much more performant. There are two helpful and simple tools for checking the speed of dnsresolving, DNSbench and namebench.

__W__

---

_______________________________________________________________________________

Just unbroken here now.
I could not reach it earlier today.

---

"Time is simply the mechanism that keeps everything from happening all at once."