Surely Microsoft has IPv6 connectivity? Is there a problem with my dns, or is Microsoft not available over v6?
Thanks,
Nich
Surely Microsoft has IPv6 connectivity? Is there a problem with my dns, or is Microsoft not available over v6?
Thanks,
Nich
There is
C:\Users\jluthman>dig -t aaaa www.microsoft.com +short
toggle.www.ms.akadns.net.
www.microsoft.com-c.edgekey.net.
www.microsoft.com-c.edgekey.net.globalredir.akadns.net.
e10088.dspb.akamaiedge.net.
2600:1407:10:390::2768
2600:1407:10:389::2768
Josh Luthman
Office: 937-552-2340
Direct: 937-552-2343
1100 Wayne St
Suite 1337
Troy, OH 45373
www.microsoft.com seems to pass these checks for me:
http://ipv6-test.com/validate.php
Perhaps they have some other site that doesn't have it enabled?
- Jared
Which property are you trying to access? Bing? Azure? O365? Something
else?
Microsoft is highly IPv6 connected.
nslookup
set type=AAAA
www.microsoft.com.
Server: 206.83.0.42
Address: 206.83.0.42#53
Non-authoritative answer:
www.microsoft.com canonical name = toggle.www.ms.akadns.net.
toggle.www.ms.akadns.net canonical name = www.microsoft.com-c.edgekey.net.
www.microsoft.com-c.edgekey.net canonical name = www.microsoft.com-c.edgekey.net.globalredir.akadns.net.
www.microsoft.com-c.edgekey.net.globalredir.akadns.net canonical name = e10088.dspb.akamaiedge.net.
e10088.dspb.akamaiedge.net has AAAA address 2600:1406:34:280::2768
e10088.dspb.akamaiedge.net has AAAA address 2600:1406:34:288::2768
What did you lookup?
-mel beckman
In article <C26ABA0F2E16624EA737DB4674DC05AB167B25F3@mail.baec.local> you write:
Surely Microsoft has IPv6 connectivity? Is there a problem with my dns, or is Microsoft not available over v6?
Looks like it's your DNS.
; <<>> DiG 9.10.2-P2 <<>> www.microsoft.com aaaa
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16645
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;www.microsoft.com. IN AAAA
;; ANSWER SECTION:
www.microsoft.com. 3559 IN CNAME toggle.www.ms.akadns.net.
toggle.www.ms.akadns.net. 260 IN CNAME www.microsoft.com-c.edgekey.net.
www.microsoft.com-c.edgekey.net. 21560 IN CNAME www.microsoft.com-c.edgekey.net.globalredir.akadns.net.
www.microsoft.com-c.edgekey.net.globalredir.akadns.net. 3560 IN CNAME e10088.dspb.akamaiedge.net.
e10088.dspb.akamaiedge.net. 9 IN AAAA 2600:1408:10:18f::2768
And there isn't
~$ dig -t AAAA www.microsoft.com +short
toggle.www.ms.akadns.net.
www.microsoft.com-c.edgekey.net.
www.microsoft.com-c.edgekey.net.globalredir.akadns.net.
e10088.dspb.akamaiedge.net.
~$ host e10088.dspb.akamaiedge.net
e10088.dspb.akamaiedge.net has address 23.220.92.16
-Jim P.
I agree that www.microsoft.com passes. But it looks like microsoft.com does not.
sincerely,
Mark Keymer
CFO/COO
Vivio Technologies
BTW, the issue is Google Public DNS:
~$ dig -t AAAA www.microsoft.com +short @2001:4860:4860::8888
toggle.www.ms.akadns.net.
www.microsoft.com-c.edgekey.net.
www.microsoft.com-c.edgekey.net.globalredir.akadns.net.
e10088.dspb.akamaiedge.net.
2600:1408:17:28e::2768
2600:1408:17:280::2768
~$ dig -t AAAA www.microsoft.com +short @8.8.8.8
toggle.www.ms.akadns.net.
www.microsoft.com-c.edgekey.net.
www.microsoft.com-c.edgekey.net.globalredir.akadns.net.
e10088.dspb.akamaiedge.net.
-Jim P.
http://www.mrp.net/cgi-bin/ipv6-status.cgi
SMTP fails for both microsoft.com and xbox.com
live.com has only DNS.
bing.com is a total fail.
Antonio Querubin
e-mail: tony@lavanauts.org
xmpp: antonioquerubin@gmail.com
Hi,
And there isn't
its your DNS
host e10088.dspb.akamaiedge.net
e10088.dspb.akamaiedge.net has address 104.70.251.201
e10088.dspb.akamaiedge.net has IPv6 address 2a02:26f0:cb:2a4::2768
e10088.dspb.akamaiedge.net has IPv6 address 2a02:26f0:cb:29a::2768
alan
Hi,
however...this revelation is shocking...my users can access www.microsoft.com
material via IPv6?? turn this filth off!!
alan
No. My DNS (using the roots) gets it right.
The failure is somewhere between Google Public DNS's IPv4 servers and Akamai.
See my earlier post.
-Jim P.
Hi,
No. My DNS (using the roots) gets it right.
so if you choose google DNS you dont see the right stuff..in which case its your DNS
and not microsoft or Akamai not doing IPv6 same true for OpenDNS? likely...
alan
Dude, it was a test I ran for Nicholas... not my dns. It doesn't
mean something is internal or related to a person just because they
post some data here.
Do I need to spoon feed you the test data that I posted earlier?
-Jim P.
Perhaps the smiley?
I think the general statement is that if someone uses Google DNS they may not be getting the full IPv6 experience which may be surprising to some people.
I’m not sure why google would filter the AAAA responses, or if it’s something else happening but it does make me wonder what other queries that google would get wrong.
- Jared
Umm, ok so your saying you get AAAA records for "microsoft.com"
I am Not talking about www.microsoft.com I agree that it has AAAA records. But the request was for "microsoft.com"
And as noted other domains without the WWW might not have AAAA Records.
Sincerely,
Mark Keymer
CFO/COO
Vivio Technologies
Yes.
-Jim P.
probably not Google DNS filtering
test point 1
$ dig e10088.dspb.akamaiedge.net AAAA @n0dspb.akamaiedge.net
; <<>> DiG 9.10.2-P2 <<>> e10088.dspb.akamaiedge.net AAAA @n0dspb.akamaiedge.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51914
;; flags: qr aa rd ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; WARNING: recursion requested but not available
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;e10088.dspb.akamaiedge.net. IN AAAA
;; AUTHORITY SECTION:
dspb.akamaiedge.net. 1000 IN SOA n0dspb.akamaiedge.net.
hostmaster.akamai.com. 1436917052 1000 1000 1000 1800
;; Query time: 51 msec
;; SERVER: 96.7.248.137#53(96.7.248.137)
;; WHEN: Wed Jul 15 08:37:32 KST 2015
;; MSG SIZE rcvd: 119
test point 2
$ dig e10088.dspb.akamaiedge.net AAAA @n0dspb.akamaiedge.net
; <<>> DiG 9.8.1-P1 <<>> e10088.dspb.akamaiedge.net AAAA @n0dspb.akamaiedge.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 27887
;; flags: qr aa rd; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;e10088.dspb.akamaiedge.net. IN AAAA
;; ANSWER SECTION:
e10088.dspb.akamaiedge.net. 20 IN AAAA 2600:1408:10:18f::2768
e10088.dspb.akamaiedge.net. 20 IN AAAA 2600:1408:10:181::2768
e10088.dspb.akamaiedge.net. 20 IN AAAA 2600:1408:10:188::2768
;; Query time: 18 msec
;; SERVER: 88.221.81.193#53(88.221.81.193)
;; WHEN: Tue Jul 14 16:37:17 2015
;; MSG SIZE rcvd: 128
I get different IPs for n0dspb.akamaiedge.net / n0dscb.akamaiedge.net
every time.
So it depends on source IP of the query and which akamai DNS server is
answering?
Thanks for the tests that show the NODATA is from the authoritative
nameserver. To clarify, Google DNS does not filter either AAAA or any of
these domains.
Yunhong