FQDN for Leafnode

Bit Twister

On Wed, 2 Jan 2008 06:01:05 +0000 (UTC), Bit Twister wrote:
> How do I get rid of the must have FQDN problem.
> /etc/cron.daily/texpire causes


Short answer, changed nodes' FQDN
from wb.home.invalid
to wb.home.bogus


Long answer:
You can get the message because of the following test snippets found
in the source code. Thanks to David W. Hodgins for that research.

Do a
host $(hostname --fqdn)

and if the parts of the results match any of the following
"localhost"
"127."
"linux.local"
"example.org"
"example.com"
"example.net"
".example"
".invalid"
".local"
".localdomain"
".localhost"
".test"
".site"

you get something like
Leafnode must have a fully-qualified and globally unique domain name,
not just "wb.home.invalid".
Edit your /etc/hosts file to add a unique, fully qualified domain name.
"localhost.localdomain" or thereabouts will not work;
it's qualified, but not unique.
Please see the README-FQDN file for details.

Bit Twister

On Wed, 02 Jan 2008 15:27:39 -0500, David W. Hodgins wrote:
> On Wed, 02 Jan 2008 11:34:21 -0500,
> Bit Twister <BitTwister@mouse-potato.com> wrote:
>
>> named is started on boot and leafnode is started on demand.
>
> leafnode is executed on demand, but the config file is only loaded
> when xinetd starts, or you run service leafnode start.
>
> Is the error message being generated when you run service leafnode start,
> or only when xinetd is initially loading?

Message is from /etc/cron.daily/texpire, See:

Leafnode must have a fully-qualified and globally unique domain name,
not just "wb.home.invalid".
Edit your /etc/hosts file to add a unique, fully qualified domain name.
"localhost.localdomain" or thereabouts will not work;
it's qualified, but not unique.
Please see the README-FQDN file for details.

----- and here is results of cat /etc/cron.daily/texpire ------------
#!/bin/sh
#
# Leafnode texpire cron job. To be run daily.

# Expire old news.
su - news -c /usr/sbin/texpire

# Get new news.
#su - news -c /usr/sbin/fetch
-------------------- end of cat /etc/cron.daily/texpire ----------------------

# file /usr/sbin/texpire
/usr/sbin/texpire: ELF 32-bit LSB executable, Intel 80386, version 1
(SYSV), for GNU/Linux 2.6.9, dynamically linked (uses shared libs), stripped

Bit Twister

On Wed, 02 Jan 2008 18:00:45 -0800, wrote:

> David H. has is right. Now, can we change it? Let us know.

I would guess complaints at leafnode.org might do it.

At best they aught to add the reject name list to their DNS-FAQ.

> Oh, and I got a "frap" from BT. Where do I get the T-shirt.

Hahaha.

> Thanks BT for all you've done for us mere mortals.

Hey thanks to you for jumping in and giving a solution.

I tried your .inet without a DNS server and leafnode still complained.
Started named and it worked. Guess I need to register a domain name.

Quick search would suggest
, ,
to be a free registration answer.

Jeff@gammalinux.inet

On Wed, 02 Jan 2008 06:01:05 +0000, Bit Twister wrote:

> How do I get rid of the must have FQDN problem.
> /etc/cron.daily/texpire causes
>
> # cat /var/log/news.all
> Jan 1 23:15:24 wb texpire[994]: config: debugmode is 3
> Jan 1 23:15:24 wb texpire[994]: config: found username for news.verizon.net
> Jan 1 23:15:24 wb texpire[994]: config: found password for news.verizon.net
> Jan 1 23:15:24 wb texpire[994]: config: maxage is 2
> Jan 1 23:15:24 wb texpire[994]: config: filterfile is /etc/leafnode/filters
> Jan 1 23:15:24 wb texpire[994]: Core file size: 67108864
> Leafnode must have a fully-qualified and globally unique domain name,
> not just "wb.home.invalid".
> Edit your /etc/hosts file to add a unique, fully qualified domain name.
> "localhost.localdomain" or thereabouts will not work;
> it's qualified, but not unique.
> Please see the README-FQDN file for details.
>
> Been there, done that, plus google.
> I have got to be missing something simple.
-snip-
Hi Bit,
Yes it is something simple. Leafnode doesn't like the ".invalid" part.
I've been using leafnode for a couple years now and use ".inet" which it
seems to like. I know you like to tell the newbies (like me) to set their
hostname to xxx.xxx.invalid but when I first did that, fetchnews stopped
working for me. Changing it back to .inet fixed it.
Oh, and I haven't set up any DNS server for my nntp server and simply use
the static local IP address I assigned to read the news on my intranet.
Hope this helps.
Jeff


--
Posted via a free Usenet account from

Bit Twister

On Wed, 02 Jan 2008 16:23:09 -0800, wrote:

> Yes it is something simple. Leafnode doesn't like the ".invalid" part.

Well, frap.

And double frap, it does not like ".test" either. :-(
..test should work in my opinion.

Doug Laidlaw

Bit Twister wrote:

> On Wed, 2 Jan 2008 06:01:05 +0000 (UTC), Bit Twister wrote:
>> How do I get rid of the must have FQDN problem.
>> /etc/cron.daily/texpire causes
>
>
> Short answer, changed nodes' FQDN
> from wb.home.invalid
> to wb.home.bogus
>
>
> Long answer:
> You can get the message because of the following test snippets found
> in the source code. Thanks to David W. Hodgins for that research.
>
> Do a
> host $(hostname --fqdn)
>
> and if the parts of the results match any of the following
> "localhost"
> "127."
> "linux.local"
> "example.org"
> "example.com"
> "example.net"
> ".example"
> ".invalid"
> ".local"
> ".localdomain"
> ".localhost"
> ".test"
> ".site"
>
> you get something like
> Leafnode must have a fully-qualified and globally unique domain name,
> not just "wb.home.invalid".
> Edit your /etc/hosts file to add a unique, fully qualified domain name.
> "localhost.localdomain" or thereabouts will not work;
> it's qualified, but not unique.
> Please see the README-FQDN file for details.

Interesting that you were caught too BT. I am now using "dougshost.<my Web
domain>", since you thought that my previous "dougshost.mydomain.org" might
overlap with an issued domain name.

Leafnode's maintainer Andre is very sure that if you
use "localhost.localdomain" you will lose posts, and his software will get
the blame for it. So he insists that you have a "proper" FQDN.
Interesting to see how far he has gone to enforce that.

Doug.

Bit Twister

On Sat, 05 Jan 2008 01:26:01 +1100, Doug Laidlaw wrote:
>
> Interesting that you were caught too BT. I am now using "dougshost.<my Web
> domain>", since you thought that my previous "dougshost.mydomain.org" might
> overlap with an issued domain name.

Normally when I replay to a network problem, I assume a newbie and
assume they made up a domain name. I'll check domain name with
whois mydomain.org
and indicate the domain may be in use. Here try
$ whois junk-stuff.com
$ whois junkstuff.com

You may have to install whois urpmi --wget whois --auto


Sorry if mydomain.org is yours.

> Leafnode's maintainer Andre is very sure that if you
> use "localhost.localdomain" you will lose posts,

Yes, the message
"localhost.localdomain" or thereabouts will not work;
is misleading since I was not using "localhost.localdomain"

Should be an easy fix to plug in the node name he is checking.


> and his software will get
> the blame for it. So he insists that you have a "proper" FQDN.
> Interesting to see how far he has gone to enforce that.

Yes I understand, but
indicates .test is for testing.

David W. Hodgins

On Wed, 02 Jan 2008 16:25:17 -0500, Bit Twister <BitTwister@mouse-potato..com> wrote:

> Message is from /etc/cron.daily/texpire, See:

May want to setup a dynamic dns host name (to ensure no one else is using it),
so you can use a real domain name, safely.

Checking the source code from the leafnode package ...

int is_validfqdn(const char *f) {
/* do not let us fool by trailing dots */
char *fqdn = strdup(f);
if (!fqdn) return 0;
while (fqdn[strlen(fqdn)-1] == '.')
fqdn[strlen(fqdn)-1] = '\0';

if (/* reject unqualified names */
!(strchr(fqdn, '.'))
/* Red Hat list the FQDN on the same line as localhost, thus,
* the qualification returns two "localhost*" aliases */
|| 0 == strncasecmp(fqdn, "localhost", 9)
/* protect against broken hosts or DNS */
|| 0 == strncmp(fqdn, "127.", 4)
/* SuSE default hostname on some installs is linux.local */
|| 0 == strcasecmp(fqdn, "linux.local")
/* kill RFC 2606 second- and top-level domains */
|| 0 == strcasecmpsuffix(fqdn, "example.org")
|| 0 == strcasecmpsuffix(fqdn, "example.com")
|| 0 == strcasecmpsuffix(fqdn, "example.net")
|| 0 == strcasecmpsuffix(fqdn, ".example")
|| 0 == strcasecmpsuffix(fqdn, ".invalid")
|| 0 == strcasecmpsuffix(fqdn, ".local")
|| 0 == strcasecmpsuffix(fqdn, ".localdomain")
|| 0 == strcasecmpsuffix(fqdn, ".localhost")
|| 0 == strcasecmpsuffix(fqdn, ".test")
|| 0 == strcasecmpsuffix(fqdn, ".site")
)
{
free(fqdn);
return 0;
}
free(fqdn);
return 1;
}

The readme states that the above restrictions are in place, to try and guarantee
the generation of unique message ids.

Regards, Dave Hodgins

--
Change nomail.afraid.org to ody.ca to reply by email.
(nomail.afraid.org has been set up specifically for
use in usenet. Feel free to use it yourself.)

Doug Laidlaw

Bit Twister wrote:

> On Wed, 2 Jan 2008 06:01:05 +0000 (UTC), Bit Twister wrote:
>> How do I get rid of the must have FQDN problem.
>> /etc/cron.daily/texpire causes
>
>
> Short answer, changed nodes' FQDN
> from wb.home.invalid
> to wb.home.bogus
>
>
> Long answer:
> You can get the message because of the following test snippets found
> in the source code. Thanks to David W. Hodgins for that research.
>
> Do a
> host $(hostname --fqdn)
>
> and if the parts of the results match any of the following
> "localhost"
> "127."
> "linux.local"
> "example.org"
> "example.com"
> "example.net"
> ".example"
> ".invalid"
> ".local"
> ".localdomain"
> ".localhost"
> ".test"
> ".site"
>
> you get something like
> Leafnode must have a fully-qualified and globally unique domain name,
> not just "wb.home.invalid".
> Edit your /etc/hosts file to add a unique, fully qualified domain name.
> "localhost.localdomain" or thereabouts will not work;
> it's qualified, but not unique.
> Please see the README-FQDN file for details.

Interesting that you were caught too BT. I am now using "dougshost.<my Web
domain>", since you thought that my previous "dougshost.mydomain.org" might
overlap with an issued domain name.

Leafnode's maintainer Andre is very sure that if you
use "localhost.localdomain" you will lose posts, and his software will get
the blame for it. So he insists that you have a "proper" FQDN.
Interesting to see how far he has gone to enforce that.

Doug.

Jeff@gammalinux.inet

On Thu, 03 Jan 2008 01:24:25 +0000, Bit Twister wrote:

> On Wed, 02 Jan 2008 16:23:09 -0800, wrote:
>
>> Yes it is something simple. Leafnode doesn't like the ".invalid" part.
>
> Well, frap.
>
> And double frap, it does not like ".test" either. :-(
> .test should work in my opinion.

David H. has is right. Now, can we change it? Let us know.
Oh, and I got a "frap" from BT. Where do I get the T-shirt.
Thanks BT for all you've done for us mere mortals.
Jeff

--
Posted via a free Usenet account from