Académique Documents
Professionnel Documents
Culture Documents
On considère un réseau local constitué d’un segment Ethernet. Ce réseau local est connecté au
réseau Internet par le biais d’un routeur d’adresse IP 192.55.47.1 et d’adresse MAC
ab:23:f2:45:54:c3 (voir la figure). Ce routeur permet d’accéder au reste de l’Internet. Le
réseau local se voit attribuer le nom de domaine suivant : «univ.fr».
Serveur DNS
192.55.47.20
Ethernet
reste de
l’Internet
192.55.47.1
192.55.47.0
Sur ce réseau local, on connecte un PC fonctionnant sous Linux jouant le rôle de serveur DNS
(Domain Name Server). Un serveur DNS, quand on lui envoie le nom d’une machine
quelconque connectée à l’Internet (par ex. «www.yahoo.com»), retourne l’adresse IP de cette
machine sur le réseau. Le serveur DNS a comme adresse IP 192.55.47.20, comme adresse
MAC 12:34:e3:5a:23:ab, et comme nom «chtulhu.univ.fr». On veut ouvrir une session telnet
sur le serveur DNS à partir du PC d’adresse IP 192.55.47.45. On tape pour cela la commande
«telnet 192.55.47.20». On suppose que le cache ARP de la machine d’adresse IP 192.55.47.45
est vide avant l’exécution de la commande telnet.
TD réseaux 5 -1-
3. Au niveau réseau, quels sont les échanges qui vont se produire pour réaliser cette
commande ?
On veut maintenant ouvrir une session telnet sur une machine de nom «mortimer.epfl.edu» à
partir du PC d’adresse IP 192.55.47.45. Cette machine est connectée à l’Internet, mais est
extérieure au réseau local. On tape la commande «telnet mortimer.epl.edu».
5. Au niveau réseau, quels sont les échanges qui vont se produire pour réaliser cette
commande ?
8. On travaille sur une station Unix du réseau de l'IUT de Saint-Malo. Cette machine
possède un fichier /etc/hosts dont une partie du contenu est donné ci-dessous :
193.52.38.1 iutsm-gw.iutsm.univ-rennes1.fr
193.52.38.3 sehi-1-sm.iutsm.univ-rennes1.fr
193.52.38.4 sehi-2-sm.iutsm.univ-rennes1.fr
193.52.38.5 sehi-3-sm.iutsm.univ-rennes1.fr
193.52.38.6 sehi-4-sm.iutsm.univ-rennes1.fr
193.52.38.7 sehi-5-sm.iutsm.univ-rennes1.fr
193.52.38.28 minos.iutsm.univ-rennes1.fr minos
193.52.38.29 pegase.iutsm.univ-rennes1.fr pegase www ftp mailhost
193.52.38.30 pc-allae.iutsm.univ-rennes1.fr
Commentez ces quelques lignes. D'après vous, quand ce fichier est-il utilisé ? Quand on
tape la commande "telnet minos", le serveur DNS de l'IUT est-il invoqué ?
TD réseaux 5 -2-
12.Une machine, sous un nom donné, peut posséder plusieurs adresses IP. Pour quelle(s)
raison(s) ?
13.On tape la commande "ftp ftp.apple.com" pour se connecter au serveur ftp d'apple. Le
cache arp possède alors deux entrées :
Internet Address Physical Address Type
193.52.38.1 00-00-0c-38-99-0a dynamic
193.52.38.29 00-20-af-df-21-f7 dynamic
A quoi correspond cette deuxième entrée ?
14.Le datagramme Internet suivant correspond à une requête envoyée par le serveur DNS.
Quel type de protocole encapsule ce datagramme IP ?
16.On effectue la même interrogation du DNS peu de temps après. On obtient les échanges
donnée en annexe (trames 5 et 6). Commentez et expliquez.
17.La commande "nslookup" sous Unix permet d'interroger localement un serveur DNS.
Quand on interroge deux fois de suite le serveur DNS pour un même nom de machine,
on obtient la réponse suivante :
Non-authoritative answer:
Name: pascal.ibp.fr
Address: 132.227.77.2
Aliases: ftp.ibp.fr
TD réseaux 5 -3-
18.Il est possible de lancer une option de déboguage pour la commande nslookup. On peut
alors mieux comprendre la nature des données échangées entre le client nslookup et le
serveur DNS. Commentez et expliquez.
pegase:~$ nslookup
;; res_mkquery(0, ftp.apple.com.iutsm.univ-rennes1.fr, 1, 1)
------------
Got answer:
HEADER:
opcode = QUERY, id = 57663, rcode = NXDOMAIN
header flags: response, auth. answer, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 1, additional = 0
QUESTIONS:
ftp.apple.com.iutsm.univ-rennes1.fr, type = A, class = IN
AUTHORITY RECORDS:
-> iutsm.univ-rennes1.fr
ttl = 86400 (1 day)
origin = pegase.iutsm.univ-rennes1.fr
mail addr = allaire.univ-rennes1.fr
serial = 1997070801
refresh = 28800 (8 hours)
retry = 7200 (2 hours)
expire = 3600000 (41 days 16 hours)
minimum ttl = 86400 (1 day)
------------
;; res_mkquery(0, ftp.apple.com, 1, 1)
------------
Got answer:
HEADER:
opcode = QUERY, id = 57664, rcode = NOERROR
header flags: response, want recursion, recursion avail.
questions = 1, answers = 9, authority records = 3, additional = 3
QUESTIONS:
ftp.apple.com, type = A, class = IN
ANSWERS:
-> ftp.apple.com
internet address = 17.254.0.27
ttl = 288 (4 mins 48 secs)
-> ftp.apple.com
internet address = 17.254.0.31
ttl = 288 (4 mins 48 secs)
-> ftp.apple.com
internet address = 17.254.0.32
ttl = 288 (4 mins 48 secs)
-> ftp.apple.com
internet address = 17.254.0.33
ttl = 288 (4 mins 48 secs)
-> ftp.apple.com
internet address = 17.254.0.22
ttl = 288 (4 mins 48 secs)
-> ftp.apple.com
internet address = 17.254.0.23
ttl = 288 (4 mins 48 secs)
-> ftp.apple.com
TD réseaux 5 -4-
internet address = 17.254.0.24
ttl = 288 (4 mins 48 secs)
-> ftp.apple.com
internet address = 17.254.0.25
ttl = 288 (4 mins 48 secs)
-> ftp.apple.com
internet address = 17.254.0.26
ttl = 288 (4 mins 48 secs)
AUTHORITY RECORDS:
-> APPLE.com
nameserver = NSERVER.APPLE.com
ttl = 148747 (1 day 17 hours 19 mins 7 secs)
-> APPLE.com
nameserver = NSERVER2.APPLE.com
ttl = 148747 (1 day 17 hours 19 mins 7 secs)
-> APPLE.com
nameserver = NSERVER.EURO.APPLE.com
ttl = 148747 (1 day 17 hours 19 mins 7 secs)
ADDITIONAL RECORDS:
-> NSERVER.APPLE.com
internet address = 17.254.0.50
ttl = 148747 (1 day 17 hours 19 mins 7 secs)
-> NSERVER2.APPLE.com
internet address = 17.254.0.59
ttl = 148747 (1 day 17 hours 19 mins 7 secs)
-> NSERVER.EURO.APPLE.com
internet address = 194.151.19.41
ttl = 148747 (1 day 17 hours 19 mins 7 secs)
------------
Non-authoritative answer:
Name: ftp.apple.com
Addresses: 17.254.0.27, 17.254.0.31, 17.254.0.32, 17.254.0.33
17.254.0.22, 17.254.0.23, 17.254.0.24, 17.254.0.25, 17.254.0.26
> exit
19.Sous Unix, un des serveurs de noms le plus utilisé est le programme « bind », qui
apparaît sous le nom « named » dans la liste des processus. Sa configuration de base se
fait au travers d’un fichier « named.conf », placé dans le répertoire /etc. A titre
d’exemple, voici le fichier « named.conf» de pegase.iutsm.univ-rennes1.fr. Analyser et
commenter.
//
// FICHIER D'INITIALISATION POUR LE SERVEUR DE NOMS BIND version 8
//
// Deux domaines geres en tant que serveur primaire :
// - iutsm.univ-rennes1.fr
// - iutsm.etu.univ-rennes1.fr
// Deux serveurs DNS secondaires autorises pour ces deux domaines :
// - resone.univ-rennes1.fr
// - soleil.uvsq.fr
// resone.univ-rennes1.fr (129.20.128.2) est declare "forwarders"
// en tant que serveur "riche en cache".
options {
directory "/var/named";
forwarders {
129.20.128.2;
};
};
zone "." {
TD réseaux 5 -5-
type hint;
file "root.cache";
};
zone "0.0.127.in-addr.arpa" {
type master;
file "pz/0.0.127.in-addr.arpa.header";
};
zone "38.52.193.in-addr.arpa" {
type master;
file "pz/38.52.193.in-addr.arpa.header";
};
zone "128.221.195.in-addr.arpa" {
type master;
file "pz/128.221.195.in-addr.arpa.header";
};
zone "208.20.129.in-addr.arpa" {
type master;
file "pz/208.20.129.in-addr.arpa.header";
};
zone "209.20.129.in-addr.arpa" {
type master;
file "pz/209.20.129.in-addr.arpa.header";
};
zone "210.20.129.in-addr.arpa" {
type master;
file "pz/210.20.129.in-addr.arpa.header";
};
zone "211.20.129.in-addr.arpa" {
type master;
file "pz/211.20.129.in-addr.arpa.header";
};
zone "208.60.148.in-addr.arpa" {
type master;
file "pz/208.60.148.in-addr.arpa.header";
};
zone "209.60.148.in-addr.arpa" {
type master;
file "pz/209.60.148.in-addr.arpa.header";
};
zone "210.60.148.in-addr.arpa" {
type master;
file "pz/210.60.148.in-addr.arpa.header";
};
zone "211.60.148.in-addr.arpa" {
type master;
file "pz/211.60.148.in-addr.arpa.header";
};
zone "iutsm.univ-rennes1.fr" {
type master;
file "pz/iutsm.univ-rennes1.fr.header";
};
zone "iutsm.etu.univ-rennes1.fr" {
type master;
file "pz/iutsm.etu.univ-rennes1.fr.header";
};
TD réseaux 5 -6-
20.Ce fichier renvoie à différents fichiers de configuration, placés dans le répertoire
/var/named/pz. A titre d’exemple, considérer le fichier « 38.52.193.in-
addr.arpa.header » :
$ORIGIN 38.52.193.in-addr.arpa.
;
@ IN SOA pegase.iutsm.univ-rennes1.fr. hostmaster.iutsm.univ-
rennes1.fr.
(
2003091701 ;serial
28600 ;refresh : 8 heures
7200 ;retry : 2 heures
3600000 ;expire : 41 jours 16 heures
86400 ) ;ttl : 1 jour
;
@ IN NS pegase.iutsm.univ-rennes1.fr.
@ IN NS resone.univ-rennes1.fr.
@ IN NS soleil.uvsq.fr.
@ IN MX 10 mailimailo.univ-rennes1.fr.
;
;
$INCLUDE /var/named/pz/38.52.193.in-addr.arpa
Analyser et commenter.
21.Le protocole netbios propose également un service de noms : WINS. En quoi ce service
est-il différent du DNS ?
Trame 1
---------------------------------------Ethernet II--------------------------------------
Destination address = 3ComDF21F7
Source address = 00400549D0E7
Type = 0800 Internet IP(IPv4)
---------------------------------Internet Protocol (IP)---------------------------------
Version = 4
IP header length = 5 (32-bit words, or(20)bytes)
Type of service = 0
000. .... = Precedence (Routine)
...0 .... = Delay, 0=Normal Delay, 1=Low Delay
.... 0... = Throughput, 0=Normal Throughput, 1=High Throughput
.... .0.. = Reliability, 0=Normal Reliability, 1=High Reliability
.... ..0. = Cost, 0=Normal cost, 1=Minimize cost
.... ...0 = Reserved for future use (set to 0)
Total length = 56
Identifier = 3081
Flags = 0
0... .... = Reserved (set to 0)
.0.. .... = (DF)0=May fragment, 1-Don't fragment
..0. .... = (MF)0=Last fragment, 1-More fragments
Fragment offset = 0
Time to live = 32
Protocol = 17 (UDP User Datagram)
Header checksum = BFE4 Computed = BFE4
Source address = 193.52.38.66
Destination address = 193.52.38.29
------------------------------User Datagram Protocol (UDP)------------------------------
Source port = 1087
Destination port = 53 (Domain Name Server)
Length = 36
Header checksum = DD45
--------------------------------Domain Name System (DNS)--------------------------------
Identification = 0001
TD réseaux 5 -7-
Flags, Byte 1 = 1
0... .... = Type: Query
.000 0... = Opcode: 0 - Standard Query (QUERY)
.... .0.. = No Authoritative Answer
.... ..0. = No Truncation
.... ...1 = Recursion Desired (RD)
Flags, Byte 2 = 0
0... .... = No Recursion Available
...0 .... = Unicast Packet
.... 0000 = Return code: 0 - No Error
Question count = 0001
Answer count = 0000
Authority count = 0000
Additional record count = 0000
Question Section:
Name = www.fhg.de
Type = Host Address (Type - A)
Class = Internet (Type - IN)
Trame 2
---------------------------------------Ethernet II--------------------------------------
Destination address = Cisco38990A
Source address = 3ComDF21F7
Type = 0800 Internet IP(IPv4)
---------------------------------Internet Protocol (IP)---------------------------------
Version = 4
IP header length = 5 (32-bit words, or(20)bytes)
Type of service = 0
000. .... = Precedence (Routine)
...0 .... = Delay, 0=Normal Delay, 1=Low Delay
.... 0... = Throughput, 0=Normal Throughput, 1=High Throughput
.... .0.. = Reliability, 0=Normal Reliability, 1=High Reliability
.... ..0. = Cost, 0=Normal cost, 1=Minimize cost
.... ...0 = Reserved for future use (set to 0)
Total length = 56
Identifier = 35724
Flags = 0
0... .... = Reserved (set to 0)
.0.. .... = (DF)0=May fragment, 1-Don't fragment
..0. .... = (MF)0=Last fragment, 1-More fragments
Fragment offset = 0
Time to live = 64
Protocol = 17 (UDP User Datagram)
Header checksum = 1E49 Computed = 1E49
Source address = 193.52.38.29
Destination address = 193.141.40.1
------------------------------User Datagram Protocol (UDP)------------------------------
Source port = 53 (Domain Name Server)
Destination port = 53 (Domain Name Server)
Length = 36
Header checksum = D60E
--------------------------------Domain Name System (DNS)--------------------------------
Identification = 0A2A
Flags, Byte 1 = 0
0... .... = Type: Query
.000 0... = Opcode: 0 - Standard Query (QUERY)
.... .0.. = No Authoritative Answer
.... ..0. = No Truncation
.... ...0 = No Recursion Desired
Flags, Byte 2 = 0
0... .... = No Recursion Available
...0 .... = Unicast Packet
.... 0000 = Return code: 0 - No Error
Question count = 0001
Answer count = 0000
Authority count = 0000
Additional record count = 0000
Question Section:
Name = www.fhg.de
Type = Host Address (Type - A)
Class = Internet (Type - IN)
Trame 3
TD réseaux 5 -8-
---------------------------------------Ethernet II--------------------------------------
Destination address = 3ComDF21F7
Source address = Cisco38990A
Type = 0800 Internet IP(IPv4)
---------------------------------Internet Protocol (IP)---------------------------------
Version = 4
IP header length = 5 (32-bit words, or(20)bytes)
Type of service = 0
000. .... = Precedence (Routine)
...0 .... = Delay, 0=Normal Delay, 1=Low Delay
.... 0... = Throughput, 0=Normal Throughput, 1=High Throughput
.... .0.. = Reliability, 0=Normal Reliability, 1=High Reliability
.... ..0. = Cost, 0=Normal cost, 1=Minimize cost
.... ...0 = Reserved for future use (set to 0)
Total length = 242
Identifier = 989
Flags = 4
0... .... = Reserved (set to 0)
.1.. .... = (DF)0=May fragment, 1-Don't fragment
..0. .... = (MF)0=Last fragment, 1-More fragments
Fragment offset = 0
Time to live = 235
Protocol = 17 (UDP User Datagram)
Header checksum = BA3D Computed = BA3D
Source address = 193.141.40.1
Destination address = 193.52.38.29
------------------------------User Datagram Protocol (UDP)------------------------------
Source port = 53 (Domain Name Server)
Destination port = 53 (Domain Name Server)
Length = 222
Header checksum = 9438
--------------------------------Domain Name System (DNS)--------------------------------
Identification = 0A2A
Flags, Byte 1 = 84
1... .... = Type: Response
.000 0... = Opcode: 0 - Standard Query (QUERY)
.... .1.. = Authoritative Answer (AA)
.... ..0. = No Truncation
.... ...0 = No Recursion Desired
Flags, Byte 2 = 80
1... .... = Recursion Available (RA)
...0 .... = Unicast Packet
.... 0000 = Return code: 0 - No Error
Question count = 0001
Answer count = 0002
Authority count = 0004
Additional record count = 0004
Question Section:
Name = www.fhg.de
Type = Host Address (Type - A)
Class = Internet (Type - IN)
Answer section:
Name = www.fhg.de
Type = Canonical name for alias (Type - CNAME)
Class = Internet (Type - IN)
Time-to-live = 86400 (Seconds)
Data length = 11
Canonical name = mm.fhg.de
Answer section:
Name = mm.fhg.de
Type = Host Address (Type - A)
Class = Internet (Type - IN)
Time-to-live = 86400 (Seconds)
Data length = 4
Host address = 153.96.1.10
Authority section:
Name = fhg.de
Type = Authoritative Name Server (Type - NS)
Class = Internet (Type - IN)
Time-to-live = 86400 (Seconds)
Data length = 5
Authoritative name server = ns.fhg.de
Authority section:
Name = fhg.de
TD réseaux 5 -9-
Type = Authoritative Name Server (Type - NS)
Class = Internet (Type - IN)
Time-to-live = 86400 (Seconds)
Data length = 6
Authoritative name server = ns1.fhg.de
Authority section:
Name = fhg.de
Type = Authoritative Name Server (Type - NS)
Class = Internet (Type - IN)
Time-to-live = 86400 (Seconds)
Data length = 6
Authoritative name server = DNS.fhg.de
Authority section:
Name = fhg.de
Type = Authoritative Name Server (Type - NS)
Class = Internet (Type - IN)
Time-to-live = 86400 (Seconds)
Data length = 18
Authoritative name server = xlink1.xlink.net
Additional records section:
Name = ns.fhg.de
Type = Host Address (Type - A)
Class = Internet (Type - IN)
Time-to-live = 86400 (Seconds)
Data length = 4
Host address = 153.96.1.1
Additional records section:
Name = ns1.fhg.de
Type = Host Address (Type - A)
Class = Internet (Type - IN)
Time-to-live = 86400 (Seconds)
Data length = 4
Host address = 153.96.1.2
Additional records section:
Name = DNS.fhg.de
Type = Host Address (Type - A)
Class = Internet (Type - IN)
Time-to-live = 86400 (Seconds)
Data length = 4
Host address = 192.44.37.1
Additional records section:
Name = xlink1.xlink.net
Type = Host Address (Type - A)
Class = Internet (Type - IN)
Time-to-live = 86400 (Seconds)
Data length = 4
Host address = 193.141.40.1
Trame 4
---------------------------------------Ethernet II--------------------------------------
Destination address = 00400549D0E7
Source address = 3ComDF21F7
Type = 0800 Internet IP(IPv4)
---------------------------------Internet Protocol (IP)---------------------------------
Version = 4
IP header length = 5 (32-bit words, or(20)bytes)
Type of service = 0
000. .... = Precedence (Routine)
...0 .... = Delay, 0=Normal Delay, 1=Low Delay
.... 0... = Throughput, 0=Normal Throughput, 1=High Throughput
.... .0.. = Reliability, 0=Normal Reliability, 1=High Reliability
.... ..0. = Cost, 0=Normal cost, 1=Minimize cost
.... ...0 = Reserved for future use (set to 0)
Total length = 242
Identifier = 35725
Flags = 0
0... .... = Reserved (set to 0)
.0.. .... = (DF)0=May fragment, 1-Don't fragment
..0. .... = (MF)0=Last fragment, 1-More fragments
Fragment offset = 0
Time to live = 64
Protocol = 17 (UDP User Datagram)
Header checksum = 1FA6 Computed = 1FA6
Source address = 193.52.38.29
TD réseaux 5 -10-
Destination address = 193.52.38.66
------------------------------User Datagram Protocol (UDP)------------------------------
Source port = 53 (Domain Name Server)
Destination port = 1086
Length = 222
Header checksum = 9B70
--------------------------------Domain Name System (DNS)--------------------------------
Identification = 0001
Flags, Byte 1 = 85
1... .... = Type: Response
.000 0... = Opcode: 0 - Standard Query (QUERY)
.... .1.. = Authoritative Answer (AA)
.... ..0. = No Truncation
.... ...1 = Recursion Desired (RD)
Flags, Byte 2 = 80
1... .... = Recursion Available (RA)
...0 .... = Unicast Packet
.... 0000 = Return code: 0 - No Error
Question count = 0001
Answer count = 0002
Authority count = 0004
Additional record count = 0004
Question Section:
Name = www.fhg.de
Type = Host Address (Type - A)
Class = Internet (Type - IN)
Answer section:
Name = www.fhg.de
Type = Canonical name for alias (Type - CNAME)
Class = Internet (Type - IN)
Time-to-live = 86400 (Seconds)
Data length = 11
Canonical name = mm.fhg.de
Answer section:
Name = mm.fhg.de
Type = Host Address (Type - A)
Class = Internet (Type - IN)
Time-to-live = 86400 (Seconds)
Data length = 4
Host address = 153.96.1.10
Authority section:
Name = fhg.de
Type = Authoritative Name Server (Type - NS)
Class = Internet (Type - IN)
Time-to-live = 86400 (Seconds)
Data length = 5
Authoritative name server = ns.fhg.de
Authority section:
Name = fhg.de
Type = Authoritative Name Server (Type - NS)
Class = Internet (Type - IN)
Time-to-live = 86400 (Seconds)
Data length = 6
Authoritative name server = ns1.fhg.de
Authority section:
Name = fhg.de
Type = Authoritative Name Server (Type - NS)
Class = Internet (Type - IN)
Time-to-live = 86400 (Seconds)
Data length = 6
Authoritative name server = DNS.fhg.de
Authority section:
Name = fhg.de
Type = Authoritative Name Server (Type - NS)
Class = Internet (Type - IN)
Time-to-live = 86400 (Seconds)
Data length = 18
Authoritative name server = xlink1.xlink.net
Additional records section:
Name = ns.fhg.de
Type = Host Address (Type - A)
Class = Internet (Type - IN)
Time-to-live = 86400 (Seconds)
Data length = 4
Host address = 153.96.1.1
TD réseaux 5 -11-
Additional records section:
Name = ns1.fhg.de
Type = Host Address (Type - A)
Class = Internet (Type - IN)
Time-to-live = 86400 (Seconds)
Data length = 4
Host address = 153.96.1.2
Additional records section:
Name = DNS.fhg.de
Type = Host Address (Type - A)
Class = Internet (Type - IN)
Time-to-live = 86400 (Seconds)
Data length = 4
Host address = 192.44.37.1
Additional records section:
Name = xlink1.xlink.net
Type = Host Address (Type - A)
Class = Internet (Type - IN)
Time-to-live = 86400 (Seconds)
Data length = 4
Host address = 193.141.40.1
Trame 5
---------------------------------------Ethernet II--------------------------------------
Destination address = 3ComDF21F7
Source address = 00400549D0E7
Type = 0800 Internet IP(IPv4)
---------------------------------Internet Protocol (IP)---------------------------------
Version = 4
IP header length = 5 (32-bit words, or(20)bytes)
Type of service = 0
000. .... = Precedence (Routine)
...0 .... = Delay, 0=Normal Delay, 1=Low Delay
.... 0... = Throughput, 0=Normal Throughput, 1=High Throughput
.... .0.. = Reliability, 0=Normal Reliability, 1=High Reliability
.... ..0. = Cost, 0=Normal cost, 1=Minimize cost
.... ...0 = Reserved for future use (set to 0)
Total length = 56
Identifier = 3081
Flags = 0
0... .... = Reserved (set to 0)
.0.. .... = (DF)0=May fragment, 1-Don't fragment
..0. .... = (MF)0=Last fragment, 1-More fragments
Fragment offset = 0
Time to live = 32
Protocol = 17 (UDP User Datagram)
Header checksum = BFE4 Computed = BFE4
Source address = 193.52.38.66
Destination address = 193.52.38.29
------------------------------User Datagram Protocol (UDP)------------------------------
Source port = 1087
Destination port = 53 (Domain Name Server)
Length = 36
Header checksum = DD45
--------------------------------Domain Name System (DNS)--------------------------------
Identification = 0001
Flags, Byte 1 = 1
0... .... = Type: Query
.000 0... = Opcode: 0 - Standard Query (QUERY)
.... .0.. = No Authoritative Answer
.... ..0. = No Truncation
.... ...1 = Recursion Desired (RD)
Flags, Byte 2 = 0
0... .... = No Recursion Available
...0 .... = Unicast Packet
.... 0000 = Return code: 0 - No Error
Question count = 0001
Answer count = 0000
Authority count = 0000
Additional record count = 0000
Question Section:
Name = www.fhg.de
Type = Host Address (Type - A)
TD réseaux 5 -12-
Class = Internet (Type - IN)
Trame 6
---------------------------------------Ethernet II--------------------------------------
Destination address = 00400549D0E7
Source address = 3ComDF21F7
Type = 0800 Internet IP(IPv4)
---------------------------------Internet Protocol (IP)---------------------------------
Version = 4
IP header length = 5 (32-bit words, or(20)bytes)
Type of service = 0
000. .... = Precedence (Routine)
...0 .... = Delay, 0=Normal Delay, 1=Low Delay
.... 0... = Throughput, 0=Normal Throughput, 1=High Throughput
.... .0.. = Reliability, 0=Normal Reliability, 1=High Reliability
.... ..0. = Cost, 0=Normal cost, 1=Minimize cost
.... ...0 = Reserved for future use (set to 0)
Total length = 242
Identifier = 35726
Flags = 0
0... .... = Reserved (set to 0)
.0.. .... = (DF)0=May fragment, 1-Don't fragment
..0. .... = (MF)0=Last fragment, 1-More fragments
Fragment offset = 0
Time to live = 64
Protocol = 17 (UDP User Datagram)
Header checksum = 1FA5 Computed = 1FA5
Source address = 193.52.38.29
Destination address = 193.52.38.66
------------------------------User Datagram Protocol (UDP)------------------------------
Source port = 53 (Domain Name Server)
Destination port = 1087
Length = 222
Header checksum = B1B7
--------------------------------Domain Name System (DNS)--------------------------------
Identification = 0001
Flags, Byte 1 = 81
1... .... = Type: Response
.000 0... = Opcode: 0 - Standard Query (QUERY)
.... .0.. = No Authoritative Answer
.... ..0. = No Truncation
.... ...1 = Recursion Desired (RD)
Flags, Byte 2 = 80
1... .... = Recursion Available (RA)
...0 .... = Unicast Packet
.... 0000 = Return code: 0 - No Error
Question count = 0001
Answer count = 0002
Authority count = 0004
Additional record count = 0004
Question Section:
Name = www.fhg.de
Type = Host Address (Type - A)
Class = Internet (Type - IN)
Answer section:
Name = www.fhg.de
Type = Canonical name for alias (Type - CNAME)
Class = Internet (Type - IN)
Time-to-live = 86391 (Seconds)
Data length = 11
Canonical name = mm.fhg.de
Answer section:
Name = mm.fhg.de
Type = Host Address (Type - A)
Class = Internet (Type - IN)
Time-to-live = 86391 (Seconds)
Data length = 4
Host address = 153.96.1.10
Authority section:
Name = fhg.de
Type = Authoritative Name Server (Type - NS)
Class = Internet (Type - IN)
Time-to-live = 86391 (Seconds)
TD réseaux 5 -13-
Data length = 5
Authoritative name server = ns.fhg.de
Authority section:
Name = fhg.de
Type = Authoritative Name Server (Type - NS)
Class = Internet (Type - IN)
Time-to-live = 86391 (Seconds)
Data length = 6
Authoritative name server = ns1.fhg.de
Authority section:
Name = fhg.de
Type = Authoritative Name Server (Type - NS)
Class = Internet (Type - IN)
Time-to-live = 86391 (Seconds)
Data length = 6
Authoritative name server = DNS.fhg.de
Authority section:
Name = fhg.de
Type = Authoritative Name Server (Type - NS)
Class = Internet (Type - IN)
Time-to-live = 86391 (Seconds)
Data length = 18
Authoritative name server = xlink1.xlink.net
Additional records section:
Name = ns.fhg.de
Type = Host Address (Type - A)
Class = Internet (Type - IN)
Time-to-live = 86391 (Seconds)
Data length = 4
Host address = 153.96.1.1
Additional records section:
Name = ns1.fhg.de
Type = Host Address (Type - A)
Class = Internet (Type - IN)
Time-to-live = 86391 (Seconds)
Data length = 4
Host address = 153.96.1.2
Additional records section:
Name = DNS.fhg.de
Type = Host Address (Type - A)
Class = Internet (Type - IN)
Time-to-live = 86391 (Seconds)
Data length = 4
Host address = 192.44.37.1
Additional records section:
Name = xlink1.xlink.net
Type = Host Address (Type - A)
Class = Internet (Type - IN)
Time-to-live = 86391 (Seconds)
Data length = 4
Host address = 193.141.40.1
TD réseaux 5 -14-