[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [public-dns-discuss] DNS64 Not Resolving Addresses



By "outage" I was referring to the failure to respond to DNS that you
reported.  My apologies for the imprecise, overloaded term.

Best of luck.
On Sun, 17 Jun 2018 at 21:12, Jeffry Handal <jhandal11 AT gmail.com> wrote:
>
> Erik,
>
> I just opened a ticket with Comcast and hope it gets to the proper group.
>
> If I log into the  Cisco network via VPN, the DNS64 server works. So, it
> has to be something inside the Comcast network.
>
> Where did you see the outage you mentioned in the previous email?
>
>
> Regards,
>
> Jeffry J. Handal
>
> On 6/16/18 6:06 AM, Erik Kline wrote:
> > Hmmm.  From Japan:
> >
> > dig -t AAAA ipv4.google.com @2001:4860:4860::6464
> >
> > ; <<>> DiG 9.10.6 <<>> -t AAAA ipv4.google.com @2001:4860:4860::6464
> > ;; global options: +cmd
> > ;; Got answer:
> > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16110
> > ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
> >
> > ;; OPT PSEUDOSECTION:
> > ; EDNS: version: 0, flags:; udp: 512
> > ;; QUESTION SECTION:
> > ;ipv4.google.com. IN AAAA
> >
> > ;; ANSWER SECTION:
> > ipv4.google.com. 21599 IN CNAME ipv4.l.google.com.
> > ipv4.l.google.com. 299 IN AAAA 64:ff9b::acd9:188e
> >
> > ;; Query time: 48 msec
> > ;; SERVER: 2001:4860:4860::6464#53(2001:4860:4860::6464)
> > ;; WHEN: Sat Jun 16 19:58:12 JST 2018
> > ;; MSG SIZE  rcvd: 93
> >
> > "dig any cnn.com +trace +all @2001:4860:4860::6464" is also quite voluminous.
> >
> > Are you still seeing an outage from your location? (whois suggests:
> >
> > NetName:        HOUSTON-RPD-V6-2
> > NetHandle:      NET6-2601-2C0-1
> > Parent:         COMCAST6NET (NET6-2601-1)
> >
> > but that's not necessarily authoritative)
> > On Sat, 16 Jun 2018 at 14:45, Jeffry Handal <jhandal11 AT gmail.com> wrote:
> >> Erik and team,
> >>
> >>
> >>
> >> The public DNS64 resolvers are pingable but do not resolve. The
> >> following simple test is coming from an IPv6-only network that is behind
> >> NAT64.
> >>
> >> ping6 2001:4860:4860::6464
> >> PING6(56=40+8+8 bytes) 2601:2c3:887f:5f73:11b7:5c86:b051:5c2c -->
> >> 2001:4860:4860::6464
> >> 16 bytes from 2001:4860:4860::6464, icmp_seq=0 hlim=42 time=133.313 ms
> >> 16 bytes from 2001:4860:4860::6464, icmp_seq=1 hlim=42 time=25.670 ms
> >>
> >> ping6 2001:4860:4860::64
> >> PING6(56=40+8+8 bytes) 2601:2c3:887f:5f73:11b7:5c86:b051:5c2c -->
> >> 2001:4860:4860::64
> >> 16 bytes from 2001:4860:4860::64, icmp_seq=0 hlim=44 time=635.711 ms
> >> 16 bytes from 2001:4860:4860::64, icmp_seq=3 hlim=44 time=1911.751 ms
> >> 16 bytes from 2001:4860:4860::64, icmp_seq=4 hlim=44 time=915.951 ms
> >> 16 bytes from 2001:4860:4860::64, icmp_seq=5 hlim=44 time=24.304 ms
> >> 16 bytes from 2001:4860:4860::64, icmp_seq=6 hlim=44 time=23.048 ms
> >>
> >> ping6 google.com
> >> ping6: getaddrinfo -- nodename nor servname provided, or not known
> >>
> >>
> >> dig google.com @2001:4860:4860::6464
> >>
> >>
> >>    nslookup
> >>   > server 2001:4860:4860::6464
> >> Default server: 2001:4860:4860::6464
> >> Address: 2001:4860:4860::6464#53
> >>   > google.com
> >>
> >>
> >>    dig any cnn.com +trace +all
> >>
> >> ; <<>> DiG 9.8.3-P1 <<>> any cnn.com +trace +all
> >> ;; global options: +cmd
> >> ;; connection timed out; no servers could be reached
> >>
> >>
> >> cat /etc/resolv.conf
> >> #
> >> # Mac OS X Notice
> >> #
> >> # This file is not used by the host name and address resolution
> >> # or the DNS query routing mechanisms used by most processes on
> >> # this Mac OS X system.
> >> #
> >> # This file is automatically generated.
> >> #
> >> nameserver 2001:4860:4860::6464
> >> nameserver 2001:4860:4860::64
> >>
> >>
> >>
> >> Thank you in advance for the guidance.
> >>
> >>
> >>
> >> --
> >> Jeffry J. Handal
> >>
> >> --
> >> --
> >> ========================================================
> >> You received this message because you are subscribed to the Google
> >> Groups "public-dns-discuss" group.
> >> To post to this group, send email to public-dns-discuss AT googlegroups.com
> >> To unsubscribe from this group, send email to
> >> public-dns-discuss+unsubscribe AT googlegroups.com
> >> For more options, visit this group at
> >> http://groups.google.com/group/public-dns-discuss
> >> For more information on Google Public DNS, please visit
> >> http://developers.google.com/speed/public-dns
> >> ========================================================
> >> ---
> >> You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.
> >> To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsubscribe AT googlegroups.com.
> >> For more options, visit https://groups.google.com/d/optout.
>

-- 
-- 
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dns-discuss AT googlegroups.com
To unsubscribe from this group, send email to 
public-dns-discuss+unsubscribe AT googlegroups.com
For more options, visit this group at
http://groups.google.com/group/public-dns-discuss
For more information on Google Public DNS, please visit
http://developers.google.com/speed/public-dns
========================================================
--- 
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsubscribe AT googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature