| bucy wrote:] ] The SRV RR allows administrators to use several servers
 ] ] for a single domain, to move services from host to host
 ] ] with little fuss, and to designate some hosts as primary
 ] ] servers for a service and others as backups.
 ]
 ] SRV records might, for example, make sitefinder much less bad;
 ] if the wildcard were
 ]
 ] *.com IN SRV	host=sitefinder.verisign.com port=80 priority=1
 ] weight=1
 ]
 ] rather than
 ]
 ] *.com IN A ...
 ]
 ] I expect that the effects would be much less disruptive, i.e.
 ] browsers would be redirected but everything else would not.
 This is a very interesting approach to the sitefinder problem. John, if you make it to Phreaknic I'm willing to give you some of my speaking time to talk about this. U: I guess one concern is this still creates problems for HTTP based XMLRPC services, which will get a "no XML service on this webserver" error instead of a "host not found" error. (Of course, one could ask that xmlrpc lookup _xmlrpc._tcp.*... RE: A DNS RR for specifying the location of services (DNS SRV) (RFC2782) |