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
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>The unique fully-qualified domain name</title>
<link rev="made" href="mailto:feedback@suse.de" />
</head>
<body style="background-color: white">
<p><a name="__index__"></a></p>
<!-- INDEX BEGIN -->
<ul>
<li><a href="#the_unique_fullyqualified_domain_name">The unique fully-qualified domain name</a></li>
<li><a href="#introduction">Introduction</a></li>
<li><a href="#how_to_get_a_unique_fullyqualified_domain_name">How to get a unique fully-qualified domain name</a></li>
<ul>
<li><a href="#when_leafnode_ignores_your_host_name">When leafnode ignores your host name</a></li>
<li><a href="#why_localhost.anything_will_not_work">Why localhost.ANYTHING will not work</a></li>
</ul>
<li><a href="#how_to_configure_the_fullyqualified_domain_name">How to configure the fully-qualified domain name</a></li>
<ul>
<li><a href="#systemwide">System-wide</a></li>
<li><a href="#local_to_leafnode">Local to leafnode</a></li>
<li><a href="#should_i_configure_the_fqdn_systemwide_or_local_to_leafnode">Should I configure the FQDN system-wide or local to leafnode?</a></li>
</ul>
</ul>
<!-- INDEX END -->
<hr />
<p>
</p>
<h1><a name="the_unique_fullyqualified_domain_name">The unique fully-qualified domain name</a></h1>
<p>This document will introduce you to the Message-ID and FQDN difficulties
and help you out.</p>
<p>
</p>
<hr />
<h1><a name="introduction">Introduction</a></h1>
<p>The unique fully-qualified domain name (or host name, FQDN or FQHN for
short) is used by leafnode to generate the Message-ID.</p>
<p>What is the Message-ID?</p>
<p>Every message (mail or news) has a unique identifier in its header, the
Message-ID. It may not be visible in your software unless you choose
``display all headers'' or ``display raw'' or ``display source''.</p>
<p>The Message-ID looks roughly like an E-Mail address,
<<a href="mailto:12345.67890@host.example.com">12345.67890@host.example.com</a>>: it has a local and
a domain part, separated by an @ sign, only that the local part of the
Message-ID is different for different pieces of mail or news, while the
local part of the mail address is constant. The domain part is usually
the name of the host that generated the Message-ID: your computer's name
when you are sending mail or posting news.</p>
<p>Whenever a news server is offered a new news article for redistribution,
it looks at the Message-ID to determine if it already has the article,
to avoid double work, and to avoid that news articles run in circles.</p>
<p>Therefore, each message sent, mail or news, must have a unique
Message-ID. If the Message-ID is not unique, because you use the same
host name as somebody else, and you and the other person write an
article at the same time, either article will be discarded by the
server. Leafnode will tell you that the Message-ID of the article it is
about to post is already in use upstream.</p>
<p>Please note that <strong>this problem is not leafnode-specific</strong>. Any software
may suffer, but it's less prominent in mail, and it's difficult to see,
because you're not getting a bounce back.</p>
<p>
</p>
<hr />
<h1><a name="how_to_get_a_unique_fullyqualified_domain_name">How to get a unique fully-qualified domain name</a></h1>
<p>There are several ways to obtain one. When you got yours, see <a href="#how_to_configure_the_fullyqualified_domain_name">below on how to configure your domain name</a>.</p>
<dl>
<dt><strong><a name="item_if_you_have_a_domain_registered%3a">If you have a domain registered:</a></strong><br />
</dt>
<dd>
Assume you are the rightful owner of example.com. You can now reserve
any subdomain you wish, say mid.example.com, and a host name for your
leafnode computer, say, abacus.mid.example.com, or for a friend. How you
track that only one machine has the same name at the same time, is up to
you. Writing <em>gave abacus.mid.example.com to Joe at 2002-07-11</em> on a
sheet of paper is perfectly sufficient.
</dd>
<dd>
<p>Again: This host name <strong>need not</strong> be entered into your DNS data base,
just make sure only one computer uses this name at the same time.</p>
</dd>
<p></p>
<dt><strong><a name="item_if_you_have_an_account_at_news%2eindividual%2ede_o">If you have an account at <code>news.individual.de</code> or
<code>news.individual.net</code>:</a></strong><br />
</dt>
<dd>
You have been assigned a user ID. To find it out, type in your shell:
</dd>
<dd>
<pre>
telnet news.individual.de 119</pre>
</dd>
<dd>
<p>(wait until connected)</p>
</dd>
<dd>
<pre>
authinfo user sixpack
authinfo pass joe
quit</pre>
</dd>
<dd>
<p>Replace ``sixpack'' and ``joe'' by your login and password. After the
``authinfo pass'' line, you should see a line that reads:</p>
</dd>
<dd>
<pre>
281 Authentication accepted. (UID=00000)</pre>
</dd>
<dd>
<p>If you get a 481 line, please retry, you may have mistyped user name or
password. Correcting these lines with Backspace or Delete may also lead
to failed logins. Retry with careful typing so that you do not need to
correct your input.</p>
</dd>
<dd>
<p>00000 shall be replaced by your actual user ID.</p>
</dd>
<dd>
<p>Your hostname then is ID-00000.user.uni-berlin.de. DO MAKE SURE TO
REPLACE THE NUMBER IN ID-00000 by the number the server told you in the
UID= LINE.</p>
</dd>
<p></p>
<dt><strong><a name="item_specific_providers%2e">Specific providers.</a></strong><br />
</dt>
<dl>
<dt><strong><a name="item_t%2donline">T-Online</a></strong><br />
</dt>
<dd>
T-Online customers, your hostname is NNNNN.dialin.t-online.de, where
NNNNN is your T-Online number. If your T-Online number contains your
telephone number, contact T-Online support to have a new T-Online number
assigned. I'm unaware if they charge you for this change.
</dd>
<p></p></dl>
<dt><strong><a name="item_ask_your_network_administrator_or_your_internet_se">Ask your network administrator or your internet service provider.</a></strong><br />
</dt>
<dd>
Your local network administrator can assign you a domain to use for
Message-IDs.
</dd>
<dd>
<p>Your internet service provider may have reserved a special subdomain for
the sole purpose of letting users create their own unique Message-IDs.</p>
</dd>
<p></p></dl>
<p>
</p>
<h2><a name="when_leafnode_ignores_your_host_name">When leafnode ignores your host name</a></h2>
<p>Well, it is probably the default name or domain that your OS vendor
chose, like ``localhost.localdomain''. As such, it is not unique, but used
on many computers, and therefore does not qualify as fully qualified
domain name.</p>
<p>
</p>
<h2><a name="why_localhost.anything_will_not_work">Why localhost.ANYTHING will not work</a></h2>
<p>Many sites run resolvers that are based on ISC Bind code. And many sites
configure their name servers so that they will resolve localhost.example.com.
Therefore, localhost.example.com will not designate a single computer,
but any computer that has ``localhost'' as a name. These resolvers are
problematic because they will first see the domain as unqualified and
append the domain or searchlist, so assuming that your domain is
example.com, these resolvers will try localhost.example.com first, which
will resolve to 127.0.0.1 at many sites.</p>
<p>(It is usually a mistake to add localhost to the name server for a
domain, the clients had better be fixed instead. As a workaround,
removing all domain and searchlist lines from <code>/etc/resolv.conf</code> will
usually work at the expense of not being able to use short names unless
they are listed in <code>/etc/hosts</code>.)</p>
<p>
</p>
<hr />
<h1><a name="how_to_configure_the_fullyqualified_domain_name">How to configure the fully-qualified domain name</a></h1>
<p>
</p>
<h2><a name="systemwide">System-wide</a></h2>
<p>Preferably, the host name is entered into your system configuration so
that it is available globally, to your mailers and news readers should
they desire to create a FQDN.</p>
<p>How exactly the hostname is configured, depends on your system, it is
usually a two-step approach, but your system installation/configuration
software may simplify things for you.</p>
<p>1. Configure the bare hostname. Red Hat Linux and Mandrake Linux use
<em>linuxconf</em>. SuSE Linux 7.3 and older read it from <code>FQHOSTNAME</code> in
<code>/etc/rc.config</code> (but you can also use YaST or YaST2), SuSE Linux 8.0
and newer read it from <code>/etc/HOSTNAME</code>. FreeBSD 4.X reads
it from <code>hostname</code> in <code>/etc/rc.conf</code> (but you can use
<code>/stand/sysinstall</code>).</p>
<p>2. On many systems, you will have to put the fully qualified host name
into <code>/etc/hosts</code> in addition to the place mentioned above. (On
networked systems, using NIS, DNS or LDAP is also feasible if the client
is configured to use the respective system to resolve host names.)
Usually, a computer that is to resolve a hostname will look at
<code>/etc/hosts</code> first and then at DNS.</p>
<p>An <code>/etc/hosts</code> line might look like this:</p>
<pre>
192.168.0.1 abacus.mid.example.com abacus oldname</pre>
<p>Keep the original name of the computer as an alias in case you
configured some other software to use the old name.</p>
<p><strong>WARNING:</strong> SuSEconfig (or its hostname module in more recent versions
of SuSE Linux) will destroy aliases and leave only the hostname (from
<code>/etc/rc.config</code> or <code>/etc/HOSTNAME</code> depending on SuSE version) on your
<code>/etc/hosts</code> line. In the above example, SuSEconfig would remove
``oldname''.</p>
<p>The workaround is to replace the local host name by
the FQDN, if possible. If you cannot replace the local host name, a
different workaround is to set <code>CHECK_ETC_HOSTS="no"</code> in either
<code>/etc/rc.config</code> (SuSE Linux 7.3 and older) or
<code>/etc/sysconfig/suseconfig</code> (SuSE Linux 8.0 and newer).</p>
<p>
</p>
<h2><a name="local_to_leafnode">Local to leafnode</a></h2>
<p>You can also write a line like</p>
<pre>
hostname = abacus.mid.example.com</pre>
<p>into your <code>/etc/leafnode/config</code>. But I recommend against it, see the
next section:</p>
<p>
</p>
<h2><a name="should_i_configure_the_fqdn_systemwide_or_local_to_leafnode">Should I configure the FQDN system-wide or local to leafnode?</a></h2>
<p>You should configure the FQDN system-wide. Your news reader may generate
a Message-ID itself, and it is not aware of leafnode's configuration and
will generate an invalid Message-ID -- leafnode will then reject the
posting because the Message-ID is invalid.</p>
</body>
</html>
|
