TRENDnet TDM-E400 User's Guide - Page 103

Configuring DNS Server Addresses, About DNS, Assigning DNS Addresses to PCs

Page 103 highlights

9 Configuring DNS Server Addresses About DNS Domain Name System (DNS) servers map the user-friendly domain names that users type into their Web browsers (e.g., "yahoo.com") to the equivalent numerical IP addresses that are used for Internet routing. When a PC user types a domain name into a browser, the PC must first send a request to a DNS server to obtain the equivalent IP address. The DNS server will attempt to look up the domain name in its own database, and will communicate with higher-level DNS servers when the name cannot be found locally. When the address is found, it is sent back to the requesting PC and is referenced in IP packets for the remainder of the communication. Assigning DNS Addresses to PCs Multiple DNS addresses are useful to provide alternatives when one of the servers is down or is encountering heavy traffic. ISPs typically provide primary and secondary DNS addresses, and may provide additional addresses. Your LAN PCs learn these DNS addresses in one of the following ways: f Statically: If your ISP provides you with their DNS server addresses, you can assign them to each PC by modifying the PCs' IP properties. f Dynamically from a DHCP pool: You can configure the DHCP Server feature on the ADSL2+ Ethernet Modem Router and create an address pool that specifies the DNS addresses to be distributed to the PCs. Refer to "Configuring DHCP Server," on page 95 for instructions on creating DHCP address pools. In either case, you can specify the actual addresses of the ISP's DNS servers (on the PC or in the DHCP pool), or you can specify the address of the LAN interface on the ADSL/ADSL2+ Ethernet Modem Router (e.g., 192.168.1.254). When you specify the LAN interface IP address, the device performs DNS relay, as described in the following section. Note If you specify the actual DNS server addresses on the PCs or in the DHCP pool, the DNS relay feature is not used. 103

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205

103
9
Configuring DNS Server Addresses
About DNS
Domain Name System (DNS) servers map the user-friendly domain
names that users type into their Web browsers (e.g., "yahoo.com")
to the equivalent numerical IP addresses that are used for Internet
routing.
When a PC user types a domain name into a browser, the PC must
first send a request to a DNS server to obtain the equivalent IP
address. The DNS server will attempt to look up the domain name
in its own database, and will communicate with higher-level DNS
servers when the name cannot be found locally. When the address
is found, it is sent back to the requesting PC and is referenced in IP
packets for the remainder of the communication.
Assigning DNS Addresses to PCs
Multiple DNS addresses are useful to provide alternatives when one
of the servers is down or is encountering heavy traffic. ISPs typically
provide primary and secondary DNS addresses, and may provide
additional addresses. Your LAN PCs learn these DNS addresses in
one of the following ways:
Statically:
If your ISP provides you with their DNS server
addresses, you can assign them to each PC by modifying
the PCs' IP properties.
Dynamically from a DHCP pool:
You can configure the
DHCP Server feature on the ADSL2+ Ethernet Modem
Router and create an address pool that specifies the DNS
addresses to be distributed to the PCs. Refer to
“Configuring DHCP Server,” on page 95 for instructions on
creating DHCP address pools.
In either case, you can specify the actual addresses of the ISP's
DNS servers (on the PC or in the DHCP pool), or you can specify
the address of the LAN interface on the ADSL/ADSL2+ Ethernet
Modem Router (e.g., 192.168.1.254). When you specify the LAN
interface IP address, the device performs
DNS relay
, as described
in the following section.
Note
If you specify the actual DNS server addresses on the PCs or in
the DHCP pool, the DNS relay feature is not used.