On 16 Dec 2015, at 15:22, Masataka Ohta wrote: > But, it is stupid to forbid "https://example.com"; and force using > "https://www.example.com";, which means, in a long run, a domain > will support a lot of application protocols. This is why the URI would be: _http._tcp.example.com. IN URI 1 1 "https://www.example.com/"; _http._tcp.www.example.com. IN URI 1 1 "https://www.example.com/"; Etc... Patrik
Attachment:
signature.asc
Description: OpenPGP digital signature