So I got hold of a domain that shows my exact full name. I thought it would be useful for showing up as “professional” when working in IT and sending resumes.

I got some mail forwarded using the domain registrar. I also made a small static website, which only has hello world for now but soon will get the contents filled up.

But then… what? I suppose I can host anything I want, but then there’s the whole “real name - gotta look professional” aspect that makes me weary of hosting a Lemmy instance, for example, when the domain without my name attached wouldn’t.

I suppose having personal domains were cool in the 90s where people were barely learning about “the internets”. Not so anymore?

Is there a usefulness in having a domain name with your real name attached on this age?

  • shadowbert@kbin.social
    6·
    10 months ago

    I host some private stuff on mine, hidden behind an authentication service that is. But because I just use a wildcard no-one can really tell what I have hosted - the same login page occurs for every subdomain, regardless of whether it’s actually wired up to something.

    That doesn’t help with services you wish to make semi-public (like a lemmy instance) though.

      • shadowbert@kbin.social
        2·
        10 months ago

        I’m using cloudflare as my DNS, and it’s literally just:

        • Create an A record.
        • Set the name to *
        • Set the IP to the appropriate server
        • You may want to untick the proxy, depending on what you’re hosting. If it’s web stuff only it’s fine, but if you’re doing anything else as well it’ll get in the way.

        On the letsencrypt side, it’s pretty similar. Create a certificate with domain.name and *.domain.name (if you want them to share a cert) and you’re off.