Text 11564, 87 rader
Skriven 2010-10-30 13:29:45 av Roy Witt (1:387/22)
  Kommentar till text 11493 av Michiel van der Vlist (2:280/5555)
Ärende: N'other one evicted from dyndns?
========================================
27 Oct 10 13:36, Michiel van der Vlist wrote to Robert Bashe:

 MvdV> Hello Robert,

 MvdV> On Tuesday October 26 2010 11:30, you wrote to me:

 RB>>>> but sometimes "unknown host" too.

 MV>>> Which defenitely indicates a DNS problem.

 RB>> Maybe his router didn't update the DNS. Shit happens.

 MvdV> It seems it didn't. But... as I tried to tell you several times, a
 MvdV> mere failure to update does NOT explain that particular error.

Yes it does.

 MvdV> It is like telling your secretary to call mr. Brown to see if he is
 MvdV> at home. She asks for the number and you tell her to look it up in
 MvdV> the phone book. She comes back with "mr. Brown is not in the phone
 MvdV> book". Does that mean mr. Brown's phone is out of order? No, of
 MvdV> course not. It just means he is not in the phone book. If you knew
 MvdV> his number, you could probably still call him.

That is, IF his phone number were still the same. If it isn't, you get a
total stranger. If it's been re-assigned to Mr Black, then it is no longer
Mr Brown's number.

 MvdV> This is what happens when you try to ping rustysbbs.dyndns.org. In
 MvdV> order to execute the ping, Ping needs the IP number.

No, ping gets the IP from DYNDNS. If you knew his IP, you could prove that
to yourself by pinging it directly.

 MvdV> So Ping attempts to resolve the IP number for rustysbbs.dyndns.org
 MvdV> by a DNS query.

From a DNS provider who doens't have it (because the IP is down).

 MvdV> IOW. it looks it up in the "phone book".

In the DYNDNS phone book. If it's not listed, there is no IP.

 MvdV> Now when it was merely a question of an overdue DNS uodate, that
 MvdV> is, the IP number has changed, but de DNS system has not been told
 MvdV> yet, it would return the old number. But that is not the response;
 MvdV> the response is: it is not there.

Because it wasn't updated. Once the old IP is re-assigned and rusty's
system gets a new one, it isn't necessarily in the phone book yet because
it hasn't been listed.

 MvdV> Ergo conclusio: dyndns has removed it.

That is automatic. i.e. no one has removed it, rusty just hasn't told
DYNDNS what it is.

 MvdV> My guess is that they nuked the account for the client's failure to
 MvdV> take some action.

I'll bet Rusty can access his account at the DYNDNS website. They don't
remove accounts for nothing.

 MvdV> This IS what they announced: to discontinue "inactive" accounts.
 MvdV> When Russell's system has been off-line for some time and he has
 MvdV> taken no positive action, this is a plausible explanation.

But his 'account' there still exists.

 MvdV> Call that speculation if you want, but this is perfectly valid as a
 MvdV> scientific method.

Actually it shows us that you don't know exactly how DYNDNS works. You've
taken the Pirates word for it that its a corrupt entity, when the corrupt
entity is the very person who you stick your neck out for.

 MvdV> Observe a fact; do some deduction and then formulate a theory to
 MvdV> explain the observed fact. Then wait for counter evidence to
 MvdV> emerge.

Knowing how the DYNDNS system works, I don't have to wait, I already know.

                R\%/itt

 "Peltier was responsible for the close range execution of FBI agents..."
--- Twit(t) Filter v2.1 (C) 2000-10
 * Origin: SATX Alamo Area Net * South * Texas, USA * (1:387/22)