The Passport Payment (2000)
web.archive.org
The Passport Payment (2000)
1–10 of 55 posts
Re: The Passport Payment (2000)
#2According to the story, it took somewhere between 13 and 19 hours for passport.com to resolve properly after he renewed it for Microsoft. Is that normally how long it takes to reactivate a domain name that has gone into a renewal grace period, or was something different back then?
Perhaps the NXDOMAIN response was cached by ISPs for an especially long time because it was such a frequently visited hostname?
Re: The Passport Payment (2000)
#3According to the story, it took somewhere between 13 and 19 hours for passport.com to resolve properly after he renewed it for Microsoft. Is that normally how long it takes to reactivate a domain name that has gone into a renewal grace period, or was something different back then? Perhaps the NXDOMAIN response was cached by ISPs for an especially long time because it was such a frequently visited hostname?
NXDOMAIN is often cached for much longer because it's assumed not to change soon. Sometimes, as in this case, that's a wrong assumption.
Re: The Passport Payment (2000)
#4> in addition to a new copy of Visual Studio 6.0 (which I need to compile and run the decss program to decode my DVD's so that I can play them under Linux)
Why would you need VS6 to compile a program for Linux?
Re: The Passport Payment (2000)
#5> in addition to a new copy of Visual Studio 6.0 (which I need to compile and run the decss program to decode my DVD's so that I can play them under Linux) Why would you need VS6 to compile a program for Linux?
DeCSS was a windows-only program back in those days.
Re: The Passport Payment (2000)
#6This happened in 1999/2000, maybe someone could add (2000) to the title?
Re: The Passport Payment (2000)
#7According to the story, it took somewhere between 13 and 19 hours for passport.com to resolve properly after he renewed it for Microsoft. Is that normally how long it takes to reactivate a domain name that has gone into a renewal grace period, or was something different back then? Perhaps the NXDOMAIN response was cached by ISPs for an especially long time because it was such a frequently visited hostname?
It used to be that nameserver changes with TLDs were measured in days, not minutes. Even today some TLDs continue to operate this way.
Re: The Passport Payment (2000)
#8According to the story, it took somewhere between 13 and 19 hours for passport.com to resolve properly after he renewed it for Microsoft. Is that normally how long it takes to reactivate a domain name that has gone into a renewal grace period, or was something different back then? Perhaps the NXDOMAIN response was cached by ISPs for an especially long time because it was such a frequently visited hostname?
It used to be that nameserver changes with TLDs were measured in days, not minutes. Even today some TLDs continue to operate this way.
What are reasonable timeframe expectations for nameserver changes now?
Re: The Passport Payment (2000)
#9Could you imagine doing this today? You'd probably get lawyers making you sign agreements saying your payment of the domain renewal is not a ownership interest in the domain and threatening to take you to court for renewing their domain.
Re: The Passport Payment (2000)
#10> in addition to a new copy of Visual Studio 6.0 (which I need to compile and run the decss program to decode my DVD's so that I can play them under Linux) Why would you need VS6 to compile a program for Linux?
He was compiling a Windows program to decode his DVDs so that he could play them on Linux