Hi Riju Kumar
Greetings!
I understand that you have configured the FQDN "msa-ant-cmrp-dataingestionapi.ant.works" on the application gateway backend in which diagnostic checks point to a DNS resolution failure for the backend server's FQDN.
Mostly, this issue happens when custom DNS servers aren't reachable or doesn't have the necessary records to resolve the domain. If you have recently changed the DNS servers, you need to stop and start by using the PowerShell commands described in these linked resources described in these linked resources, because the application gateway might cache old DNS settings.
If the domain is private or internal, you can try to do nslookup or resolve the private domain "msa-ant-cmrp-dataingestionapi.ant.works" from a VM in the same virtual network. Also, you can check the network connectivity between the DNS servers and the Application Gateway. If there are NSGs or firewalls blocking DNS traffic (port 53), that could cause resolution failures. You can do this by using connection troubleshoot
Please refer DNS resolution error
If above is unclear and/or you are unsure about something add a comment below.
Your feedback is important so please take a moment to accept answers. If you still have questions, please let us know what is needed in the comments so the question can be answered. Thank you for helping to improve Microsoft Q&A!
Please accept an answer if correct. Original posters help the community find answers faster by identifying the correct answer. Here is how.