Scribd
Upload
101 views

E-Mail & DNS

This document discusses electronic mail (e-mail) and its architecture. E-mail has become one of the most popular Internet services, though its designers likely did not foresee this. Its architecture includes several components like user agents (UAs), mail transfer agents (MTAs), and mail access agents (MAAs) that work together depending on whether the sender and receiver are on the same or different systems and how they connect to mail servers. The document provides figures and notes to illustrate the different scenarios and components involved in e-mail communication.

Uploaded by

Prathyusha Vallabhadas
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
101 views

E-Mail & DNS

This document discusses electronic mail (e-mail) and its architecture. E-mail has become one of the most popular Internet services, though its designers likely did not foresee this. Its architecture includes several components like user agents (UAs), mail transfer agents (MTAs), and mail access agents (MAAs) that work together depending on whether the sender and receiver are on the same or different systems and how they connect to mail servers. The document provides figures and notes to illustrate the different scenarios and components involved in e-mail communication.

Uploaded by

Prathyusha Vallabhadas
Copyright
© © All Rights Reserved
Available Formats
Download as PPT, PDF, TXT or read online on Scribd
You are on page 1/ 42

ELECTRONIC MAIL

One of the most popular Internet services is electronic


mail (e-mail). The designers of the Internet probably
never imagined the popularity of this application
program. Its architecture consists of several
components that we discuss in this chapter.

26.1
Figure 26.6 First scenario in electronic mail

26.2
Note

When the sender and the receiver of an


e-mail are on the same system,
we need only two user agents.

26.3
Figure 26.7 Second scenario in electronic mail

26.4
Note

When the sender and the receiver of an


e-mail are on different systems, we
need two UAs and a pair of
MTAs (client and server).

26.5
Figure 26.8 Third scenario in electronic mail

26.6
Note

When the sender is connected to the


mail server via a LAN or a WAN,
we need two UAs and two pairs
of MTAs (client and server).

26.7
Figure 26.9 Fourth scenario in electronic mail

26.8
Figure 26.10 Push versus pull in electronic email

26.9
Note

When both sender and receiver are


connected to the mail server via
a LAN or a WAN, we need two
UAs, two pairs of MTAs
and a pair of MAAs.
This is the most common situation
today.

26.10
Figure 26.11 Services of user agent

26.11
Note

Some examples of command-driven


user agents are mail, pine,
and elm.

26.12
Note

Some examples of GUI-based user


agents are Eudora, Outlook, and
Netscape.

26.13
Figure 26.12 Format of an e-mail

26.14
Figure 26.13 E-mail address

26.15
Figure 26.17 Commands and responses

26.16
Figure 26.18 Command format

26.17
Table 26.7 Commands

26.18
NAME SPACE

To be unambiguous, the names assigned to machines


must be carefully selected from a name space with
complete control over the binding between the names
and IP addresses.

25.19
DOMAIN NAME SPACE

• In the postal system


• the country, state or province, city, street
address and name of the addressee.

• Hierarchical addressing ensures that there is NO


confusion between the
• Street no. 2 in Azad Nagar in Jalandhar,
Punjab and the Street no. 2 in Azad Nagar
in Ambala, Haryana.

• DNS works the same way.


25.20
Figure 25.1 Example of using the DNS service

25.21
Figure 25.2 Domain name space

25.22
Figure 25.3 Domain names and labels

25.23
Flat Name Space vs Hierarchical Name Space
 Flat Name Space: A name is assigned to an address. A
name in this space is a sequence of characters without
structure.

 Disadvantage: It cannot be used in a large system such as


the Internet because it must be centrally controlled to
avoid ambiguity and duplication.

 Hierarchical Name Space: Each name is made of several


parts. The first part can define the nature of the
organization, the second part can define the name of
an organization, the third part can define departments
in the organization, and so on. In this case, the
authority to assign and control the name spaces can be
decentralized.
26.24
Fully Qualified Domain Name

 If a label is terminated by a null string, it


is called a FQDN.
 An FQDN is a domain name that contains
the full name of a host.
 It contains all labels, from the most
specific to the most general, that uniquely
define the name of the host.
 For example, the domain name
challenger.ate.tbda.edu
26.25
Partially Qualified Domain Name
 If a label is not terminated by a null string, it is called a
PQDN.
 A PQDN starts from a node, but it does not reach the
root.
 It is used when the name to be resolved belongs to the
same site as the client.
 Here the resolver can supply the missing part, called the
suffix, to create an FQDN. For example, if a user at the
jhda.edu. site wants to get the IP address of the
challenger computer, he or she can define the partial
name
challenger The DNS client adds the suffix atc.jhda.edu.
before passing the address to the DNS server.
26.26
Figure 25.4 FQDN and PQDN

25.27
Figure 25.5 Domains

25.28
DISTRIBUTION OF NAME SPACE

The information contained in the domain name space


must be stored. However, it is very inefficient and also
unreliable to have just one computer store such a huge
amount of information. In this section, we discuss the
distribution of the domain name space.

25.29
Hierarchy of name servers

25.30
26.31
Zones and domains

25.32
Note

A primary server loads all information


from the disk file; the secondary server
loads all information from
the primary server.

When the secondary downloads


information from the primary, it is called
zone transfer.
25.33
DNS IN THE INTERNET

DNS is a protocol that can be used in different


platforms. In the Internet, the domain name space
(tree) is divided into three different sections:

generic domains
country domains
inverse domain.

25.34
DNS IN THE INTERNET

25.35
Generic domains

25.36
Table 25.1 Generic domain labels

25.37
Figure 25.10 Country domains

25.38
Figure 25.11 Inverse domain

 The inverse domain is used to map an


address to a name.

 When a server has received a request


from a client to do a task.

 Server has a file that contains a list of


authorized clients, only the IP address of
the client (extracted from the received IP
packet) is listed.

 Server asks its resolver to send a query


to the DNS server to map an address to a
name to determine if the client is on the
authorized list.

 This type of query is called an inverse or


pointer (PTR) query.

25.39
RESOLUTION

Mapping a name to an address or an address to a


name is called name-address resolution.

25.40
Figure 25.12 Recursive resolution

25.41
Figure 25.13 Iterative resolution

25.42

You might also like