On Tue, 2006-03-14 at 14:22 -0800, Erik Nordmark wrote:
> Iljitsch van Beijnum wrote:
[..big snip..]
> > The latter would probably be desireable for sites that want to optimize
> > for TE or want to balance incoming sessions over different hosts.
>
> I'm having a hard time seeing how this can be done without introducing
> several additional SRV lookups; being able to express all these in a
> single SRV lookup would be hard. (Hmm, unless we take the
> _ip.www.example.com hack above and hack it some more by overloading the
> returned port number field to have semantics like the above. At that
> point in time it might be better to introduce a new DNS RR type.)
For that matter, why isn't there an AAAA/A which looks somewhat like:
(PAAAA/PA = Prioritized AAAA/A)
host.example.org PAAAA 100 2001:db8:1000::1
PAAAA 200 2001:db8:2000::2
PAAAA 300 2001:db8:3000::3
Thus giving preference to the ::1 address, if that fails, try ::2 etc.
This would allow one to specify their 'primary' provider and their
backups. One could also mimic SRV completely adding the balancing
options. I actually guess that in many implementations the following
will work already though:
host.example.org SRV 100 50 0 2001:db8:1000::1
SRV 100 50 0 2001:db8:2000::2
SRV 200 20 0 2001:db8:3000::3
Just like folks inserting IP addresses directly in MX's. Most tools use
getaddrinfo() or gethostaddr() or similar to look it up and these
recognize the IP address and use that directly.
Greets,
Jeroen
Attachment:
signature.asc
Description: This is a digitally signed message part