Domain registration

  • SpinRite v6.1 Release #3
    Guest:
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
    /Steve.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

    /Steve.
  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)

a viewer

Well-known member
Sep 30, 2020
81
18
I was surprised by this week's episode about problem domains. If the record (which probably nobody does right) was set up correctly, this shouldn't be an issue. Should the person or company managing your domain be no longer available, the owner of the domain should still be able to interact with the domain reseller. All the ones I have used have owner, admin, billing, and tech contacts for each domain (ICANN requirement?).

Even if payment lapses, you usually get about a month afterward to renew it. It is not difficult to imagine that you can lose your domain but really shouldn't happen. Maybe people should insist on being listed as the owner and billing(?) contacts.


You even get a yearly request to verify the information

 
  • Like
Reactions: PHXdNelson
All the ones I have used have owner, admin, billing, and tech contacts for each domain (ICANN requirement?).
As that data is not private, many resellers use a third party service to hide the information, which means all the registrations are to the 3rd party. (Aka DNS privacy.) But in any case, since the information is public, what is to stop anyone from impersonating you?? I doubt that any serious service is going to take your word that the domain is really yours.
 
I was surprised by this week's episode about problem domains. If the record (which probably nobody does right) was set up correctly, this shouldn't be an issue. Should the person or company managing your domain be no longer available, the owner of the domain should still be able to interact with the domain reseller. All the ones I have used have owner, admin, billing, and tech contacts for each domain (ICANN requirement?).

Even if payment lapses, you usually get about a month afterward to renew it. It is not difficult to imagine that you can lose your domain but really shouldn't happen. Maybe people should insist on being listed as the owner and billing(?) contacts.


You even get a yearly request to verify the information

I think you nailed the issue. If website guy sets up his Hover account and then adds domains to it, they'll inherit the default owner, admin and tech contacts (i.e. him) unless he specifies otherwise--and many of them probably don't bother.