Skip to main content
We are aware of an issue with a recent Apache update that causes proxied sites to return a "421 Misdirected Request" error. Please see the following article for more information and updates:
Websites show 421 Misdirected Request error while using EA Nginx

new hostname not resolving to any ip

mmaciel
hello recently our hosting provider (godaddy) warned us that the default hostname used for their vps had changed and would stop resolving mid september, so we had to change our server hostname as well we did, via godaddy's control panel, which also automatically adds the new dns zones and hostname to whm, but unfortunately this new hostname does not resolve to our servers IPs (which remains the same) the new hostname and correct ip does show up under whm > home > dns functions > add an A entry for your hostname, it also shows up under dns zone manager with the correct ip, but still does not resolve also, funnily enough, the new default hostname godaddy uses now resolves to the correct ip, but i can't find any entry for it anywhere in our server's or godaddy's control panel (maybe it's an internal config of theirs?) should i just change it back to their new default hostname? i really don't like their format of using the server ip as the hostname any help would be appreciated, thanks

Comments

5 comments

Date Votes
  • cPRex Jurassic Moderator
    Hey there! The hostname is just another subdomain, so you'll need to ensure the DNS for that subdomain exists wherever that is being managed. It sounds like the DNS is not being managed on the cPanel server itself, since you have noted all the A records are in place but it is still not resolving. I'd check the DNS for the domain and confirm where that is being handled and ensure the A record is created there.
    0
  • mmaciel
    Hey there! The hostname is just another subdomain, so you'll need to ensure the DNS for that subdomain exists wherever that is being managed. It sounds like the DNS is not being managed on the cPanel server itself, since you have noted all the A records are in place but it is still not resolving. I'd check the DNS for the domain and confirm where that is being handled and ensure the A record is created there.

    hey Rex, how are you? yeah, it's weird, the entry is there under dns zone editor and everything is correct, but like you said, it sounds like it's not being managed by the cpanel server, which is weird, cause we use godaddy for hosting only, and our domains/dns are managed directly with our registrar and cpanel by ourselves and there was never an entry for the old or the new hostname, so everything points to godaddy managing this internally (and automatically) here's the full message just in case: [QUOTE] Action Required Our default VPS hostnames have changed. If you are still using your default hostname of ip-ourserverip.ip.secureserver.net, you will need to change it. The new hostname format is ourserverreverseip.host.secureserver.net. DNS for your previous hostname will stop resolving on 09/14/2022, 08:00 PM. Additional information can be found
    0
  • cPRex Jurassic Moderator
    It sounds like you may have to use that hostname they provide from the sounds of it. I'd reach out to them to see if a custom hostname is an option at all.
    0
  • mmaciel
    It sounds like you may have to use that hostname they provide from the sounds of it. I'd reach out to them to see if a custom hostname is an option at all.

    indeed... i'll reach out to them, thanks Rex.
    0
  • cPRex Jurassic Moderator
    Sure thing!
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post