[dns-operations] An simple observation

[Livingood, Jason]

On 9/25/14, 12:28 PM, "Warren Kumari" <warren at kumari.net> wrote:


>>There is additional operational complexity in running a dual-stack
>>network, which implies some risk, but in my opinion it¹s not serious
>>enough to be a real blocker for most networks.

+1

>>It¹s a little weird to me that google¹s authoritative DNS servers are
>>not addressable over v6.  Their Google Public DNS service does operate
>>over v6, so clearly they have the infrastructure in place.
>
>Google has been focusing on IPv6 for the user first -- for example,
>the Google Public DNS stuff, the web interface, etc. Obviously enough,
>this involved a bunch of infrastructure work...

FWIW you can get to Comcast¹s auth servers via IPv6. When we did v6 on the
recursive side we also did it on the authoritative side at roughly the
same time. It took some upgrading of network equipment in order to get
that to happen - so I suspect that may be a challenge for some other
domains. As Warren also said, organizational / process inertia surely also
plays a role.

; <<>> DiG 9.8.3-P1 <<>> @a.gtld-servers.net comcast.net ns
;; QUESTION SECTION:
;comcast.net.			IN	NS

;; AUTHORITY SECTION:
comcast.net.		172800	IN	NS	dns101.comcast.net.
comcast.net.		172800	IN	NS	dns102.comcast.net.
comcast.net.		172800	IN	NS	dns103.comcast.net.
comcast.net.		172800	IN	NS	dns104.comcast.net.
comcast.net.		172800	IN	NS	dns105.comcast.net.

;; ADDITIONAL SECTION:
dns101.comcast.net.	172800	IN	AAAA	2001:558:fe23:8:69:252:250:103
dns101.comcast.net.	172800	IN	A	69.252.250.103
dns102.comcast.net.	172800	IN	AAAA	2001:558:1004:7:68:87:85:132
dns102.comcast.net.	172800	IN	A	68.87.85.132
dns103.comcast.net.	172800	IN	AAAA	2001:558:1014:c:68:87:76:228
dns103.comcast.net.	172800	IN	A	68.87.76.228
dns104.comcast.net.	172800	IN	AAAA	2001:558:100a:5:68:87:68:244
dns104.comcast.net.	172800	IN	A	68.87.68.244
dns105.comcast.net.	172800	IN	AAAA	2001:558:100e:5:68:87:72:244
dns105.comcast.net.	172800	IN	A	68.87.72.244