Austin, we seem to have a problem here.

xilman · 2003-08-06, 15:14

Richard Wackerbarth's NFSNET servers in Austin Texas seem to have fallen off the net. Don and I have been investigating and we are fairly sure that he is having connectivity problems with his ISP.

Unfortunately, the nfsnet.org DNS domain is driven from there and name resolution is not working properly. Not only is www.nfsnet.org (apparently) not working, neither are the mailing lists nor, I guess his task allocation and receiver services.

I run an alternative DNS resolver at 213.199.145.253 and that's still working fine. Some of you may be able to use this address for your resolver. I do not know why the NFSNET.ORG registration does not give this as a resolver for the domain and I will ask Richard to review the situation when he is contactable again.

The webserver itself is also running happily. Until the DNS is fixed, or you use my resolver, the only easy way to verify this claim is to go to http://66.51.115.16/

We're doing all we can at the moment to mitigate thesituation but there are limits to what we can do at a range of several thousand miles for an organization that is incommunicado.

Paul

Wacky · 2003-08-06, 17:42

I apologize for the disruption. My servers were all happily running, but could not connect to the outside world.

I am happy to report that my connectivity has returned, at least temporarily. We'll see if it stays up of if TPC breaks it again.

This outage has exposed a number of problems with our DNS.
One of the alternate servers is down and another was rebuilt without the proper entries.

It also appears that Paul's DNS was either lost, or never properly activated in the .org name servers. I have submitted the change for this and hopefully it will propagate before it's access becomes critical again.

Please check your sievers. They should all be happily running again by now.

Richard

2003-08-06, 15:14	#1
xilman Bamboozled! "𒉺𒌌𒇷𒆷𒀭" May 2003 Down not across 10,753 Posts	Austin, we seem to have a problem here. Richard Wackerbarth's NFSNET servers in Austin Texas seem to have fallen off the net. Don and I have been investigating and we are fairly sure that he is having connectivity problems with his ISP. Unfortunately, the nfsnet.org DNS domain is driven from there and name resolution is not working properly. Not only is www.nfsnet.org (apparently) not working, neither are the mailing lists nor, I guess his task allocation and receiver services. I run an alternative DNS resolver at 213.199.145.253 and that's still working fine. Some of you may be able to use this address for your resolver. I do not know why the NFSNET.ORG registration does not give this as a resolver for the domain and I will ask Richard to review the situation when he is contactable again. The webserver itself is also running happily. Until the DNS is fixed, or you use my resolver, the only easy way to verify this claim is to go to http://66.51.115.16/ We're doing all we can at the moment to mitigate thesituation but there are limits to what we can do at a range of several thousand miles for an organization that is incommunicado. Paul

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
What is the problem here?	didgogns	Msieve	1	2016-11-15 03:31
problem 2.4	MattcAnderson	Puzzles	4	2014-08-21 04:40
problem I have	science_man_88	Miscellaneous Math	2	2010-10-10 16:36
51 problem	Neves	Miscellaneous Math	5	2004-02-10 22:59
51 problem	Neves	Puzzles	15	2004-02-05 23:11

2003-08-06, 17:42	#2
Wacky Jun 2003 The Texas Hill Country 2101₈ Posts	I apologize for the disruption. My servers were all happily running, but could not connect to the outside world. I am happy to report that my connectivity has returned, at least temporarily. We'll see if it stays up of if TPC breaks it again. This outage has exposed a number of problems with our DNS. One of the alternate servers is down and another was rebuilt without the proper entries. It also appears that Paul's DNS was either lost, or never properly activated in the .org name servers. I have submitted the change for this and hopefully it will propagate before it's access becomes critical again. Please check your sievers. They should all be happily running again by now. Richard