What is 199.232.214.172 / : bg.microsoft.map.fastly.net

Hello,

Thank you for posting in Microsoft Community forum.

Step-by-Step Troubleshooting Guide:

Step 1: Check DNS Configuration

1. Verify DNS Settings

Ensure that the DNS configuration on the devices (especially the Windows 11 device) is set up correctly. You can check and change DNS settings as follows:

Open Network and Sharing Center.

Select Change adapter settings.

Right-click on the active network connection (Wi-Fi or Ethernet), and choose Properties.

Select Internet Protocol Version 4 (TCP/IPv4), then click Properties.

In the DNS section, enter the following DNS server addresses:

You can use Google DNS (8.8.8.8 and 8.8.4.4) or Cloudflare DNS (1.1.1.1 and 1.0.0.1).

Click OK to save the settings.

1. Verify DNS Resolution

Use the command prompt to verify that the domain resolves correctly:

nslookup bg.microsoft.map.fastly.net

If the DNS cannot resolve this domain, try using other DNS servers or check if the DNS server is experiencing issues.

Step 2: Check Network Connection

1. Check Wi-Fi Signal Strength

Ensure the Wi-Fi signal strength is adequate. If the signal is weak, try moving closer to the router or use a wired connection.

1. Test Wi-Fi and Wired Connection Speeds

Test the speed of both Wi-Fi and wired connections to confirm if network bandwidth is sufficient.

If the Wi-Fi network is overloaded, try using a wired connection temporarily for testing.

1. Try Using Wired Connection

If the issue only occurs on Wi-Fi, try connecting the Windows 11 device directly to the router using an Ethernet cable and check if the SQL server connection works properly.

Step 3: Check Fastly Network Service

1. Check Fastly Service Status

Visit Fastly's status page to check for any global or regional service outages. If there is an issue, wait for Fastly to resolve it before proceeding.

1. Contact Fastly Support

If Fastly's service is operational but the domain still cannot be resolved, contact Fastly support to verify if the domain bg.microsoft.map.fastly.net is properly configured and added to the service.

Step 4: Check Windows 11 Network Settings

1. Disable IPv6

In some network configurations, IPv6 can cause issues. Try disabling IPv6:

Open Network and Sharing Center.

Select Change adapter settings.

Right-click on the active network connection, and choose Properties.

1. Uncheck Internet Protocol Version 6 (TCP/IPv6), then click OK.
2. Disable Windows Firewall or Security Software

Temporarily disable Windows Firewall or any third-party security software to check if they are causing the network connection issues.

1. Update Network Drivers

Ensure that the network adapter drivers on Windows 11 are up to date. You can check and update drivers via Device Manager.

Step 5: Consider Delaying Windows 11 Deployment

1. Delay Windows 11 Deployment

If the above steps don't resolve the issue, consider delaying the deployment of Windows 11 until the network and domain resolution problems are fixed.

1. Complete Tasks Using Wired Network

In the meantime, use a wired connection to complete tasks and avoid the impact of Wi-Fi network issues.

Summary:

Following the steps outlined above will help diagnose and resolve domain resolution and network connectivity issues. Verify DNS settings, check network connections, use Wireshark for analysis, and ensure there are no issues with Fastly services. If the problem persists, consider delaying the Windows 11 deployment and temporarily using a wired connection.

I hope this helps! Let me know if you have further questions or if you need additional assistance.

First thing i did was check the DNS, and set the application server in the host file to see if i could boost preformance.

Pinging the IP resolved to fastly.net, think DNS is working.

All Windows 10 Laptops on DHCP don't have the issue, so a DNS problem only on Windows 11 (Maybe if it was static).

I think it is more likely that the IP is used for windows update (updating the 24H2 release). but it's on 0% for a couple of days.

I'm going to blacklist the IP for now till Microsoft fixes the faulty content.

(To be clear, it's on 24H2, but the update or fix for 24H2 is not doing anything).

Based on the customer's feedback, here’s a detailed troubleshooting plan:

1. Check DNS Configuration

Ensure that the DNS settings on the Windows 11 devices are correctly configured, especially if you're using static IP addresses.

You can follow these steps to verify the DNS settings:

• Go to Control Panel > Network and Sharing Center > Change adapter settings.
• Right-click on the active network connection (Wi-Fi or Ethernet), and select Properties.
• Select Internet Protocol Version 4 (TCP/IPv4), then click Properties.
• Set the DNS to public DNS (e.g., Google DNS: 8.8.8.8 and 8.8.4.4, or Cloudflare DNS: 1.1.1.1 and 1.0.0.1).
• Click OK to save the settings.

Verify whether this resolves the DNS issue.

2. Check Static IP Issues

If you're using a static IP, ensure that the IP address does not conflict with the DHCP server’s assigned range.

If possible, try switching the static IP to a dynamic one to see if the issue persists.

3. Check Windows Update Status

Go to Settings > Windows Update and check if there are any pending updates or updates in progress.

If the 24H2 update is stuck (e.g., showing 0%), try these steps:

• Pause the update and restart the device.
• Run the Windows Update Troubleshooter: Settings > System > Troubleshoot > Other troubleshooters > Windows Update.
• If the issue remains, you can manually download and install the 24H2 update package.

4. Verify Fastly CDN Issues

Based on the customer's feedback, Fastly CDN might be causing issues in delivering content. You can use tools like nslookup or ping to check the resolution status of bg.microsoft.map.fastly.net.

Ensure the domain resolves correctly and is not being blocked by a firewall or network security software.

5. Disable IPv6

If the device is using IPv6, disabling it might help resolve some connectivity issues:

• Go to Control Panel > Network and Sharing Center > Change adapter settings.
• Right-click the connection, select Properties.
• Uncheck Internet Protocol Version 6 (TCP/IPv6) under the "This connection uses the following items" list.
• Click OK to save the settings.

6. Test Wired Connection

If Wi-Fi is problematic, test with a wired connection to verify network stability and DNS resolution.

7. Blacklist the IP

As per the customer's request, temporarily blacklist the involved IP (e.g., 199.232.214.172) to prevent it from interfering with the device’s updates and connections.