IPv6 in the enterprise

Doug Barton dougb at dougbarton.us
Thu Apr 21 19:38:13 CEST 2011


On 04/21/2011 00:49, S.P.Zeidler wrote:
> Thus wrote Mikael Abrahamsson (swmike at swm.pp.se):
>
>> On Thu, 21 Apr 2011, S.P.Zeidler wrote:
>>
>>>> Could you please elaborate on what you do when you are "fixing it up"?
>>>
>>> Changing resolv.conf on its clients.
>>
>> That doesn't make sense either for IPv4 or IPv6. You can use
>> function IP addresses for both.
>
> In IPv4 that's not necessary since the IP address is not bound to the
> hardware.

IPv6 addresses don't have to be either.

>>>> I would create a dedicated resolver address (a subnet with the
>>>> address ::53 being the resolver) and then I would move this address
>>>> around when the service changes physical hardware, perhaps even
>>>> having it in multiple places (anycast).
>>>
>>> That is an instance of not using SLAAC, yes.
>>
>> That's an instance of not *only* using EUI64 addresses, with SLAAC
>> you can use ANY address on the subnet that is not already taken.
>
> Sorry I was too terse, obviously. That in an instance of not using SLAAC
> for the address of the resolver that is actually getting used for this
> service.
>
> The original premise was that all hosts including servers should use
> SLAAC. I gave an example where even a very small setup reaches the point
> where that is annoying.

So hopefully by now you realize that this is a bad premise, from which 
many bad conclusions follow? :)


Doug

-- 

	Nothin' ever doesn't change, but nothin' changes much.
			-- OK Go

	Breadth of IT experience, and depth of knowledge in the DNS.
	Yours for the right price.  :)  http://SupersetSolutions.com/



More information about the ipv6-ops mailing list