Bug 9928

Summary: in-addr.arpa.localdomain queries during kickstart install
Product: [Retired] Red Hat Linux Reporter: Kent Engström <kent>
Component: installerAssignee: Erik Troan <ewt>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.1   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-07-13 13:14:17 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Kent Engström 2000-03-02 22:23:27 UTC 
When doing a kickstart install of 6.1, using

  network --bootproto dhcp
  nfs --server 192.168.1.100 --dir /install/redhat/rh61-cdrom

and DHCP server configured with

  server-identifier 192.168.1.100;
  deny unknown-clients;

  subnet 192.168.1.0 netmask 255.255.255.0 {
        option routers 192.168.1.1;
        option domain-name-servers 192.168.1.100;
 }

  host host_101 {
    hardware ethernet xx:xx:xx:xx:xx:xx;
    fixed-address 192.168.1.101;
    next-server 192.168.1.100;
    filename "/install/conf/kickstart/probe.cfg";
 }

the computer being installed fails to reverse map its IP address,
asking questions about 101.1.168.192.in-addr.arpa.localdomain
instead of just 101.1.168.192.in-addr.arpa.

To be able to install I have to add an extra zone to my nameserver,
for the bogus in-addr.arpa.localdomain domain.
Comment 1 Erik Troan 2000-06-16 15:24:39 UTC 
Have you tested this with 6.2 to see if it still has this behavior?
Comment 2 Erik Troan 2000-07-13 13:14:15 UTC 
As I haven't heard back, I'm assuming this is fixed in 6.2.