🔧 Issue: SSL/TLS Certificate Stuck on “Waiting on DNS propagation” Despite Successful Verification

Support
1

Hi everyone,

I’m facing an issue with SSL/TLS provisioning on Netlify that I haven’t been able to resolve despite extensive troubleshooting.

:white_check_mark: Current Situation

  • Custom domain: kahvely.app

  • Netlify domain: kahvely.netlify.app

  • DNS provider: Hostinger

  • Netlify domain setup:

    • kahvely.app (primary)

    • www.kahvely.app → redirects correctly

:magnifying_glass_tilted_left: DNS Configuration

I have tested multiple configurations:

1. ALIAS (flattened CNAME)

ALIAS @ → apex-loadbalancer.netlify.com

2. A records (fallback)

A @ → 75.2.60.5

3. CNAME for www

CNAME www → kahvely.netlify.app

:test_tube: Verification & Testing

  • DNS propagation checked globally via DNSChecker:

    • Root domain resolves consistently to:

      75.2.60.5

    • www resolves correctly to kahvely.netlify.app

  • No conflicting or legacy DNS records remain

  • TTL values are low (60–300)

  • Let’s Encrypt HTTP-01 challenge test: passed successfully

  • Domain is reachable and routing correctly to Netlify

:warning: The Issue

In Netlify:

  1. When I click “Verify DNS configuration”, I get:

    DNS verification was successful âś…

  2. However, after refreshing the page:

    SSL/TLS certificate → Waiting on DNS propagation ⏳

This state keeps repeating indefinitely.

:brain: Observations

  • DNS is clearly propagated globally

  • Netlify can verify DNS on-demand

  • But SSL provisioning never progresses to “Provisioning” or “Active”

  • UI seems to revert to “Waiting on DNS propagation” after refresh

:repeat_button: What I’ve Tried

  • Switching between ALIAS and pure A record setups

  • Removing all conflicting records

  • Re-verifying DNS multiple times

  • Waiting (over 12+ hours)

  • Testing from multiple networks / tools

:red_question_mark: Question

Has anyone encountered this behavior where:

DNS verification succeeds manually, but Netlify fails to persist the state and does not issue the SSL certificate?

Could this be:

  • A caching issue on Netlify’s side?

  • A validation inconsistency across regions?

  • A known issue with certain DNS providers (Hostinger)?

Any insight would be greatly appreciated. Thanks in advance :folded_hands:

2

Okay it seems like its fixed after a couple of days.
I don’t know why or how.
Thanks anyways.