TechTalkz.com Logo

Go Back   TechTalkz.com Technology & Computer Troubleshooting Forums > Tech Support Archives > Linux & Opensource > Mandriva Linux

Notices

FQDN for Leafnode

Mandriva Linux


Reply
 
Thread Tools Display Modes
Old 09-01-2008, 04:43 AM   #1
Bit Twister
Guest
 
Posts: n/a
FQDN for Leafnode

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.

Setting hostname = wb.home.invalid in /etc/leafnode/config makes no difference.



$ cat /etc/release
Mandriva Linux release 2008.0 (Official) for i586

leafnode-1.11.6-1mdv2008.0.i586.rpm 345814 Oct 05 00:01

$ head -5 /etc/hosts
127.0.0.1 localhost.localdomain localhost
192.168.1.11 fw.home.invalid fw
192.168.1.12 wb1.home.invalid wb1
192.168.1.130 wb.home.invalid wb
192.168.1.131 beta.home.invalid beta


$ grep -i wb.h /etc/hosts
192.168.1.130 wb.home.invalid wb

$ grep 130 /etc/hosts
192.168.1.130 wb.home.invalid wb


FYI: /etc/hosts -> ../var/lib/named/etc/hosts


$ hostname
wb.home.invalid

$ hostname --ip-address
192.168.1.130

$ host wb
wb.home.invalid has address 192.168.1.130

$ host wb.home.invalid
wb.home.invalid has address 192.168.1.130

$ nslookup $(hostname)
Server: 192.168.1.130
Address: 192.168.1.130#53

Name: wb.home.invalid
Address: 192.168.1.130


$ cat /etc/host.conf
order hosts,bind
multi on
nospoof on
spoofalert on

$ grep hosts: /etc/nsswitch.conf
hosts: files dns nis

$ ifconfig eth0 | head -3
eth0 Link encap:Ethernet HWaddr 00:A0:CC:21:B8:91
inet addr:192.168.1.130 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::2a0:ccff:fe21:b891/64 Scope:Link
  Reply With Quote
Old 09-01-2008, 04:44 AM   #2
David W. Hodgins
Guest
 
Posts: n/a
Re: FQDN for Leafnode

On Wed, 02 Jan 2008 01:01:05 -0500, Bit Twister <> wrote:

> How do I get rid of the must have FQDN problem.


Have you set the HOSTNAME= in /etc/sysconfig/network ?

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.)
  Reply With Quote
Old 09-01-2008, 04:44 AM   #3
Jeff@gammalinux.inet
Guest
 
Posts: n/a
Re: FQDN for Leafnode

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

  Reply With Quote
Old 09-01-2008, 04:44 AM   #4
Bit Twister
Guest
 
Posts: n/a
Re: FQDN for Leafnode

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.
  Reply With Quote
Old 09-01-2008, 04:44 AM   #5
David W. Hodgins
Guest
 
Posts: n/a
Re: FQDN for Leafnode

On Wed, 02 Jan 2008 11:34:21 -0500, Bit Twister <> 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?

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.)
  Reply With Quote
Old 09-01-2008, 04:44 AM   #6
Bit Twister
Guest
 
Posts: n/a
Re: FQDN for Leafnode

On Wed, 02 Jan 2008 01:08:20 -0500, David W. Hodgins wrote:
> On Wed, 02 Jan 2008 01:01:05 -0500, Bit Twister <BitTwister@mouse-potato.com> wrote:
>
>> How do I get rid of the must have FQDN problem.

>
> Have you set the HOSTNAME= in


I would be impressed if leafnode's tools look in there.

$ grep -i home /etc/sysconfig/network
HOSTNAME=wb.home.invalid

And Oh, by the way

$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.1.130
domain home.invalid


$ dig $(hostname)

; <<>> DiG 9.4.1-P1 <<>> wb.home.invalid
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38404
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1

;; QUESTION SECTION:
;wb.home.invalid. IN A

;; ANSWER SECTION:
wb.home.invalid. 86400 IN A 192.168.1.130

;; AUTHORITY SECTION:
home.invalid. 86400 IN NS ns1.home.invalid.
home.invalid. 86400 IN NS ns2.home.invalid.

;; ADDITIONAL SECTION:
ns1.home.invalid. 86400 IN A 192.168.1.130

;; Query time: 3 msec
;; SERVER: 192.168.1.130#53(192.168.1.130)
;; WHEN: Wed Jan 2 01:54:27 2008
;; MSG SIZE rcvd: 101
  Reply With Quote
Old 09-01-2008, 04:45 AM   #7
Bit Twister
Guest
 
Posts: n/a
Re: FQDN for Leafnode

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

  Reply With Quote
Old 09-01-2008, 04:45 AM   #8
Bit Twister
Guest
 
Posts: n/a
Re: FQDN for Leafnode SOLUTION

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.
  Reply With Quote
Old 09-01-2008, 04:46 AM   #9
David W. Hodgins
Guest
 
Posts: n/a
Re: FQDN for Leafnode

On Wed, 02 Jan 2008 02:56:40 -0500, Bit Twister <> wrote:

>>> How do I get rid of the must have FQDN problem.


Have you confirmed that "host 192.168.1.130" is returning wb.home.invalid,
and that the named service is starting prior to leafnode (xinetd service)?

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.)
  Reply With Quote
Old 09-01-2008, 04:46 AM   #10
Bit Twister
Guest
 
Posts: n/a
Re: FQDN for Leafnode

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.
  Reply With Quote
Reply

Thread Tools
Display Modes



< Windows Help - MS Office Help - Hardware Support >


New To Site? Need Help?

All times are GMT +5.5. The time now is 01:56 AM.


vBulletin, Copyright ©2000 - 2009, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO
Copyright © 2005-2009, TechTalkz.com. All Rights Reserved - Privacy Policy
Valid XHTML 1.0 Transitional