[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
This has baffled me for ages... I have a LAN with a server which runs dhcpd and named (BIND). All other devices on the LAN ask the server for IPs. That part works. But dhcpd is supposed to tell named to update the dns records. It did on the old server, but it doesn't now for some reason. The configuration files were copied across with only minor changes. Strangely, running named as root produced "permission denied" errors in the log, but running it as the user "named" fixed it (the files were owned by named). The dhcpd logs produce some strange things which I don't understand. Some devices concerned have static IP assignments in dhcpd.conf. They get the correct addresses, but some are identified by name, and some aren't. One of them was getting added to the dns, but now it isn't. The thing I really don't understand is why virtually all (but again, some hosts don't have this) hosts have 192.168.39.1 in the log entries. I did have the subnet 192.168.39.x defined on one host once, but that shouldn't be affecting this. I've tried deleting cache from named, dhcpd and dhcpcd on the relevant hosts, but still I get this address in the logs. Note also that sometimes it says found, and sometimes it says not found. This appears to be fairly random, and doesn't matter whether the host has a dynamic or static IP. Here is a sample of my logs. Note that the host presario is identified by name to start with, and then it doesn't bother later on. DHCPREQUEST for 192.168.38.250 (192.168.39.1) from 00:0d:9d:81:bf:44 (presario) via eth0 DHCPACK on 192.168.38.250 to 00:0d:9d:81:bf:44 (presario) via eth0 DHCPDISCOVER from 00:0d:61:72:b8:0d via eth0 DHCPOFFER on 192.168.38.12 to 00:0d:61:72:b8:0d via eth0 DHCPREQUEST for 192.168.38.12 (192.168.39.1) from 00:0d:61:72:b8:0d via eth0 DHCPACK on 192.168.38.12 to 00:0d:61:72:b8:0d via eth0 DHCPREQUEST for 192.168.38.2 from 00:0f:3d:ac:9c:a0 via eth0 DHCPACK on 192.168.38.2 to 00:0f:3d:ac:9c:a0 via eth0 DHCPRELEASE of 192.168.38.250 from 00:0d:9d:81:bf:44 via eth0 (found) DHCPDISCOVER from 00:0d:9d:81:bf:44 via eth0 DHCPOFFER on 192.168.38.250 to 00:0d:9d:81:bf:44 via eth0 DHCPREQUEST for 192.168.38.250 (192.168.39.1) from 00:0d:9d:81:bf:44 via eth0 DHCPACK on 192.168.38.250 to 00:0d:9d:81:bf:44 via eth0 WHAT IS GOING ON!??!?!????????? If anyone has any ideas, please share them. Thanks in advance Simon -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/linux_adm/list-faq.html