Internal DNS Server resolves to wrong External IP address

Anonymous
2024-03-03T14:16:11+00:00
  • Starting a few days ago our Internal DNS servers began using Comcast DNS servers which are not correctly resolving External IP addresses. See image 1
  • Specifying the correct DNS server in nslookup still resolves to the wrong IP address. See image 2.
  • Using nslookup from an external network resolves to the correct IP address. See image 3
  • I assume we have to clear or reset our DNS cache/settings or contact Comcast.
  • Please advise.
Windows for business | Windows Server | Networking | Network connectivity and file sharing

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes
Accepted answer
  1. Anonymous
    2024-03-04T17:00:14+00:00

    Good Morning, the issue was Comcast Security Edge. Even though I had added our website url to the allowed list, it was still being blocked. I had Comcast disable Security Edge completely and access to our website from our internal network was restored. Below is the Comcast Security Edge report showing the website being blocked. Than you for your help.

    0 comments No comments

3 additional answers

Sort by: Most helpful
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  2. Anonymous
    2024-03-04T05:44:41+00:00

    Hi, I'm here to help with your problem.

    Can you try the following command to clear the cache and see if it improves:

    ipconfig /flushdns

    If it doesn't improve, I recommend you contact Comcast, as you indicated.

    Best regards,

    Yu

    0 comments No comments
  3. Anonymous
    2024-03-04T15:08:18+00:00

    Good Morning and thank you for the reply. I did run the command ipconfig /flushdns on both domain controllers/dns servers, unfortunately that di not change anything. I will contact Comcast. It seems there have been other Comcast customers with DNS problems

    0 comments No comments