RFC 3958:Domain-Based Application Service Location...
RFC-Ref

DNS


Click on the red underlined text to get to the source

... port. As discussed in section 5, existing approaches to using DNS records for dynamically determining the current host for a given application ...
... 5] and SRV ([3]) DNS resource records. This can be viewed as a more general version of the use of SRV ...


... (contained in the NAPTR records) are used to determine the successive DNS lookups until a desirable target is found. ...
... S-NAPTR, the REPLACEMENT field is used as the target of the next DNS lookup -- for NAPTR RRs. ...
... processing rules. In the case of an "S" flag, the REPLACEMENT field is used as the target of a DNS query for SRV RRs, ...
... o the S-NAPTR-designated DNS lookup fails to yield expected results -- e.g., no A RR for an "A" target ...
... domain of a named application service. The first DNS query is for the NAPTR RRs ...


... all the features of NAPTR resource records, it is not intended to imply that DNS resolvers should fail to implement all aspects of the NAPTR RR ...
... As noted in section 8, use of the DNS for server location increases the importance of using protocol ...


... o The server may be operated by a completely different organization without having to list the details of that organization's DNS setup (SRVs). ...
... The purpose here is to define a single, common mechanism (the DDDS application) to use NAPTR when all that is desired is simple DNS- based location of services. This should be easy for applications to ...


... DDDS application ([6]). The DDDS DNS database requires each DDDS application ...
... [5] specifies that a DDDS Database using the NAPTR DNS resource record contain the rewrite rules. The Keys for this database are encoded as domain ...
... requested. DNS servers MAY interpret Flag values and use that information to include appropriate NAPTR, SRV ...
... SRV, or A records in the Additional Information portion of the DNS packet. Clients are encouraged to check for additional information but are not required to do so. See ...
... information on NAPTR records and the Additional Information section of a DNS response packet. ...


... application service location is only as good as the security of the DNS queries along the way. If any of them is compromised, bogus NAPTR and SRV records ...
... discussion of the security threats pertaining to DNS can be found in [11]. ...
... 11]. To protect against DNS-vectored attacks, secured DNS (DNSSEC ...
... To protect against DNS-vectored attacks, secured DNS (DNSSEC) [12] ...
... 12] can be used to ensure the validity of the DNS records received. Whether or not DNSSEC ...


... Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR for specifying the location of services (DNS SRV ...
... DNS RR for specifying the location of services (DNS SRV)", RFC 2782prop, February 2000. ...
... Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database", RFC 3403prop, October 2002. ...
... Arends, R., Larson, M., Austein, R., and D. Massey, "Protocol Modifications for the DNS Security Extensions", Work in Progress, May 2004. ...


... o entwine the application-specific protocol with the DNS lookup and RRset processing described in the pseudocode ...



Google
Web
RFC-Ref