DNS Management

static.bg gives you full control over your domain’s DNS records directly from the control panel. No support tickets, no hidden limitations, and no delays.

Full DNS Control

You can create, edit, and delete DNS records at any time. All changes are managed by you and applied immediately, allowing you to configure your domain exactly the way your project requires.

This is especially useful when connecting third-party services, setting up email, or verifying domain ownership for external platforms.

Supported DNS Record Types

The control panel supports the most commonly used DNS record types:

• TXT – domain verification, SPF, DKIM, and other metadata
• MX – configure external email providers

TXT Records

TXT records are commonly used for domain verification, email security, and integrations with third-party services. You can add multiple TXT records without restrictions.

Typical use cases include SPF, DKIM, DMARC, and ownership verification for services like Google, Cloudflare, or email providers.

MX Records

MX records allow you to route email for your domain to any external mail service. static.bg does not impose any limits on MX priorities or the number of records.

This makes it easy to use services such as Google Workspace, Microsoft 365, or any custom mail server.

No Vendor Lock-in

Your DNS configuration is fully transparent and portable. You are free to integrate static.bg with any external service or infrastructure without workarounds or platform-specific restrictions.

Best Practices

• Always double-check TXT and MX values before saving
• Allow some time for DNS propagation when testing changes
• Keep SPF, DKIM, and DMARC records up to date for email reliability

GitHub Deployment

static.bg allows you to deploy static websites directly from a GitHub repository. Once connected, your site can be updated automatically or manually with every change pushed to your repository.

Connecting a GitHub Repository

To enable GitHub deployment, connect your GitHub account from the control panel. After authorization, you can select one of your repositories to use as the source for your static site.

Only static build artifacts from the selected repository will be deployed. Server-side code and dynamic runtimes are not supported.

Repository and Branch Selection

You can choose which repository and branch should be used for deployment. This allows you to keep production, staging, or preview versions separated using different branches.

• Select the repository that contains your static project
• Choose the branch to deploy (for example main or production)

JavaScript Frameworks

If your project uses a JavaScript framework, you can select it from the framework dropdown. This helps preconfigure the build process.

Supported setups include plain HTML/CSS/JS as well as frameworks that can generate static output, such as Astro, Vite, React, Vue, and others.

Build Command

For projects that require a build step, you can define a build command. This command is executed on the server before deploying the generated static files.

If your project does not require a build step, you can leave this option set to None (no build step).

Automatic Updates

static.bg provides two optional automation features:

• Auto pull commits – automatically pulls the latest changes from the selected branch
• Auto deploy – automatically redeploys the site after new commits are pulled

These options allow you to create a fully automated deployment pipeline with zero manual intervention.

Manual Deployment

If automation is disabled, you can manually trigger deployments from the control panel. This gives you full control over when changes go live.

Security and Access

GitHub access is limited strictly to the permissions required for deployment. static.bg does not modify your repositories and only reads the data necessary to fetch source files.