How a System Administrator Can Solve the _globalsign-domain-verification Issue

Contents: Understanding _globalsign-domain-verification Verify Where DNS is Managed Add the TXT Record to the DNS Zone Reload the DNS Service Verify the TXT Record Ensure DNS Propagation Troubleshooting Issues Notify GlobalSign for Verification Summary

System administrator solving GlobalSign verification issue

As a system administrator, your goal is to correctly add the _globalsign-domain-verification TXT record to your DNS server and ensure it propagates successfully. This guide provides a detailed, step-by-step approach to resolving any issues.

Understanding _globalsign-domain-verification

_globalsign-domain-verification is a TXT DNS record required by GlobalSign to verify domain ownership.
This record is used for Domain Control Validation (DCV) before issuing an SSL/TLS certificate.

GlobalSign provides the verification value in the format:

_globalsign-domain-verification=abcdef1234567890abcdef1234567890

Your task is to correctly add this TXT record to your DNS zone file.

Verify Where DNS is Managed

Before making any changes, determine where the DNS for the domain is hosted.

Check the DNS Authoritative Server

Run the following command to check where the domain's nameservers point:

dig NS example.com
or
nslookup -type=NS example.com

Replace example.com with the actual domain.

The output will list the authoritative nameservers. If your server is listed, you can proceed with adding the record. If the DNS is managed elsewhere, you may need to update the record on an external system.

Add the TXT Record to the DNS Zone

Now, you need to edit the domain's DNS zone file and add the _globalsign-domain-verification TXT record.

Modify the Zone File (BIND or Any Other DNS Server)

Open the DNS zone file:
sudo nano /etc/bind/zones/example.com.db

(Modify the path if your DNS server uses a different directory.)
Add the TXT record at the bottom of the file:
_globalsign-domain-verification IN TXT "abcdef1234567890abcdef1234567890"
Save the file and exit.

Reload the DNS Service

After modifying the DNS zone file, reload the DNS service to apply changes.

For BIND (named) DNS Server:

sudo systemctl reload named
or
sudo rndc reload

For PowerDNS:

sudo systemctl restart pdns

For Knot DNS:

sudo systemctl restart knot

If your system uses a different DNS server, reload it accordingly.

Verify the TXT Record

After adding the record and reloading DNS, verify that it has been correctly published.

Check Locally

Run:

dig TXT _globalsign-domain-verification.example.com
or
nslookup -type=TXT _globalsign-domain-verification.example.com

If the record appears with the correct value, the configuration is correct.

Check from External Servers

Use external tools to verify DNS propagation:

dig TXT _globalsign-domain-verification.example.com @8.8.8.8

(This queries Google's public DNS resolver.)

Another option:

dig TXT _globalsign-domain-verification.example.com @1.1.1.1

(This queries Cloudflare's public resolver.)

Ensure DNS Propagation

DNS records may take up to 48 hours to propagate. To speed up propagation, lower the TTL (Time to Live) before making changes.

Open the zone file again:
sudo nano /etc/bind/zones/example.com.db
Find the TTL setting (usually near the top) and reduce it to 300 seconds (5 minutes):
$TTL 300
Save the file and reload DNS.

Note: Once verification is complete, you can increase the TTL back to its original value.

Troubleshooting Issues

Issue	Solution
TXT record not found	Ensure it is added in the correct zone file and DNS is reloaded.
Incorrect TXT value	Copy the exact value provided by GlobalSign, ensuring no typos.
Delayed propagation	Lower the TTL and wait for propagation (can take up to 48 hours).
Query returns old data	Clear the local cache using `systemctl restart nscd` (if caching is enabled).
External queries fail	Verify firewall settings to allow external DNS queries.

Notify GlobalSign for Verification

Once the TXT record is confirmed to be live, GlobalSign should detect it automatically. If verification does not complete within 24 hours, manually notify GlobalSign and provide proof of the TXT record.

Summary

Check where the domain's DNS is hosted.
Add the _globalsign-domain-verification TXT record to the zone file.
Reload the DNS service to apply changes.
Verify the TXT record locally and externally.
Ensure proper DNS propagation by adjusting TTL settings.
Troubleshoot if the record is not found.
Wait for GlobalSign to detect the record and issue the SSL certificate.

By following these steps, a system administrator can successfully complete GlobalSign domain verification and ensure SSL certificates are issued without delays.

How a System Administrator Can Solve the _globalsign-domain-verification Issue

Understanding _globalsign-domain-verification

Verify Where DNS is Managed

Check the DNS Authoritative Server

Add the TXT Record to the DNS Zone

Modify the Zone File (BIND or Any Other DNS Server)

Reload the DNS Service

For BIND (named) DNS Server:

For PowerDNS:

For Knot DNS:

Verify the TXT Record

Check Locally

Check from External Servers

Ensure DNS Propagation

Troubleshooting Issues

Notify GlobalSign for Verification

Summary

Cloud Windows VDS

Hosting

Cloud Solution

For You

VDS

Website Builders

Our services

Client Area

Select Currency

How a System Administrator Can Solve the _globalsign-domain-verification Issue

Understanding _globalsign-domain-verification

Verify Where DNS is Managed

Check the DNS Authoritative Server

Add the TXT Record to the DNS Zone

Modify the Zone File (BIND or Any Other DNS Server)

Reload the DNS Service

For BIND (named) DNS Server:

For PowerDNS:

For Knot DNS:

Verify the TXT Record

Check Locally

Check from External Servers

Ensure DNS Propagation

Troubleshooting Issues

Notify GlobalSign for Verification

Summary

Cloud Windows VDS

Hosting

Cloud Solution

For You

VDS

Website Builders

Our services

Client Area

Выберите валюту