Custom query (937 matches)

Filters
 
or
 
  
 
Columns

Show under each result:

Results (130 - 132 of 937)

← 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 →
Ticket Resolution Summary Owner Reporter
#595 fixed DNS Negative Caching? bzeeb+ietf@… Jason_Livingood@…
Description 
Hi – Can you check behavior of the resolvers for the name techfund.comcast.com? It should return a CNAME and then that resolves an A record:

dhcp-16f4:~ jason$ dig techfund.comcast.com

; <<>> DiG 9.8.3-P1 <<>> techfund.comcast.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 33385
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;techfund.comcast.com. IN A

;; AUTHORITY SECTION:
comcast.com. 2084 IN SOA dns101.comcast.net. domregtech.comcastonline.com. 2009085610 7200 3600 1209600 3600

;; Query time: 1 msec
;; SERVER: 130.129.5.6#53(130.129.5.6)
;; WHEN: Mon Mar 11 14:40:49 2013
;; MSG SIZE  rcvd: 117

dhcp-16f4:~ jason$ dig techfund.comcast.com @8.8.8.8

; <<>> DiG 9.8.3-P1 <<>> techfund.comcast.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 46171
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;techfund.comcast.com. IN A

;; ANSWER SECTION:
techfund.comcast.com. 2581 IN CNAME grants.g.comcast.net.
grants.g.comcast.net. 15 IN A 69.252.208.135

;; Query time: 23 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Mar 11 14:41:00 2013
;; MSG SIZE  rcvd: 88
#596 wontfix IPv6 @ tower1 is broken bzeeb+ietf@… Ronald.vanderPol@…
Description 
spock$ traceroute6 kirk.rvdp.org
traceroute6 to kirk.rvdp.org (2001:980:8fda:1::2) from 2001:df8::64:3963:2c77:82d5:350c, 64 hops max, 12 byte packets
 1  * * *
 2  tserv1.fmt2.he.net  973.264 ms  303.334 ms  301.499 ms
 3  * * *
 4  * * *
 5  * * *
 6  * * *
 7  * *^C
spock$

spock$ ping6 kirk.rvdp.org
PING6(56=40+8+8 bytes) 2001:df8::64:3963:2c77:82d5:350c --> 2001:980:8fda:1::2
^C
--- kirk.rvdp.org ping6 statistics ---
62 packets transmitted, 0 packets received, 100.0% packet loss

spock$ 

spock$ ping6 www.ietf.org
PING6(56=40+8+8 bytes) 2001:df8::64:3963:2c77:82d5:350c --> 2001:1890:123a::1:1e
^C
--- www.ietf.org ping6 statistics ---
21 packets transmitted, 0 packets received, 100.0% packet loss

spock$

spock$ ifconfig -a
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
	options=3<RXCSUM,TXCSUM>
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1 
	inet 127.0.0.1 netmask 0xff000000 
	inet6 ::1 prefixlen 128 
	inet 127.94.0.2 netmask 0xff000000 
	inet 127.94.0.1 netmask 0xff000000 
gif0: flags=8010<POINTOPOINT,MULTICAST> mtu 1280
stf0: flags=0<> mtu 1280
en0: flags=8823<UP,BROADCAST,SMART,SIMPLEX,MULTICAST> mtu 1500
	ether 14:10:9f:f0:0b:4c 
	media: autoselect (<unknown type>)
	status: inactive
p2p0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> mtu 2304
	ether 06:10:9f:f0:0b:4c 
	media: autoselect
	status: inactive
en2: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	options=4<VLAN_MTU>
	ether 00:0e:c6:f1:50:f0 
	inet6 fe80::20e:c6ff:fef1:50f0%en2 prefixlen 64 scopeid 0x7 
	inet 130.129.66.238 netmask 0xfffff800 broadcast 130.129.71.255
	inet6 2001::20e:c6ff:fef1:50f0 prefixlen 64 autoconf 
	inet6 2001::1958:538f:62e6:13d4 prefixlen 64 autoconf temporary 
	inet6 2001:df8::64:20e:c6ff:fef1:50f0 prefixlen 64 autoconf 
	inet6 2001:df8::64:3963:2c77:82d5:350c prefixlen 64 autoconf temporary 
	media: autoselect (100baseTX <full-duplex>)
	status: active
spock$

spock$ date -u
Tue 12 Mar 2013 01:30:34 UTC
spock$


spock$ traceroute kirk.rvdp.org
traceroute to kirk.rvdp.org (82.95.74.93), 64 hops max, 52 byte packets
 1  rtr (130.129.64.1)  0.602 ms  0.403 ms  0.358 ms
 2  75-112-170-148.net.bhntampa.com (75.112.170.148)  10.431 ms  11.579 ms  11.595 ms
 3  bun2.tamp20-car1.bhn.net (71.44.3.73)  9.513 ms
    bun2.tamp20-car2.bhn.net (71.44.3.75)  11.536 ms
    bun2.tamp20-car1.bhn.net (71.44.3.73)  13.647 ms
 4  hun0-0-0-0-tamp20-cbr1.bhn.net (72.31.117.156)  10.130 ms  15.397 ms
    hun0-7-0-0-tamp20-cbr1.bhn.net (72.31.117.164)  9.705 ms
 5  ae-5-10.cr0.dfw10.tbone.rr.com (66.109.6.106)  41.346 ms
    ae-11-11.cr0.dfw10.tbone.rr.com (66.109.10.12)  32.404 ms  32.407 ms
 6  107.14.19.154 (107.14.19.154)  79.610 ms
    107.14.19.156 (107.14.19.156)  87.159 ms  83.176 ms
 7  ae-3-0.cr0.lax30.tbone.rr.com (66.109.6.0)  86.209 ms
    ae-0-0.cr0.hou30.tbone.rr.com (66.109.6.38)  86.192 ms
    ae-3-0.cr0.lax30.tbone.rr.com (66.109.6.0)  80.605 ms
 8  bu-ether14.lsancarc0yw-bcr00.tbone.rr.com (66.109.6.4)  83.112 ms
    ae-4-0.cr0.sjc10.tbone.rr.com (66.109.6.11)  84.241 ms  86.436 ms
 9  25.ge-1-1-0.a0.cdp00.tbone.rr.com (66.109.1.17)  78.655 ms
    ae-3-0.cr0.sjc10.tbone.rr.com (66.109.6.6)  85.654 ms
    25.ge-1-1-0.a0.cdp00.tbone.rr.com (66.109.1.17)  79.352 ms
10  sjca-s1-rou-1001.us.eurorings.net (134.222.248.37)  79.855 ms  79.625 ms
    ae-0-0.pr0.sjc10.tbone.rr.com (66.109.6.141)  77.062 ms
11  sjca-s1-rou-1041.us.eurorings.net (134.222.226.118)  176.515 ms  176.088 ms  177.259 ms
12  sjca-s1-rou-1041.us.eurorings.net (134.222.226.118)  173.568 ms  173.886 ms
    chg-s1-rou-1041.us.eurorings.net (134.222.226.130)  176.146 ms
13  chg-s1-rou-1041.us.eurorings.net (134.222.226.130)  174.702 ms
    ahbn-s1-rou-1041.us.eurorings.net (134.222.229.26)  109.655 ms
    chg-s1-rou-1041.us.eurorings.net (134.222.226.130)  174.610 ms
14  ahbn-s1-rou-1041.us.eurorings.net (134.222.229.26)  91.848 ms  91.085 ms
    ahbn-s1-rou-1001.us.eurorings.net (134.222.231.122)  181.250 ms
15  ahbn-s1-rou-1001.us.eurorings.net (134.222.231.118)  174.876 ms
    ahbn-s1-rou-1001.us.eurorings.net (134.222.226.57)  175.210 ms
    nyk-s1-rou-1021.us.eurorings.net (134.222.228.9)  92.489 ms
16  nyk-s1-rou-1001.us.eurorings.net (134.222.231.237)  176.786 ms
    nyk-s1-rou-1001.us.eurorings.net (134.222.226.1)  177.588 ms
    nyk-s1-rou-1021.us.eurorings.net (134.222.228.9)  90.672 ms
17  asd2-rou-1022.nl.eurorings.net (134.222.226.169)  176.544 ms
    nyk-s1-rou-1001.us.eurorings.net (134.222.226.1)  174.110 ms
    nyk-s1-rou-1001.us.eurorings.net (134.222.231.237)  175.270 ms
18  asd2-rou-1044.nl.eurorings.net (134.222.229.109)  176.360 ms
    asd2-rou-1022.nl.eurorings.net (134.222.226.169)  175.873 ms  176.104 ms
19  134.222.97.18 (134.222.97.18)  176.320 ms  176.457 ms
    asd2-rou-1044.nl.eurorings.net (134.222.229.109)  174.879 ms
20  134.222.97.18 (134.222.97.18)  176.055 ms
    te2-0-0.dr4.d12.xs4all.net (194.109.7.134)  177.814 ms
    134.222.97.18 (134.222.97.18)  175.082 ms
21  kirk.rvdp.org (82.95.74.93)  191.412 ms !X
    te2-0-0.dr4.d12.xs4all.net (194.109.7.134)  175.833 ms
    kirk.rvdp.org (82.95.74.93)  190.935 ms !X
spock$
#606 fixed Fwd: [www.ietf.org/rt #54822] ietf-v6ONLY wifi network is not providing DNS resolver information bzeeb+ietf@… cmorgan@…
Description 

Begin forwarded message:

> From: "Dan York via RT" <mtd@ietf.org>
> Date: March 13, 2013 2:46:22 PM EDT
> To: "AdminCc of www.ietf.org/rt Ticket #54822":;
> Subject: [www.ietf.org/rt #54822] ietf-v6ONLY wifi network is not providing DNS resolver information 
> Reply-To: mtd@ietf.org
> 
> 
> Wed Mar 13 11:46:20 2013: Request 54822 was acted upon.
> Transaction: Ticket created by york@isoc.org
>       Queue: IETF-MeetingCommunication
>     Subject: ietf-v6ONLY wifi network is not providing DNS resolver information
>       Owner: Nobody
>  Requestors: york@isoc.org
>      Status: new
> Ticket <URL: https://www.ietf.org/rt/Ticket/Display.html?id=54822 >
> 
> 
> Hi, when we put our machines on the "ietf-v6ONLY" wife network, they do not get a DNS resolver as part of the RA packets and so they cannot resolve addresses and make connections.  Two of us have manually added "2001:df8:0:5::6" as the DNS server and have then been able to connect to sites.
> 
> We've seen this with Mac laptops running 10.8.x and also with an iPhone.   (I couldn't find anyone in the room with a non-Apple laptop to try it out.)
> 
> It would be great if we could get this fixed.
> 
> Thanks,
> Dan
> 
> --
> Dan York
> Senior Content Strategist, Internet Society
> york@isoc.org   +1-802-735-1624 
> Jabber: york@jabber.isoc.org 
> Skype: danyork   http://twitter.com/danyork
> 
> http://www.internetsociety.org/deploy360/
> 
> 
> Hi, when we put our machines on the "ietf-v6ONLY" wife network, they do not get a DNS resolver as part of the RA packets and so they cannot resolve addresses and make connections.  Two of us have manually added "2001:df8:0:5::6" as the DNS server and have then been able to connect to sites.
> 
> We've seen this with Mac laptops running 10.8.x and also with an iPhone.   (I couldn't find anyone in the room with a non-Apple laptop to try it out.)
> 
> It would be great if we could get this fixed.
> 
> Thanks,
> Dan
> 
> --
> Dan York
> Senior Content Strategist, Internet Society
> york@isoc.org   +1-802-735-1624 
> Jabber: york@jabber.isoc.org 
> Skype: danyork   http://twitter.com/danyork
> 
> http://www.internetsociety.org/deploy360/
>
← 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 →
Note: See TracQuery for help on using queries.