addon domain not resolving with new dedicated IP

[TroyL]

I have an add on domain that is not resolving since upgrading to a dedicated IP address. The add on's domain name is actually registered at another IP address and the A record is set to point to my account and was updated accordingly. I added SSL for one of my add on domains and all my other add ons are working with the exception of this one. I get the apache installation success page. This has been going on for about two weeks so it isn't a matter of the new info propagating. Is there something that I am missing or any suggestions to solve this dilema?

[Maxim M.]

It is hard to guess what the problem with this particular domain name is. I could give any details if you at least provided the domain itself.

If you use external name servers (i.e. default registrar) rather than server default or private ones, I would suggest updating them to ours. Thus you would use DNS zone on the server which should be free of any error.

Anyway, the technicians should investigate it for you. Please submit a technical department ticket at https://whbsupport.com

[Alan B]

add on's domain name is actually registered at another IP address

This statement is rather confused. If the authoritative DNS Zone is on your WHB server, then that is the zone that is required to contain the information about the addon domain. Otherwise DNS lookups won't know where to find that addon domain.

I suggest that you clarify what you have done with the setup, and also tell us both the domain name and the addon domain name.