Skip to main content
added 14 characters in body
Source Link

From my side it looks like the SE-NetworkStack Exchange Network is doing a failover which impacts the ip-adressesIP adresses for the servers. For all domains the DNS records has to be updated and then those updates need to propagate to all DNS servers and finally your own box.

The updating takes time. Maybe because a human has to enter the new IP addresses in some management console at an ISP hosting the DNS.

From my side it looks like the SE-Network is doing a failover which impacts the ip-adresses for the servers. For all domains the DNS records has to be updated and then those updates need to propagate to all DNS servers and finally your own box.

The updating takes time. Maybe because a human has to enter the new IP addresses in some management console at an ISP hosting the DNS.

From my side it looks like the Stack Exchange Network is doing a failover which impacts the IP adresses for the servers. For all domains the DNS records has to be updated and then those updates need to propagate to all DNS servers and finally your own box.

The updating takes time. Maybe because a human has to enter the new IP addresses in some management console at an ISP hosting the DNS.

edited body
Source Link
rene Mod
  • 92.1k
  • 17
  • 245
  • 516

From my siteside it looks like the SE-Network is doing a failover which impacts the ip-adresses for the servers. For all domains the DNS records has to be updated and then those updates need to propagate to all DNS servers and finally your own box.

The updating takes time. Maybe because a human has to enter the new IP addresses in some management console at an ISP hosting the DNS.

From my site it looks like the SE-Network is doing a failover which impacts the ip-adresses for the servers. For all domains the DNS records has to be updated and then those updates need to propagate to all DNS servers and finally your own box.

The updating takes time. Maybe because a human has to enter the new IP addresses in some management console at an ISP hosting the DNS.

From my side it looks like the SE-Network is doing a failover which impacts the ip-adresses for the servers. For all domains the DNS records has to be updated and then those updates need to propagate to all DNS servers and finally your own box.

The updating takes time. Maybe because a human has to enter the new IP addresses in some management console at an ISP hosting the DNS.

Source Link
rene Mod
  • 92.1k
  • 17
  • 245
  • 516

From my site it looks like the SE-Network is doing a failover which impacts the ip-adresses for the servers. For all domains the DNS records has to be updated and then those updates need to propagate to all DNS servers and finally your own box.

The updating takes time. Maybe because a human has to enter the new IP addresses in some management console at an ISP hosting the DNS.