Posts Tagged ‘DNS’

DOMAIN NAMES – CONCEPTS AND FACILITIES

Saturday, November 7th, 2009

These two rfc written November 1987 – Obsoletes: RFCs 882, 883, 973 – QUESTION – Have these been updated – OR are they still the current rfc on the topic of ‘Domain Names‘ ?

http://tools.ietf.org/html/rfc1034

http://tools.ietf.org/html/rfc1035

A host can participate in the domain name system in a number of ways,

depending on whether the host runs programs that retrieve information from the domain system, name servers that answer queries from other hosts, or various combinations of both functions. The simplest, and perhaps most typical, configuration is shown below:

                 Local Host                        |  Foreign
                                                   |
    +---------+               +----------+         |  +--------+
    |         | user queries  |          |queries  |  |        |
    |  User   |-------------->|          |---------|->|Foreign |
    | Program |               | Resolver |         |  |  Name  |
    |         |<--------------|          |<--------|--| Server |
    |         | user responses|          |responses|  |        |
    +---------+               +----------+         |  +--------+
                                |     A            |
                cache additions |     | references |
                                V     |            |
                              +----------+         |
                              |  cache   |         |
                              +----------+         |

DNS cache-poisoning

Wednesday, September 16th, 2009

Curious about how scammers – redirect you to a phishing (Identity-Theft) website?. ..  The DNS service is part of that system (Internet and Internetworking) being maintained by various infractrusture around the globe. More insight into DNS via >>>  (criketondns.com) <<<

BELOW  – QUOTED – FROM BLOG;  – ‘cricketondns.com‘ BY *Cricket Liu*

The consequences of a successful cache-poisoning attack are so dire that describing them inevitably sounds like hyperbole: A hacker who poisons the cache of a recursive name server can redirect users of that name server to web sites that appear identical to those run by their banks, insurers, or governments, where their logins, passwords, and financial information is recorded for later reuse.

He can reroute email through hostile mail servers, where that mail is surreptitiously modified for his gain, or simply copied and stored, with either sender nor recipient aware.