genwork Posted 9 hours ago Posted 9 hours ago udomz.com is having issues again. It was working fine before. but I can still access iden3.genrwork.com through the proxy Quote
wolstech Posted 3 hours ago Posted 3 hours ago Try clearing your browser cache. If that does not resolve it, it's probably an issue upstream somewhere, likely either a stale cache at your ISP or a DNS configuration issue. Since you do not use our DNS, and you have genrwork's DNS hidden behind Cloudflare, we are unable to troubleshoot this further. If you would like us to troubleshoot this, please turn off the Cloudflare Proxy and any associated gateways/security pages like Cloudflare Turnstile on genrwork.com. As for the domain udomz.com showing that domain setup page, it's because it is currently disabled due to not being pointed to our servers. Domains with DNS records that do not point to our IP addresses are automatically disabled to reduce server load. Quote
genwork Posted 3 hours ago Author Posted 3 hours ago (edited) It doesn't seem to be a browser issue, especially since the [genrwork] domain points to Heliohost's IP address, not Cloudflare's. And what I'm taking issue with is the domain [udomz.com], not [genrwork.com] Edited 2 hours ago by genwork provide more clarity on the issue Quote
wolstech Posted 2 hours ago Posted 2 hours ago The udomz.com domain is not hosted with us at the moment. It is attached to your account but is disabled because it has DNS records that do not point to us. We see the below DNS records for udomz.com, which are incorrect. Either the NS records need to be changed to ns1.heliohost.org and ns2.heliohost.org, or the A record needs to be changed to the same .90 IP as the genrwork.helioho.st domain. If you change the DNS to point to us, you will also need to go into the domain in Plesk, set its status to Active, and wait up to 2 hours for it to become functional. If you do not want the udomz.com domain to be hosted here (or it's not your domain and was inadvertently added), let us know and we can remove it from your account instead. Incorrect A record for udomz: host: udomz.com class: IN ttl: 60 type: A ip: 151.101.41.242 Third party NS records: host: udomz.com class: IN ttl: 78276 type: NS target: ns1.vercel-dns.com host: udomz.com class: IN ttl: 78276 type: NS target: ns2.vercel-dns.com Quote
genwork Posted 1 hour ago Author Posted 1 hour ago (edited) 58 minutes ago, wolstech said: you will also need to go into the domain in Plesk, set its status to Active, and wait up to 2 hours for it maybe because of this. i will try it Edited 1 hour ago by genwork aware of a suggestion Quote
wolstech Posted 56 minutes ago Posted 56 minutes ago If you enable the domain but don’t change the DNS, be aware that the server will eventually disable it again, typically within 7 days. Domains must return either one of our IPs as the A (or MX, if it’s mail-only) record, or have Cloudflare as name servers (using CF triggers our system to handle domains differently because of the proxy/security features), to avoid being disabled. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.