Patrik Fältström via dns-operations writes:
> On 13 Dec 2020, at 5:26, Viktor Dukhovni wrote:
>
> > So my question to the list is, what can or should be done to help domain
> owners avoid a similar fate?
>
> As it is today: You use a registrar that ensure your domain name never
> expires.
Yea, put them on auto renew via a credit card and change credit cards or
the card expires. Now how many places was the old card used and it
might be a year before it comes around to bite us. And then accounting
doesn't know who used that card and who has access to that place to
change the card
* Lyle Giese:
> Yea, put them on auto renew via a credit card and change credit cards or
> the card expires. Now how many places was the old card used and it
> might be a year before it comes around to bite us. And then accounting
> doesn't know who used that card and who has access to that pl
Seems to me that the answer is simple: as a domain owner you should keep
an *inventory* of all your domain names along with anniversary dates,
and set reminders if needed.
The anniversary day normally will remain the same, only the year changes
after renewal. TLDs such as .nl/.be/.de etc are somewh
I'm glad to see this dialog. ICANN has some guidance intended to educate
domain owners re the various risks. See
https://www.icann.org/resources/pages/domain-name-need-to-know-2020-05-01-en
My *impression* is the most serious risks a domain owner faces for losing
control of the domain are either
> While one might just write this off as "operator error", putting the
> blame squarely on the domain owner, I wonder whether in part the problem
> is a result of lack of transparency around impending domain expiration.
Maybe, but why does it matter. It is exactly like certificates: you don't wait
--- Begin Message ---
Hi,
On 13/12/2020 05:26, Viktor Dukhovni wrote:
Yesterday I happened to notice that the "flexfilter.nl" domain went into
"quarantine" under .NL, with NXDomain returned by the parent. This
domain still had ~14.5k signed domains using its MX hosts, including
flexwebhosting.n
Once upon a time, Viktor Dukhovni said:
> While one might just write this off as "operator error", putting the
> blame squarely on the domain owner, I wonder whether in part the problem
> is a result of lack of transparency around impending domain expiration.
You can set to auto-renew, or you can
On Sun, Dec 13, 2020 at 01:03:12PM -0600, Chris Adams wrote:
> Once upon a time, Viktor Dukhovni said:
> > While one might just write this off as "operator error", putting the
> > blame squarely on the domain owner, I wonder whether in part the problem
> > is a result of lack of transparency arou
tangent, but you started it
> [1] IANAL, but this rather looks like a gross over-reaction to GDPR,
> with some registries and registrars continuing to provide usable
> contact details with no ill consequence. The practice even among
> European ccTLDs varies rather widely. It would sure be great
Hi,
I fully agree with Steve that domain names have a peculiar value. Perhaps
the purchase price has become too low?
If your domain is important to you, most registries offer a service to
protect your registration from all kinds of mistakes and attacks.
The name and exact details of this service
On Sun, Dec 13, 2020 at 11:09 AM Maarten Bosteels
wrote:
> I fully agree with Steve that domain names have a peculiar value. Perhaps
> the purchase price has become too low?
>
That feels like treating the wrong part of the problem chain. Loss of a
phone number can also cause significant business
In article
you write:
>My *impression* is the most serious risks a domain owner faces for losing
>control of the domain are either because the registration lapses, as is
>being discussed here, or because the domain is registered by someone else,
>e.g. the tech or admin contact, who then either le
On Sun, 13 Dec 2020, Randy Bush wrote:
i find this extremely frustrating. i realize that i am a dinosaur, but
i really want a usable response to a whois query. compare
I would just like to be able to publish whois information if I /choose/
to rather than, for instance, Hover's broken "whois
In article you write:
>On Sun, 13 Dec 2020, Randy Bush wrote:
>> i find this extremely frustrating. i realize that i am a dinosaur, but
>> i really want a usable response to a whois query. compare
>
>I would just like to be able to publish whois information if I /choose/
>to rather than, for in
On Sun, Dec 13, 2020 at 3:30 PM John Levine wrote:
> In article you write:
> >On Sun, 13 Dec 2020, Randy Bush wrote:
> >> i find this extremely frustrating. i realize that i am a dinosaur, but
> >> i really want a usable response to a whois query. compare
> >
> >I would just like to be able to
> On 14 Dec 2020, at 11:47, Royce Williams wrote:
>
> On Sun, Dec 13, 2020 at 3:30 PM John Levine wrote:
> In article you write:
> >On Sun, 13 Dec 2020, Randy Bush wrote:
> >> i find this extremely frustrating. i realize that i am a dinosaur, but
> >> i really want a usable response to a wh
17 matches
Mail list logo
