Rick Moen via luv-talk wrote:
Quoting Rohan McLeod (rhn@jeack.com.au):
Rick I am sure for you this seems a small thing; but for me it would be a fairly steep learning curve; At the time I figured out how to run my own Linux server, I was a tax preparer and staff accountant, with zero IT experience. It took a couple of days to get it right (and, of course, use of a static IP address). The first machine was still my old 486, if memory serves.
I actually deferred the problem of domains and DNS until long after setting up my Linux server with SMTP Mail: Fortunately, a friend of mine owned domain 'imat.com', and was glad to make an entry in his DNS for 'hugin.imat.com' pointing to my new Linux server. He kindly keeps that entry valid, which is why I continue to be reachable on my Linux server as 'rick@hugin.imat.com', as I have been since around 1994.
ISTR a friend bought for me the 'linuxmafia.com' domain around 1998, which is perforce when I learned domain administration and authoritative DNS.
Rick and Trent I see virtue in both your 'approaches' - Rick is suggesting I just start from the beginning and persist -Trent is pointing out the huge number of 'gotcha's', which would be involved in that path It occurs to me after sleeping on it; the problem can be split. - What about if I could just acquire "jeack.com.au" (at the moment that seems analogous to owning a company name); then have the domain hosted by someone else ? Thus postponing hosting it myself ! -Is this hypothetically possible ? --What gotchas might be invovled in acquiring the domain name ? --What gotchas might be involved in then having it 'hosted' (even what that means is unclear !); by some third party ? --- About as far as I have got with understanding 'hosting' is somehow the IP(s ?) which are referenced by the domain name ; must be either changed or referrenced indirectly ? regards Rohan McLeod