Oct 27 2020 09:21 AM - edited Oct 27 2020 09:22 AM
Hi all,
After running the Microsoft 365 network connectivity test tool located at https://connectivity.office.com I'm getting following 'issue' in the TCP Connection section:
Unblock URL: *.svc.ms
Test FQDN(s) used were: 4-northcentralus1-pushp.svc.ms 6-northcentralus1-pushp.svc.ms
Any pointers on how to fix this and what it means?
Thx,
Mathieu
Oct 28 2020 07:53 AM
@mathieudenys i got the same, got any further with this already?
Oct 29 2020 06:55 AM
Solution@mathieudenys There's an older post on this forum where someone from MS says this is a bug. They later say that it was resolved, but I believe that to be incorrect, as I always get this same message and it doesn't matter what network I run it on, even when there is no sort of filtering in place. It's definitely a bug and can be ignored.
Aug 02 2021 08:15 AM
@sschreffler Its not a bug, some DNS services dont carry the zone for svc.ms E.G Google
nslookup 6-northcentralus1-pushp.svc.ms 8.8.8.8
Server: dns.google
Address: 8.8.8.8
*** dns.google can't find 6-northcentralus1-pushp.svc.ms: Non-existent domain
nslookup 6-northcentralus1-pushp.svc.ms 208.67.222.222
Server: dns.opendns.com
Address: 208.67.222.222
Non-authoritative answer:
Name: b-0013.b-msedge.net
Address: 13.107.6.168
Aliases: 6-northcentralus1-pushp.svc.ms
6-northcentralus1.pushp.svc.ms.b-0013.b-msedge.net
Sep 09 2021 10:40 AM
Oct 29 2020 06:55 AM
Solution@mathieudenys There's an older post on this forum where someone from MS says this is a bug. They later say that it was resolved, but I believe that to be incorrect, as I always get this same message and it doesn't matter what network I run it on, even when there is no sort of filtering in place. It's definitely a bug and can be ignored.