Stormkit generates txt hostname and value for validating domain names and ask user ot add these values to their dns provider.
For the txt host name we follow . format. For example if user wants to validate vsk.me stormkit will ask to add txt record with hostname .vsk.me
This is a wrong directive because just adding hash as hostname would be enough. Providers concatanate domain name automatically.
As it can be seen from image adding 1234 as hostname and cloudflare already added .gigs4peeps.com if we add 1234.gigs4.peeps has txt name cloudflare will omit that. Problem occurs with other domain providers such as namecheap unlike cloudflare and godady they don't omit 1234.gigs4.peeps which causes conflic with root level txt name. By suggesting user to just use hash as txt domain name we solve this problem
Stormkit generates txt hostname and value for validating domain names and ask user ot add these values to their dns provider.
For the txt host name we follow. format. For example if user wants to validate vsk.me stormkit will ask to add txt record with hostname .vsk.me
This is a wrong directive because just adding hash as hostname would be enough. Providers concatanate domain name automatically.
As it can be seen from image adding 1234 as hostname and cloudflare already added
.gigs4peeps.com
if we add 1234.gigs4.peeps has txt name cloudflare will omit that. Problem occurs with other domain providers such as namecheap unlike cloudflare and godady they don't omit 1234.gigs4.peeps which causes conflic with root level txt name. By suggesting user to just use hash as txt domain name we solve this problem