keybase / keybase-issues

A single repo for managing publicly recognized issues with the keybase client, installer, and website.
902 stars 37 forks source link

Adding "Custom Domains" #1505

Open muellerlukas opened 9 years ago

muellerlukas commented 9 years ago

It would be nice to set a "custom domain" like "pgp.example.com" via CNAME or A-Record, that shows directly the users profile. Looks nicer and maybe a bit more "official" for some people.

zQueal commented 9 years ago

I'm a little confused as to what you're asking here. Think you could clarify a bit more?

ItsAGeekThing commented 9 years ago

He means he would like the ability to point a subdomain with a CNAME or A record to a user's keybase profile.

Ex. pgp.mydomain.com -> keybase.io/username

ghost commented 9 years ago

this example is by design of DNS not possible, you can only do a 301 if you need to specify a path.

The only way to achieve this via CNAME is to generate subdomains UID.keybase.io additionally to the keybase.io/UID (because backwards compatibility)

muellerlukas commented 9 years ago

Yep, thats what I meant. On Tumblr e.g. you can set a "custom domain". You set an CNAME-Record to "domains.tumlr.com". Now you can use your tumbler with your own domain.

potterzot commented 8 years ago

I believe this is also relevant for users who want to use github's static-page hosting but reroute from their private domain. For me, I have an A record to route example.com to github dns ip addresses, and a CNAME in potterzot.github.io that points to example.com. This way I can use jekyll to build a static site and host on github for free.

But when I do verification at example.com, it fails, even if I have the keybase.txt file in my potterzot.github.io repository.

I could verify at potterzot.github.io explicitly, but then potterzot.com, which is the name that anyone who visits the site will see, won't be verified.

sebie commented 8 years ago

In your case @potterzot ,

I don't think the problem is with Keybase, rather with your GitHub Pages hosted Jekyll site. When trying to access http://potterzot.com/keybase.txt, or potterzot.github.io; or even robots.txt. They return a 404.

Possible problems might be:

You can always verify the domain through DNS, which might be easier in your case.