Name resolution for kickstart

Sat Oct 4 03:40:11 UTC 2014

Allegedly, on or about 03 October 2014, CLOSE Dave sent:
> We have a number of internal machines which run a local nameserver. It's 
> primarily a relay for the wider net but does a few other things as well. 
> So DHCP is configured to specify 127.0.0.1 as the nameserver address for 
> these machines.
> 
> Of course, that is also what kickstart is told when it connects and 
> begins operation. But, of course, kickstart is not running a local 
> nameserver. This means that name resolution for the "repo" lines in the 
> kickstart file doesn't work and installations fail.
> 
> The only workaround I've found is to use IP addresses in the "repo" 
> lines, not the associated names. But this isn't ideal: addresses can 
> change and sites using multiple addresses can't be properly matched.
> 
> Is there a way I can tell kickstart not to use the resolver specified by 
> DHCP but instead use one that I specify in the kickstart file?

Specify the details on your DHCP server.  Actually sending 127.0.0.1 is
an odd thing, because it means "yourself," and I'd only send such data
to those specific machines.  For everything else, give a specific DNS
server address for one of those machines.  Do all of that on the DHCP
server.  Have some specific machine entries (your servers), and separate
configuration for a range of dynamic client machines.

This is an modified example configuration from my own DHCP server,
below.  It used a range of different options, while trying things out.
There's some entries that are fixed by MAC (best option), others that
give out a specific IP to machines by their hostnames (too easily
screwed up by clients).  The stuff at the head of the file is sent to
everyone.  The stuff within the sub-clauses {bracketed}, only goes to
those particular items.

authoritative;
allow                   client-updates;
include			"/etc/rndc.key";  # (same key used by BIND, needed to update DNS records)

default-lease-time	604800;  # 7 days (was 2 hours)
max-lease-time		1209600; # 14 days (was 24 hours)
min-lease-time		30;	 # 30 seconds (might help renewing experiments)

server-name		"gigs";

#local-address	192.168.1.2;

ddns-domainname		"lan.example.com.";
ddns-rev-domainname	"in-addr.arpa.";
ddns-update-style	interim;
ddns-updates		on;

option domain-name	"lan.example.com.";

option nntp-server	news.lan.example.com;
option pop-server	pop3.lan.example.com;
option smtp-server	smtp.lan.example.com;
option wpad-curl	code 252 = text;
#option wpad-curl	"http://proxy.lan.example.com/wpad.dat";
option www-server	www.lan.example.com;

option ntp-servers	time.lan.example.com;
# option time-offset	34200;	# Australian Central Standard Time
option time-offset	37800;	# Central Australia Daylight Time
# Seem to be stupidly stuck with manually setting this!
# Daylight savings:  2am last Sun of Oct - 3am first Sun of Apr
# 2009+ changed to:  first Sunday of Oct to first Sun of Apr

option ip-forwarding	off;	# tell clients not to act as gateways (?)

shared-network lan.example.com {

	option wpad-curl        "http://proxy.lan.example.com/wpad.dat";

	subnet 192.168.1.0 netmask 255.255.255.0 {

		range 192.168.1.100 192.168.1.200;  # dynamic IP assignment range

		option routers			192.168.1.254;  # default gateway
		option subnet-mask		255.255.255.0;
		option broadcast-address	192.168.1.255;
		option domain-name-servers	192.168.1.2;

		option netbios-dd-server	192.168.1.2;  # old windows networking
		option netbios-name-servers	192.168.1.2;  # WINS
		option netbios-node-type 8;                   # old windows networking
		option netbios-scope "";                      # old windows networking

		zone lan.example.com. { 
			primary 192.168.1.2;
			key rndckey;
		} # details for remote controlling the DNS server

		zone  1.168.192.in-addr.arpa. {
			primary 192.168.1.2;
			key rndckey;
		} # details for remote controlling the DNS server

		# we want the nameserver to appear at a fixed address
		# (Any terminal saying it's "ns" or ns.lan.example.com will
		# be assigned this IP.  It'd be better to match using MAC
		# data, like the subsequent items.)

		host ns {
			fixed-address 192.168.1.2;
		}

                host fluffy {
                        hardware ethernet 00:24:21:9A:6F:6C;
                        fixed-address 192.168.1.12;
                        option host-name "fluffy";
			option domain-name-servers 192.168.1.254; # a different DNS server
                }

                host smallblack {
                        hardware ethernet 00:11:2f:f4:57:8f;
                        fixed-address 192.168.1.113;
                        option host-name "smallblack";
			option domain-name-servers 127.0.0.1; # a different DNS server
                }

		host flakey {
			hardware ethernet 00:00:21:25:92:fb; 
			fixed-address 192.168.1.180;
			option host-name "deadmeat";
			update-static-leases on;
		}

		host rover {
			hardware ethernet 00:48:54:8e:8c:0c;
			fixed-address 192.168.1.9;
			set ddns-rev-name = "9.1.168.192.in-addr.arpa.";
			option host-name "rover";
		}

	}

}

# ------------------ end of it all ---------------------------------------
# see http://www.arda.homeunix.net/dnssetup.shtml for some additional help

# removed while tidying:
#
# option nis-domain		"localdomain.";
# probably not needed, as don't use NIS
#
# range dynamic-bootp 192.168.0.20 192.168.0.30;
# not using bootp
#
# next-server ns.lan.example.com;
# server where boot files are fetched from (network clients)

-- 
[tim at localhost ~]$ uname -rsvp
Linux 3.9.10-100.fc17.x86_64 #1 SMP Sun Jul 14 01:31:27 UTC 2013 x86_64

All mail to my mailbox is automatically deleted, there is no point
trying to privately email me, I will only read messages posted to the
public lists.

George Orwell's '1984' was supposed to be a warning against tyranny, not
a set of instructions for supposedly democratic governments.

ZNQR LBH YBBX