Add KlypX domain configuration

[Anandhu-AKR]

Requirements

• You have completed your website.
• The website is reachable.
• The CNAME record doesn't contain https:// or /.
• There is sufficient information at the owner field.
• There is no NS Records (Enforced as of September 4th, 2024)
• I fully accept and understand the Terms of Service outline when using this service.
• I understand that if these requirements are not met my pull request will be closed.

Description

KlypX is a cross-platform device synchronization and fast device-to-device file transfer platform.

The domain klypx.owns.it.com will be used for the public KlypX web dashboard, which is currently hosted on Cloudflare Pages.

Link to Website

https://klypx.pages.dev

[domains-project]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[Anandhu-AKR]

I have read the CLA Document and I hereby sign the CLA

[Anandhu-AKR]

The validation workflows are currently failing due to workflow-level issues unrelated to this domain configuration.

Observed failures:

1. Validation / DNS:
   Unable to resolve action is-a-dev/dnscontrol-action, repository not found

2. Validation / JSON and Validation / Tests:
   Refusing to check out fork pull request code from a 'pull_request_target' workflow

The submitted domain JSON itself is valid and contains:

• CNAME: klypx.pages.dev
• owner repository: https://github.com/Anandhu-AKR/KlypX

The CLA has also been signed successfully.

Could a maintainer please review/re-run the validation workflows?

[Anandhu-AKR]

re-run validation

[Anandhu-AKR]

Hi maintainers,

The domain configuration itself appears valid, but the required validation workflows are currently failing before validation can complete.

Observed failures:

1. Validation / DNS
   Unable to resolve action:
   is-a-dev/dnscontrol-action@main

2. Validation / JSON
   GitHub refuses checkout of the fork PR code from a pull_request_target workflow.

3. Validation / Tests
   Same pull_request_target checkout restriction.

The CLA check is passing successfully.

There are also no merge conflicts with the base branch.

Could you please check/re-run the repository validation workflows or update the workflow configuration if needed?

I have not modified the workflow files in my fork because these appear to be base-repository workflow issues.

Thank you.