<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">On Oct 5, 2015, at 11:51 PM, Harshith Mulky <<a href="mailto:harshith.mulky@outlook.com" class="">harshith.mulky@outlook.com</a>> wrote:<br class=""><div><blockquote type="cite" class="">Let us say we are having a FQDN and we need to Resolve it. It goes through the procedure of determining the IP and Port using NAPTR/SRV/A query mechanisms<br class=""><div class=""><div class="hmmessage"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><br class="">The question I have is if I have a FQDN with a Port Number already determined, will it go through the Procedure of NAPTR/SRV/A query (or) simply do a A query (or) Is this left to the client to apply the Logic?<br class=""></div></div></div></div></div></blockquote></div><br class=""><style class=""><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style><style class=""><!--
.ExternalClass .ecxhmmessage P {
padding:0px;
}
.ExternalClass body.ecxhmmessage {
font-size:12pt;
font-family:Calibri;
}
--></style><div class="">The client must supply the logic. DNS is conceptually a simple database service — ask a question, get an answer. The logic of using NAPTR records, SRV records, A records, AAAA records, and CNAME records is mostly handled by the client. (CNAME and DNAME records are the primary exception, triggering extra processing on the recursive name server.)</div><div class=""><br class=""></div><div class="">Chris</div></body></html>