Incorrect NS Records Served by nsX.byet.org for doai.id.vn (WHOIS Correct)

[NgocDoai]

Website URL

http://doai.id.vn

Error Message

1. When accessing the URL: HTTP ERROR 500 / Internal Server Error .
2. Underlying DNS Issue: Global DNS checkers (dnschecker.org, whatsmydns.net, intodns.com) show that the authoritative nameservers nsX.byet.org are incorrectly serving mixed NS records (including both nsX.byet.org and old nsX.infinityfree.com records) even after 72+ hours.

Other Information

• My InfinityFree Account Username: if0_37984521
• My Registrar: Tenten.vn
• Details: I added doai.id.vn as an Addon Domain and correctly updated nameservers at Tenten to ns1.byet.org, ns2.byet.org, ns3.byet.org, ns4.byet.org, ns5.byet.org several days ago (>72 hours).
• WHOIS Confirmation: WHOIS lookups confirm these byet.org nameservers are correctly set at the registry level.
• The Problem: Despite correct WHOIS, the authoritative nsX.byet.org nameservers themselves are still serving the wrong/mixed NS records globally, preventing stable DNS resolution.
• Registrar Response: My registrar (Tenten) confirmed the update on their side is correct according to WHOIS but suggested contacting InfinityFree about the mixed NS results being served by your nameservers.
• Request: Could an administrator please check the DNS zone file configuration for doai.id.vn on the ns1.byet.org through ns5.byet.org nameservers? Please ensure the incorrect/old ns1.infinityfree.com and ns2.infinityfree.com NS records are removed from the zone file for my domain on your servers.
• Note: I understand the HTTP 500 error needs separate troubleshooting later, but the primary blocker preventing reliable access and potentially causing other issues seems to be the inconsistent NS records served by your nameservers.

[dan3008]

@NgocDoai

ns1.infinityfree.com and ns2.infinityfree.com

I honestly thought that these were current, since they are the ones I use, and the ones that the dashboard tells me to use.

But looking at several other sites on the ns1.byte.org - ns5.bite.org, no others that I can see are showing the infinityfree name servers. This would suggest (to me at least) that its not the name server thats reporting incorrectly.

Honestly, sounds to me like tenten are kicking the can down the street.

Although, its probably worth fixing the error500 first, since fixing that would allow you to better assess if there are any access issues with your site.

The other thing that might be worth looking at is using cloudflare (and their nameservers), which allows you to add protection to your site aginst DDOS attacks

A Full Guide To Cloudflare

Hello, I will show you how to easily set up Cloudflare, Edit Records, and Troubleshoot with images! PLEASE READ BEFORE STARTING!!! Cloudflare cannot be used on free subdomains from InfinityFree. You can use Cloudflare on Custom Domains (yoursite.com) and with Custom Sub-Domains (subdomain.yoursite.com). A video tutorial can be found at the end of this guide, should you get stuck. You must connect your domain to your InfinityFree account first. Read more here. Set-Up Cloudflare Go to Dash…

[Admin]

@NgocDoai

When accessing the URL: HTTP ERROR 500 / Internal Server Error .

That error is covered here (spoilers: it’s not DNS):

Http error 500

When trying to access your website, you may see a page which returns the status code “500”. In Google Chrome, you’ll see a page with the error code HTTP ERROR 500. There are typically two reasons which can cause this error: The PHP code has crashed. The .htaccess file contains invalid rules. Here are some things you can try to debug and fix this. Fixing crashing PHP code A HTTP ERROR 500 simply tells you that the PHP code has crashed, but gives no information as to why it has crashed. Gett…

@NgocDoai

Underlying DNS Issue: Global DNS checkers (dnschecker.org, whatsmydns.net, intodns.com) show that the authoritative nameservers nsX.byet.org are incorrectly serving mixed NS records (including both nsX.byet.org and old nsX.infinityfree.com records) even after 72+ hours.

That’s not actually an issue. Yes, it’s technically not entirely “correct”, but it has zero consequences for your website.

The only thing DNS does is make sure that your domain is linked to your website IP address with us. It has no impact at all on how that server responds to your requests for your website, including any HTTP errors.