Pinging subdomain not resolving correctly

[kb222]

I set up a subdomain and have it forwarding to a public IP. When I ping that subdomain however, it resolves to a GoDaddy 184 IP and not the IP I forwarded it to. When typed into an address bar, it forwards to the correct IP. Is this normal?

[PL281]

@kb222 

If you are using the GoDaddy "Forwarding" feature vs setting up an A record. That is the correct IP as it is pointing to the GoDaddy Forwarding Server which in turn is forwarding it to the final location.

[kb222]

I have an A name setup to forward as well.

[PL281]

@kb222 

So generally speaking you should NOT use the "subdomain" feature unless you need to "forward" to a 3rd party site

For example if I wanted search.mydomain.com to load https://www.google.com then I would use the subdomain feature.

Otherwise I would just add an A record or CNAME depending on the 3rd party system. In using the A record / CNAME - the 3rd party system / server must be configured to receive traffic from that domain.

[kb222]

@PL281 Is it possible to set it so it pings the forwarded IP directly? When I set up a subdomain, it forces me to fill out the 'forward to' box.

[PL281 · Accepted solution]

@kb222 

If you want to have your own public IP reply to the ping then what you need to do is delete the subdomain - then just add an A record in the DNS - as I said though using this method your network / server may need a setting configured to map the domain to your server