Issue Plesk DNS not responding externally – Registrar says nameserver did not respond (Windows Server)

[Fahad009]

Server operating system version

Windows Server 2019 Standard

Plesk version and microupdate number

Version 18.0.74 Update #3

Hello everyone,


I’m running Plesk on Windows Server and using Plesk to manage DNS for my domain.
My domain registrar is WebHostBD, and I have configured my own nameserver:

• ns1.mydomain.com → 203.76.124.70 (my server public IP)

However, when I try to set this at the registrar, I get the error:

“One or more of your nameservers did not respond: 203.76.124.70”

Current setup:

• OS: Windows Server 2019 Standard
• Control panel: Plesk Obsidian Web Pro Edition
• Version 18.0.74 Update #3
• DNS is managed by Plesk
• DNS service status: Running
• Port 53 (TCP/UDP): Open in Windows Firewall
• Public IP: 203.76.124.70
• Domain has DNS zone in Plesk with:
  • A record: ns1.mydomain.com → 203.76.124.70
  • NS record: mydomain.com → ns1.mydomain.com

But from outside, queries like:

nslookup mydomain.com 203.76.124.70

Either timeout or return no response.
My questions:

1. Does Plesk on Windows require any additional configuration to make DNS authoritative externally?
2. Is there anything special needed for glue/child nameservers with Plesk?

Any guidance on proper production setup for Plesk DNS on Windows would be appreciated.

Thank you in advance.

 

[Fahad009]

Here are some photos if it helps

 

[scsa20]

I have never heard of WebHostBD so I don't know what the information is consisted of what it offers but you need to set up what is called a glue record. This might be listed in the Private Nameservers or DNS Management. Without that glue record set it will not know how to properly route the request to pull the DNS information.