Mr Buck,

Thank you for that, I will now start investigating my firewall which has not changed since I built the computer a year ago, and which looked after the last version of BOINC successfully and which, by the way, I enabled for this version.

I attach the latest set of messages which as you see inform me that in a week or so the system will try to reconnect for me, any system that increments by such an amount caused by an amateur like me pushing buttons too often must be missing a certain quality control element and systems check.

I now ask the fundamental question, is seti@home still interested in getting free computation and electricity from its 5 million subscribers or has it now gone the way of the large multinationals ie I am now so big and important that the small individual customer is merely a pain in the butt!!

21/06/2005 16:41:02||Starting BOINC client version 4.45 for windows_intelx86
21/06/2005 16:41:02||Data directory: C:\Program Files\BOINC
21/06/2005 16:41:02|SETI@home|Computer ID: 453566; location: home; project prefs: default
21/06/2005 16:41:02||General prefs: from SETI@home (last modified 2005-06-19 10:28:34)
21/06/2005 16:41:02||General prefs: no separate prefs for home; using your defaults
21/06/2005 16:41:02||Remote control not allowed; using loopback address
21/06/2005 16:41:02||Insufficient work; requesting more
21/06/2005 16:41:39|SETI@home|Master file fetch failed
21/06/2005 16:41:40|SETI@home|Deferring communication with project for 1 hours, 31 minutes, and 34 seconds
21/06/2005 17:41:02||Insufficient work; requesting more
21/06/2005 17:41:40|SETI@home|Deferring communication with project for 31 minutes and 34 seconds
21/06/2005 18:03:08||request_reschedule_cpus: project op
21/06/2005 18:03:30|SETI@home|Master file fetch failed
21/06/2005 18:03:31|SETI@home|Deferring communication with project for 4 hours, 26 minutes, and 3 seconds
21/06/2005 18:05:47||request_reschedule_cpus: project op
21/06/2005 18:05:48||request_reschedule_cpus: project op
21/06/2005 18:05:49||request_reschedule_cpus: project op
21/06/2005 18:05:49||request_reschedule_cpus: project op
21/06/2005 18:06:09|SETI@home|Master file fetch failed
21/06/2005 18:06:10||request_reschedule_cpus: project op
21/06/2005 18:06:11||request_reschedule_cpus: project op
21/06/2005 18:06:31|SETI@home|Master file fetch failed
21/06/2005 18:06:33|SETI@home|Deferring communication with project for 20 hours, 24 minutes, and 29 seconds
21/06/2005 18:09:35||request_reschedule_cpus: project op
21/06/2005 18:09:58|SETI@home|Master file fetch failed
21/06/2005 18:09:59|SETI@home|Deferring communication with project for 3 hours, 41 minutes, and 55 seconds
21/06/2005 18:41:03||Insufficient work; requesting more
21/06/2005 19:09:59|SETI@home|Deferring communication with project for 2 hours, 41 minutes, and 55 seconds
21/06/2005 19:41:03||Insufficient work; requesting more
21/06/2005 20:10:00|SETI@home|Deferring communication with project for 1 hours, 41 minutes, and 54 seconds
21/06/2005 20:41:04||Insufficient work; requesting more
21/06/2005 21:10:01|SETI@home|Deferring communication with project for 41 minutes and 54 seconds
21/06/2005 21:41:04||Insufficient work; requesting more
21/06/2005 21:52:17|SETI@home|Master file fetch failed
21/06/2005 21:52:18|SETI@home|Deferring communication with project for 1 weeks, 2 days, 13 hours, 47 minutes, and 17 seconds
21/06/2005 22:41:05||Insufficient work; requesting more
21/06/2005 22:52:18|SETI@home|Deferring communication with project for 1 weeks, 2 days, 12 hours, 47 minutes, and 16 seconds
21/06/2005 23:41:05||Insufficient work; requesting more
21/06/2005 23:52:19|SETI@home|Deferring communication with project for 1 weeks, 2 days, 11 hours, 47 minutes, and 16 seconds

---

Pierre, Please check your firewall "internet applications" and see if BOTH Boinc.exe AND Boincmgr.exe have full access?

does this help?

tony

Tony I did that, and I even turned windows firewall of completeley.....

6/22/2005 9:02:06 AM|SETI@home|Computation for result 19se03aa.5812.15440.147152.63_0 finished
6/22/2005 9:02:06 AM|SETI@home|Starting result 19se03aa.5812.15440.147152.61_2 using setiathome version 4.09
6/22/2005 9:02:12 AM|SETI@home|Started upload of 19se03aa.5812.15440.147152.63_0_0
6/22/2005 9:02:21 AM|SETI@home|Finished upload of 19se03aa.5812.15440.147152.63_0_0
6/22/2005 9:02:21 AM|SETI@home|Throughput 5048 bytes/sec
6/22/2005 9:02:22 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/22/2005 9:02:22 AM|SETI@home|Requesting 0 seconds of work, returning 58 results
6/22/2005 9:02:31 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/22/2005 9:02:31 AM|SETI@home|No schedulers responded
6/22/2005 9:02:32 AM|SETI@home|Deferring communication with project for 59 seconds
6/22/2005 9:03:31 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/22/2005 9:03:31 AM|SETI@home|Requesting 0 seconds of work, returning 58 results
6/22/2005 9:03:51 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/22/2005 9:03:51 AM|SETI@home|No schedulers responded
6/22/2005 9:03:52 AM|SETI@home|Deferring communication with project for 59 seconds
6/22/2005 9:04:52 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/22/2005 9:04:52 AM|SETI@home|Requesting 0 seconds of work, returning 58 results
6/22/2005 9:05:08 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/22/2005 9:05:08 AM|SETI@home|No schedulers responded
6/22/2005 9:05:09 AM|SETI@home|Deferring communication with project for 59 seconds
6/22/2005 9:06:09 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/22/2005 9:06:09 AM|SETI@home|Requesting 0 seconds of work, returning 58 results
6/22/2005 9:06:24 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/22/2005 9:06:24 AM|SETI@home|No schedulers responded
6/22/2005 9:06:25 AM|SETI@home|Deferring communication with project for 59 seconds
6/22/2005 9:07:25 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/22/2005 9:07:25 AM|SETI@home|Requesting 0 seconds of work, returning 58 results
6/22/2005 9:07:43 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/22/2005 9:07:43 AM|SETI@home|No schedulers responded
6/22/2005 9:07:44 AM|SETI@home|Deferring communication with project for 59 seconds
6/22/2005 9:08:43 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/22/2005 9:08:43 AM|SETI@home|Requesting 0 seconds of work, returning 58 results
6/22/2005 9:08:59 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/22/2005 9:08:59 AM|SETI@home|No schedulers responded
6/22/2005 9:09:00 AM|SETI@home|Deferring communication with project for 59 seconds
6/22/2005 9:10:00 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/22/2005 9:10:00 AM|SETI@home|Requesting 0 seconds of work, returning 58 results
6/22/2005 9:10:16 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/22/2005 9:10:16 AM|SETI@home|No schedulers responded
6/22/2005 9:10:17 AM|SETI@home|Deferring communication with project for 59 seconds
6/22/2005 9:11:16 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/22/2005 9:11:16 AM|SETI@home|Requesting 0 seconds of work, returning 58 results
6/22/2005 9:11:32 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/22/2005 9:11:32 AM|SETI@home|No schedulers responded
6/22/2005 9:11:33 AM|SETI@home|Deferring communication with project for 59 seconds
6/22/2005 9:12:33 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/22/2005 9:12:33 AM|SETI@home|Requesting 0 seconds of work, returning 58 results
6/22/2005 9:12:49 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/22/2005 9:12:49 AM|SETI@home|No schedulers responded
6/22/2005 9:12:50 AM|SETI@home|Deferring communication with project for 59 seconds
6/22/2005 9:13:26 AM||May run out of work in 10.00 days; requesting more
6/22/2005 9:13:49 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/22/2005 9:13:49 AM|SETI@home|Requesting 0 seconds of work, returning 58 results
6/22/2005 9:14:05 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/22/2005 9:14:05 AM|SETI@home|No schedulers responded
6/22/2005 9:14:06 AM|SETI@home|Deferring communication with project for 59 seconds
6/22/2005 9:15:05 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/22/2005 9:15:05 AM|SETI@home|Requesting 0 seconds of work, returning 58 results
6/22/2005 9:15:25 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/22/2005 9:15:25 AM|SETI@home|No schedulers responded
6/22/2005 9:15:26 AM|SETI@home|Deferring communication with project for 59 seconds
6/22/2005 9:16:25 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/22/2005 9:16:25 AM|SETI@home|Requesting 0 seconds of work, returning 58 results
6/22/2005 9:16:43 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/22/2005 9:16:43 AM|SETI@home|No schedulers responded
6/22/2005 9:16:44 AM|SETI@home|Deferring communication with project for 59 seconds
6/22/2005 9:17:43 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/22/2005 9:17:43 AM|SETI@home|Requesting 0 seconds of work, returning 58 results
6/22/2005 9:17:59 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/22/2005 9:17:59 AM|SETI@home|No schedulers responded
6/22/2005 9:18:00 AM|SETI@home|Deferring communication with project for 59 seconds
6/22/2005 9:19:00 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/22/2005 9:19:00 AM|SETI@home|Requesting 0 seconds of work, returning 58 results
6/22/2005 9:19:16 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/22/2005 9:19:16 AM|SETI@home|No schedulers responded
6/22/2005 9:19:17 AM|SETI@home|Deferring communication with project for 59 seconds
6/22/2005 9:20:16 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/22/2005 9:20:16 AM|SETI@home|Requesting 0 seconds of work, returning 58 results
6/22/2005 9:20:32 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/22/2005 9:20:32 AM|SETI@home|No schedulers responded
6/22/2005 9:20:33 AM|SETI@home|Deferring communication with project for 59 seconds
6/22/2005 9:21:33 AM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
6/22/2005 9:21:33 AM|SETI@home|Requesting 0 seconds of work, returning 58 results
6/22/2005 9:21:52 AM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed
6/22/2005 9:21:52 AM|SETI@home|No schedulers responded
6/22/2005 9:21:53 AM|SETI@home|Deferring communication with project for 59 seconds

---

Mr Buck,

Thank you for that, I will now start investigating my firewall which has not changed since I built the computer a year ago, and which looked after the last version of BOINC successfully and which, by the way, I enabled for this version.

You are welcome.

And I must honestly say that I do not understand what is happening. And I know how difficult it is to troubleshoot problems like this. All I can do is point at things that have been the problem in the past. The only time I have had problems such as this have been when the servers themselves are down.

Though I did have a problem with Predictor@Home this morning on the PowerMac where it was indicating that it could not contact the Scheduler. Other of my systems could ... in my case, a restart of BOINC cleared up my problem (though I have not looked in the logs yet to see what might have been my problem). More annoying is I seem to have "lost" two work units...

So, I am at a loss ... and obviously do not understand what is happening ... if you do figure it out, let me know and I will try to add it to the Wiki for the future ... all I can do ...

One thing though, I don't understand why it says you will run out of work in 10 days ...

---

i understand that SETI is your main love, as it is for me as well, but i would want to try another thing:
if you are connected to another project, is it working? if no other projects, join one to see if you can obtain work.

as Paul stated, Master file fetch failed is generally not being able to connect to the server; i get it sometimes with Pirates (generally when the server is offline). when it is my connection i generally get the standard 113 error.

as for Mr Keene, you are not getting a response from the server, again, i would like to see what happens with a different project so that we will know if it is a SETI issue or a BOINC/pc issue

happy crunching (assuming you can ;)

Micah

---

S@h Berkeley's Staff Friends Club

Tony I did that, and I even turned windows firewall of completeley.....

Joseph, you have a different issue from Pierre. Pierre can't even get past his router/modem to the internet. You are reaching the internet and contacting Seti, but they aren't responding to your request. Karthwyne is asking you to see if you can connect to the scheduler of other projects. Are you attached to more than one project?

tony

I have been unable to send back completed work units or get new one for approximately 1 1/2 weeks now, is there still a problem with wanadoo.fr? I am using a proxie 57.67.8.114 on port 80.

Anyone wanna help Pierre out here. This was his original question (first post on this thread). I just looked at it and I don't use Proxies so I can't Verify that the proxy is correct. However, I think your PORT is wrong. Seti Classic and Seti/Boinc use different ports. On my windows puter, Boincmgr is using port 1043 and boinc.exe is using port 1044. port 80 was used for Classic.

anyone with more knowledge, please jump in here.

tony

Well he might start looking at the nic card, cable or router. For whats it is worth I pinged the proxy and had a good connection most of the way one was in the mid 300s and destination was unreachable......

---

Semper Eadem
So long Paul, it has been a hell of a ride.

Park your ego's, fire up the computers, Science YES, Credits No.

I am not sure of the cause of Pierre and The Gas Giant's problem. But it would be interesting to see what is in the DNS cache on the systems affected.

On Windows try using ipconfig to view the DNS cache. Open a command window e.g. press start, select run, enter

cmd

press the ok button.

In the command window type

ipconfig /displaydns | more

the | more will pause at each screen of data, scroll though (press the space bar) looking for setiboinc.ssl.berkeley.edu and then make a note of what IP address is shown against the A (host) record.

It would be worth posting this to see what IP address your system is trying to contact the scheduler at.

---

I am using a proxie 57.67.8.114 on port 80.

Are you sure that proxy server is right? I believe the proxy servers used in classic are NOT used in BOINC. I tried pinging that IP number and I can't. Shouldn't I be able to? Have you tried any of these proxy servers?

http://setiweb.ssl.berkeley.edu/forum_thread.php?id=13867#100406

---

Help and BOINC documentation is available here.

Tony I did that, and I even turned windows firewall of completeley.....

Joseph, you have a different issue from Pierre. Pierre can't even get past his router/modem to the internet. You are reaching the internet and contacting Seti, but they aren't responding to your request. Karthwyne is asking you to see if you can connect to the scheduler of other projects. Are you attached to more than one project?

tony

I beleive the two are the same. Master File Fetch and No Scheduler Responded are both caused by network outages between the client and servers at the project. Just different servers.

---

BOINC WIKI

I am not 100% sure about this but has anyone tried opening a command prompt box and running "ipconfig /flushdns" without the quotes? Seems like I read somewhere with the same problem and this resolved it.

---

Boinc....Boinc....Boinc....Boinc....

I am not 100% sure about this but has anyone tried opening a command prompt box and running "ipconfig /flushdns" without the quotes? Seems like I read somewhere with the same problem and this resolved it.

Hi,

just for a reference - for me everything is ok and working. My entry reads (ipconfig /displaydns):

setiboinc.ssl.berkeley.edu
----------------------------------------
Eintragsname..... : setiboinc.ssl.berkeley.edu
Eintragstyp..... : 1
Gültigkeitsdauer...: 1520
Datenlänge...... : 4
Abschnitt...... : Antwort
(Host-)A-Eintrag...: 66.28.250.124

Femue

I beleive the two are the same. Master File Fetch and No Scheduler Responded are both caused by network outages between the client and servers at the project. Just different servers.

You are correct as far as I have been able to figure out looking at the error logs.

Master file fetch is pulling the Project Master URL, which for most projects is the index page of the web site. Embedded within that is a comment that has the scheduler's address.

The embedded linelooks like:

<scheduler>http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi</scheduler>

---

I beleive the two are the same. Master File Fetch and No Scheduler Responded are both caused by network outages between the client and servers at the project. Just different servers.

John I get that message when I'm not signed on, and projects try to update:

6/22/2005 3:26:56 PM|LHC@home|Couldn't read master page for LHC@home: error -113
6/22/2005 3:26:56 PM|LHC@home|Master file fetch failed

I see them all the time. So are you saying that trying to connect via "proxie 57.67.8.114 on port 80" should be working? If, so then what's the next thing they (Paul, Pierre, and Joseph) should do?

I am not 100% sure about this but has anyone tried opening a command prompt box and running "ipconfig /flushdns" without the quotes? Seems like I read somewhere with the same problem and this resolved it.

Hi,

just for a reference - for me everything is ok and working. My entry reads (ipconfig /displaydns):

setiboinc.ssl.berkeley.edu
----------------------------------------
Eintragsname..... : setiboinc.ssl.berkeley.edu
Eintragstyp..... : 1
Gültigkeitsdauer...: 1520
Datenlänge...... : 4
Abschnitt...... : Antwort
(Host-)A-Eintrag...: 66.28.250.124

Femue

We would need one of the experts to comment on the IP address of the scheduler but on my system I have a different one: setiboinc.ssl.berkeley.edu points to 66.28.250.125

Are there multiple schedulers: 66.28.250.124 and 66.28.250.125 ?

---

Hi, i think so. So at least these two should work:

66.28.250.124
66.28.250.125

Good night
Femue

Windows (2k and beyond) ships with a pretty good network diagnostics tool. Just not installed by default. I'd suggest installing it, then running it and see what it says.

Using your original Windows install CD, look in the /support/tools folder, and run setup.exe. I always specify a "complete" installation, to make sure I get all the tools. Only takes up around 11M disk space.

To run, open a dos box and change to a directory that isn't full of files. Then run netdiag. I usually enter:

md \test
cd \test
netdiag
notepad netdiag.log

You'll see a summary of it running on the screen, with the details written to the file NetDiag.log. That last command opens the log in notepad, so you can see the results.

I found it best to run netdiag when the network is working, then rename the file to something else. Then when theres a problem I run netdiag again and compare the current results to the one that worked.

Well guess what, I tried all of the DNS suggestions none of them worked, I redid all of the firewall enablers (its NIS 2003) that didn't change anything. Then I finally tried the suggestion of get another project to see if its me or SETI, well my old climate prediction bit worked then I tried seti and it started to download, but all of the downloads keep failing, here are but a few of the messages: So we are partially there now what? And whats 'better banner'? I'm away for a few days catch you all later thanks again for all the help and suggestions.

23/06/2005 00:30:12|SETI@home|Backing off 1 minutes and 0 seconds on download of file 31ja04aa.19933.546.934640.161
23/06/2005 00:30:13|SETI@home|Started download of better_banner.jpg
23/06/2005 00:30:26|SETI@home|Finished download of 31ja04aa.19933.546.934640.173
23/06/2005 00:30:26|SETI@home|Throughput 20187 bytes/sec
23/06/2005 00:30:35|SETI@home|Temporarily failed download of better_banner.jpg: 500
23/06/2005 00:30:35|SETI@home|Backing off 1 minutes and 0 seconds on download of file better_banner.jpg
23/06/2005 00:30:51|SETI@home|Started download of 31ja04aa.19933.546.934640.165
23/06/2005 00:31:07|SETI@home|Started download of setiathome_4.18_windows_intelx86.pdb
23/06/2005 00:31:07|SETI@home|Unrecoverable error for result 31ja04aa.19933.546.934640.165_3 (app_version download error: couldn't get input files: setiathome_4.18_windows_intelx86.pdb -200 )
23/06/2005 00:31:07|SETI@home|Unrecoverable error for result 31ja04aa.19933.546.934640.161_2 (app_version download error: couldn't get input files: setiathome_4.18_windows_intelx86.pdb -200 )
23/06/2005 00:31:07|SETI@home|Unrecoverable error for result 31ja04aa.19933.546.934640.173_0 (app_version download error: couldn't get input files: setiathome_4.18_windows_intelx86.pdb -200 )
23/06/2005 00:31:08|SETI@home|Deferring communication with project for 59 seconds
23/06/2005 00:31:13|SETI@home|Temporarily failed download of 31ja04aa.19933.546.934640.165: 500
23/06/2005 00:31:13|SETI@home|Backing off 2 minutes and 22 seconds on download of file 31ja04aa.19933.546.934640.165
23/06/2005 00:31:13|SETI@home|Started download of 31ja04aa.19933.546.934640.161
23/06/2005 00:31:29|SETI@home|Temporarily failed download of setiathome_4.18_windows_intelx86.pdb: 500
23/06/2005 00:31:29|SETI@home|Backing off 2 minutes and 18 seconds on download of file setiathome_4.18_windows_intelx86.pdb
23/06/2005 00:31:34|SETI@home|Temporarily failed download of 31ja04aa.19933.546.934640.161: 500
23/06/2005 00:31:34|SETI@home|Backing off 1 minutes and 40 seconds on download of file 31ja04aa.19933.546.934640.161
23/06/2005 00:31:35|SETI@home|Started download of better_banner.jpg
23/06/2005 00:31:57|SETI@home|Temporarily failed download of better_banner.jpg: 500
23/06/2005 00:31:57|SETI@home|Backing off 6 minutes and 21 seconds on download of file better_banner.jpg
23/06/2005 00:32:08|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
23/06/2005 00:32:08|SETI@home|Requesting 0 seconds of work, returning 3 results
23/06/2005 00:32:10|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded

---

Here is the DNS data that you wanted if it helps, I only got this after I had tried the addition of climate prediction into BOINC

setiboincdata.ssl.berkeley.edu
----------------------------------------
Record Name . . . . . : setiboincdata.ssl.berkeley.edu
Record Type . . . . . : 1
Time To Live . . . . : 84197
Data Length . . . . . : 4
Section . . . . . . . : Answer
A (Host) Record . . . : 66.28.250.125

---