Searched refs:CNAME (Results 1 – 25 of 28) sorted by relevance
12
345 ei_get_compilerver_from_cxx_version_string("${eigen_cxx_compiler_version_string}" CNAME CVER)346 set(${VAR} "${CNAME}-${CVER}")355 macro(ei_get_compilerver_from_cxx_version_string VERSTRING CNAME CVER)365 set(${CNAME} "llvm-g++")367 set(${CNAME} "llvm-clang++")369 set(${CNAME} "icpc")371 set(${CNAME} "g++")373 set(${CNAME} "_")477 ei_get_compilerver_from_cxx_version_string(${STR} CNAME CVER)478 if((NOT ${REFNAME} STREQUAL ${CNAME}) OR (NOT ${REFVER} STREQUAL ${CVER}))[all …]
38 CNAME = 5 variable100 'CNAME' : CNAME,
108 if rdtype != dns.rdatatype.CNAME:113 dns.rdatatype.CNAME)
18 class CNAME(dns.rdtypes.nsbase.NSBase): class
63 int32_t CNAME(uint32_t remoteSSRC, char cName[RTCP_CNAME_SIZE]) const;
454 EXPECT_EQ(0, rtcp_receiver_->CNAME(kSenderSsrc, cName)); in TEST_F()466 EXPECT_EQ(0, rtcp_receiver_->CNAME(kSenderSsrc, cName)); in TEST_F()473 EXPECT_EQ(-1, rtcp_receiver_->CNAME(kSenderSsrc, cName)); in TEST_F()
511 return rtcp_receiver_.CNAME(remote_ssrc, c_name); in RemoteCNAME()
1427 int32_t RTCPReceiver::CNAME(uint32_t remoteSSRC, in CNAME() function in webrtc::RTCPReceiver
90 * generate local CNAME responses
91 Fixed cacheing of CNAMEs. Previously, a CNAME which pointed201 Re-vamped CNAME processing to cope with RFC 2317's use of329 Fix bug in CNAME chasing code: One CNAME pointing524 caching of RFC 2317 CNAME-PTR records.1290 Fix rare crash associated with long DNS names and CNAME1338 Fix interesting corner case in CNAME handling. This occurs1339 when a CNAME has a target which "shadowed" by a name in1340 /etc/hosts or from DHCP. Resolving the CNAME would sneak1341 the upstream value of the CNAME's target into the cache,1343 resolving the CNAME still gives the unshadowed value. This[all …]
659 msgid "bad CNAME"660 msgstr "mauvais CNAME"663 msgid "duplicate CNAME"664 msgstr "ce CNAME existe d�ja"
643 msgid "bad CNAME"644 msgstr "z�a CNAME"647 msgid "duplicate CNAME"648 msgstr "powt�rzona CNAME"
637 msgid "bad CNAME"641 msgid "duplicate CNAME"
661 msgid "bad CNAME"665 msgid "duplicate CNAME"666 msgstr "CNAME duplicado"
675 msgid "bad CNAME"679 msgid "duplicate CNAME"
753 msgid "bad CNAME"757 msgid "duplicate CNAME"
660 msgid "bad CNAME"664 msgid "duplicate CNAME"
658 msgid "bad CNAME"662 msgid "duplicate CNAME"
34 o ares_parse_a_reply: fix CNAME response parsing521 a CNAME record, this behaviour is defeated since the original query does524 the CNAME.
1848 programmatically-generated CNAME records. For example, if a responder1852 resource records: A CNAME record "X CNAME Y", asserting that the
1966 programmatically-generated CNAME records. For example, if a responder1970 resource records: A CNAME record "X CNAME Y", asserting that the
2302 generated CNAME records. For example, if a responder has an address2306 A CNAME record "X CNAME Y", asserting that the requested name X