Re: [dnsext] we need help to make names the same, was draft-yao-dnsext-identical-resolution-02 comment

[Mark Andrews <[e-mail]>]

In message <[e-mail]>, Danny Mayer writes:
> On 2/17/2011 6:17 PM, Mark Andrews wrote:
> > In message <[e-mail]>, Danny Mayer writes:
> >> Even if there were I'm not convinced that it would be useful since there
> >> is no way on the RHS to specify the path. It can give you a name, a
> >> port, a weight and a priority but no path. There was a proposal for a
> >> URL RR but I cannot find it right now and I don't think the wg is
> >> considering it, at least it's not on the document list.
> >>
> >> Danny
> > 
> > Which can be dealt with entirely at the HTTP/S layer.
> > 
> 
> Not for the purpose I'm looking to use it. For the particular purpose
> the SOAP Servlet path needs to be different from the regular login URL
> and there is no way to express that. It needs to be like an SRV record
> so that the particular SOAP service can be located.
> 
> > People are using CNAME for 
> > 
> > 	site -> hosting server
> > 
> > this include "www.example.net CNAME example.net".
> >  
> > We need to support 
> > 
> > 	site alias -> site { -> hosting server }
> > 
> > 		 CNAME    NEW-TYPE
> > 
> > Additionally people are too lazy to add records for each virtual
> > service in the DNS so they use "* CNAME server" which makes using
> > SRV hard as it requires prepended labels.
> > 
> > To prevent breaking existing clients that use CNAME like NEW-TYPE
> > client would look for NEW-TYPE and only re-write the URL there is
> > a CNAME and a NEW-TYPE returned.
> > 
> > The CNAME would be replace by NEW-TYPE + addresses records to
> > help with the transition.
> > 
> > This is very much like the introduction of MX records.  At
> > some point you stop putting in address records.
> 
> Maybe you can give an example of how to get to the following URL for a
> SOAP Service and a regular login otherwise for the same host and port
> number.
> 
> http://ws.example.net:5678/Ws/SOAPServlet for SOAP Service and continue
> to allow regular http access to the URL http://ws.example.net/Ws/Servlet
> for people who need to just login. This is a real example BTW and the
> current implementation stores the SOAP service URL locally. If I could
> figure out a way of using SRV records I would.

It helps to use the right scheme (RFC3288).  It should be
"soap.beep://ws.example.net:5678/Ws/SOAPServlet" not
"http://ws.example.net:5678/Ws/SOAPServlet".

The client can then make appropriate DNS lookups. 

	_soap_beep._tcp.ws.example.net SRV ....

> Danny
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: [phone]                 INTERNET: [e-mail]
_______________________________________________
dnsext mailing list
[e-mail]
https://www.ietf.org/mailman/listinfo/dnsext