Re: dhcp broken on 192.168.0 side

[Simon Oosthoek <s.oosthoek@xs4all.nl>]

On 31/08/15 12:50, Wolfgang Schweer wrote:
> On Mon, Aug 31, 2015 at 12:40:30PM +0200, Simon Oosthoek wrote:
> > As this was a tjener config moved from a physical host to a vm, I
> > still have the original image. Can I use this in some way to find out
> > what changed?
>
> You could use ldapvi to look up the LDAP data base in both cases, see
> manual.
>
> It is possible to set up LDAP from scratch, but you will loose all user
> and system data contained in LDAP, so this isn't recommended.
>
> Wolfgang

I think I found the problem, look:
root@tjener:~# host ltspserver00.subnet00
Host ltspserver00.subnet00.intern not found: 2(SERVFAIL)
root@tjener:~# host 192.168.0.254
254.0.168.192.in-addr.arpa domain name pointer ltspserver00.subnet00.intern.

The relevant part in ldap looks like:
80 
cn=subnet00.intern,cn=dhcp,cn=tjener,ou=servers,ou=systems,dc=skole,dc=skolelinux,dc=no
dhcpOption: routers ltspserver00.subnet00
dhcpOption: domain-name "intern subnet00.intern"
dhcpOption: subnet-mask 255.255.255.0
dhcpOption: broadcast-address 192.168.0.255
dhcpOption: root-path "/opt/ltsp/i386"
dhcpOption: ntp-servers ntp
dhcpOption: wpad-url "http://wpad/wpad.dat";
dhcpOption: smtp-server postoffice
dhcpOption: domain-name-servers 10.0.2.2
dhcpStatements: default-lease-time 432000
dhcpStatements: max-lease-time 432000
dhcpStatements: filename "/var/lib/tftpboot/ltsp/i386/pxelinux.0"
dhcpStatements: next-server ltspserver00.subnet00
dhcpStatements: authoritative
dhcpStatements: allow unknown-clients
dhcpStatements: allow bootp
dhcpStatements: allow booting
cn: subnet00.intern
objectClass: top
objectClass: dhcpSharedNetwork

So with the routers option, the ipnumber cannot be found and it is 
empty/left out and the clients are without a default route!

Now to figure out why the dns entry for ltspserver00.subnet00 got 
lost... and more importantly, how to get it back.

The logs say:
ldap2bind: Reloading the zone 'subnet00.intern.' failed: rndc: 'reload' 
failed: bad dotted quad\n

The terminal with the printer got a name and somehow the entry got 
messed up :-(

I'm sure I can fix it now...

Cheers

Simon