DDNS and fedora
Tim
ignored_mailbox at yahoo.com.au
Fri Apr 4 09:58:58 UTC 2008
On Fri, 2008-04-04 at 18:42 +1000, Da Rock wrote:
> I'd really rather not have to put up all my config for security
> reasons.
So, change some of the personal details...
> Especially considering that by running the dhclient manually actually
> works (-H AND -cf). The problem exists in the enormous complexity of
> network scripts that Fedora uses. It simply refuses to read the
> dhclient.conf- so why would that be?
The problem may well be that you're not writing the configuration files
properly, but we can't tell.
Also, tell us whether you're using "network" and/or "NetworkManager"
services.
I've attached the dhcpd.conf file from my server. It's full of
experiments, you don't need most of the stuff that's in it. But it
works for me, in the manner that I expect it to.
NB: "example.com" is a domain name reserved for using in example
documentation (so you don't cause problems with other people's
networks).
--
(This computer runs FC7, my others run FC4, FC5 & FC6, in case that's
important to the thread.)
Don't send private replies to my address, the mailbox is ignored.
I read messages from the public lists.
-------------- next part --------------
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 set at 2 hours)
max-lease-time 1209600; # 14 days (was set at 24 hours)
min-lease-time 30; # 30 seconds (might allow renewing experiments)
server-name "giggles";
#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
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;
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;
option netbios-name-servers 192.168.1.2; # WINS
option netbios-node-type 8;
option netbios-scope "";
option finger-server finger.lan.example.com;
zone lan.example.com. {
primary 192.168.1.2;
key rndckey;
}
zone 1.168.192.in-addr.arpa. {
primary 192.168.1.2;
key rndckey;
}
# 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.)
host ns {
fixed-address 192.168.1.2;
}
host fixed {
fixed-address 192.168.1.99;
}
host fixme {
fixed-address 192.168.1.150;
}
host suspishus {
hardware ethernet 00:1A:92:D8:F2:79;
fixed-address 192.168.1.22;
option host-name "suspishus";
}
# 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.";
# fixed-address rover.lan.example.com;
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)
More information about the fedora-list
mailing list