• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Recent content by Fahad009

  1. Fahad009

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

    Hi everyone, I just wanted to follow up and close the loop on this issue — and thank everyone who took the time to help. After extensive troubleshooting on my side (checking Windows DNS service, verifying port 53 was listening, reviewing firewall rules, testing from multiple external sources...
  2. Fahad009

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

    I’ve reviewed the DNS Server logs in Event Viewer and found the following relevant entries: Event ID 7050 (Error) These errors appear intermittently and seem to indicate failed receive operations on the DNS socket. This suggests that the DNS service is attempting to receive queries but the...
  3. Fahad009

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

    DNS port s also open C:\Users\Administrator>netstat -an | find ":53" TCP 0.0.0.0:5357 0.0.0.0:0 LISTENING TCP 123.200.15.74:53 0.0.0.0:0 LISTENING TCP 127.0.0.1:53 0.0.0.0:0 LISTENING TCP 203.76.124.70:53...
  4. Fahad009

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

    Thanks for pointing that out — you’re absolutely right about the glue record. WebHostBD lists this under Child / Private Nameservers, and I have already created the glue record there: ns1.butsbd.com → 203.76.124.70 The domain butsbd.com is currently configured to use: ns1.butsbd.com as its...
  5. Fahad009

    Issue Stop Plesk Brute Force Attacks NOW: Cloudflare + Windows Server Fix

    As of this moment, I'm still unable to pinpoint the problem
  6. Fahad009

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

    Here are some photos if it helps
  7. Fahad009

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

    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...
  8. Fahad009

    Resolved DNS Issue: One or more of your nameservers did not respond

    having facing the same issue can anyone help me my port is open glue is ok but still not working
See more
Back
Top