Posted by TYAlbert on June 19, 2011 at 01:18:55:
In Reply to: escort services utrect posted by escort shemale review on March 27, 2011 at 10:56:59:
DNS was designed to be extensible for new applications via new record types, but the protocol mandates case-insensitivity for domain names. This is useful for hostname lookups, but it could be handled purely on the client side. Building it into the protocol reduces the usefulness of DNS: e.g., looking up the name of the host with address 119.120.121.122 could have use the name z.y.x.w.in-addr.arpa instead of the slightly lengthier and costlier 122.121.120.119.in-addr.arpa.
CNAMEs are unnecessary: two domain names can have the same records without building this referencing into the protocol. CNAMEs complicate the local lookup algorithm for servers. CNAME records might also form a loop, or they might refer to nonexistent names.
A misconfigured or malicious server can respond to a query with some false name server or address records appended to the response. According to the original RFCs, clients should trust these records. Fortunately, modern clients trust records from the cwru.eduname servers only when they belong to names in the cwru.edu domain. BIND adopted a different solution to this problem earlier on - credibility rules, which have their own problems - and has kept those rules even after adopting the simpler rule given above.[url=http://www.jocuri3d.net ]jocuri 3d[/url]