Bug 17047 - Startupposition conflicts with named
Summary: Startupposition conflicts with named
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: xinetd
Version: 7.1
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Trond Eivind Glomsrxd
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-08-28 18:38 UTC by Enrico Scholz
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2000-08-30 15:34:22 UTC


Attachments (Terms of Use)

Description Enrico Scholz 2000-08-28 18:38:11 UTC
`man xinetd.conf' says nearly `only_from' (paragraph d):

d) a  host name.  When a connection is made to xinetd, a reverse
    lookup is performed, and the canonical name returned is  com-
    pared  to  the  specified host name.  You may also use domain
    names in the form of .domain.com.  If the reverse  lookup  of
    the client's IP is within .domain.com, a match occurs.

When running an own named (nameserver is 127.0.0.1) use of e.g

| only_from = host.local.zone

results in a parsing error during startup. 

This happens because xinetd starts at position 50, but named laterly at pos
55. So DNS lookups done by xinetd will fail.

Comment 1 Trond Eivind Glomsrxd 2000-08-29 15:20:48 UTC
Hmmm.... will fix

Comment 2 Trond Eivind Glomsrxd 2000-08-30 15:34:20 UTC
Fixed.


Note You need to log in before you can comment on or make changes to this bug.