Lines Matching full:cname
115 // If there is a authoritative LocalOnly record that answers questions of type A, AAAA and CNAME
397 LogMsg("AnswerQuestionByFollowingCNAME: %p %##s (%s) NOT following CNAME referral %d%s for %s",
403 // The SameDomainName check above is to ignore bogus CNAME records that point right back at
409 // for either of them. This is not a problem for CNAME loops of two or more records because in
415 // which we would subsequently cancel and retract if the CNAME referral record were removed.
418 LogInfo("AnswerQuestionByFollowingCNAME: %p %##s (%s) following CNAME referral %d for %s",
424 // If a unicast query results in a CNAME that points to a .local, we need to re-try
429 LogInfo("AnswerQuestionByFollowingCNAME: Resolving a .local CNAME %p %##s (%s) Record %s",
1191 // rr->resrec.rdata = MUST be set by client, unless record type is CNAME or PTR and rr->HostTarget is set
3313 // send the AAAA query out which will come back with CNAME and will also answer the "A" query. To prevent that,
3371 // For CNAME results to non-CNAME questions, only inform the client if they explicitly requested that
4567 // Filter the /etc/hosts records - LocalOnly, Unique, A/AAAA/CNAME
4680 // This function is called when /etc/hosts changes and that could affect A, AAAA and CNAME queries
4692 // But this can't prevent a CNAME/AAAA query to not to be sent on the wire. When it is sent on the wire,
6618 // if a CNAME record points to itself, then don't add it to the cache
6621 LogInfo("mDNSCoreReceiveResponse: CNAME loop domain name %##s", m->rec.r.resrec.name->c);
6791 // When we issue a query for A record, the response might contain both a CNAME and A records. Only the CNAME would
6793 // the A record, it does not match the question because the record name here is the CNAME. Hence we try to
8177 // Filter the /etc/hosts records - LocalOnly, Unique, A/AAAA/CNAME
