Skip to main content
This tool validates if a domain is correctly configured and resolves to the expected server IP.
Validates if a domain is correctly configured, optionally against a specific server IP.Annotations:
  • Read-only: true
  • Idempotent: true
​
domain
string
required
The domain name to validate (e.g., example.com).
​
serverIp
string
Optional server IP to validate DNS resolution against.
​
valid
boolean
Whether the domain is correctly configured.
​
resolvedIp
string
The IP address the domain currently resolves to.
​
message
string
Validation result message.
Example:
{
  "domain": "api.example.com",
  "serverIp": "192.168.1.100"
}
Response (Valid):
{
  "message": "Validation result for domain \"api.example.com\":",
  "data": {
    "valid": true,
    "resolvedIp": "192.168.1.100",
    "matches": true,
    "message": "Domain is correctly configured and resolves to the expected server IP"
  }
}
Response (Invalid):
{
  "message": "Validation result for domain \"api.example.com\":",
  "data": {
    "valid": false,
    "resolvedIp": "203.0.113.5",
    "expectedIp": "192.168.1.100",
    "matches": false,
    "message": "Domain resolves to incorrect IP address"
  }
}

​
Use Cases

​
Pre-deployment Validation

Before creating a domain in Dokploy, validate that the DNS is correctly configured: 
{
  "tool": "domain-validateDomain",
  "input": {
    "domain": "myapp.example.com",
    "serverIp": "192.168.1.100"
  }
}

​
Troubleshooting Domain Issues

If a domain isn’t working as expected, validate the DNS configuration: 
{
  "tool": "domain-validateDomain",
  "input": {
    "domain": "broken.example.com"
  }
}

​
Verify Domain Propagation

After updating DNS records, check if the changes have propagated: 
{
  "tool": "domain-validateDomain",
  "input": {
    "domain": "newapp.example.com",
    "serverIp": "192.168.1.100"
  }
}
DNS propagation can take up to 48 hours, though it typically happens within minutes to hours. If validation fails, wait a bit and try again.

​
Common Validation Errors

​
Domain Not Resolving

If the domain doesn’t resolve to any IP:
  • Check that the DNS A record is configured
  • Verify the domain registrar settings
  • Ensure nameservers are correctly set

​
Wrong IP Address

If the domain resolves to the wrong IP:
  • Update the DNS A record to point to the correct server IP
  • Wait for DNS propagation
  • Clear local DNS cache if needed

​
SSL Certificate Issues

If SSL isn’t working after domain validation:
  • Ensure the domain is validated and resolving correctly
  • Check that the certificateType is set correctly in the domain configuration
  • Verify that Let’s Encrypt can reach your server on port 80 (for HTTP-01 challenge)

Build docs developers (and LLMs) love

Get started for freeTalk to us