[Eisfair] Problem mit pxe boot / dhcpd

[Friedrich Bartel]

Am 22.06.2013 02:57, schrieb Stephan Manske:
> FAILED: Has an address record but no DHCI, not mine


Bezüglich dieser Fehlermeldung habe ich das gefunden:
Hier geht es darum das einer der Clients den selben Namen wie der 
Filserver bekommen hat.

In this case there is an existing A record, but no DHCID (ie
corresponding TXT) record. So dhcpd will not update the A record. The
assumption is that this is an existing A record not placed there by
dhcpd. eg consider if someone gave their laptop the same name as your
main fileserver.

The way to get things going again is to remove the A record manually,
then when dhcpd next renews the lease it will be able to update DNS and
create both A and TXT records.

As to how it got there, well there are a number of possibilities I can
think of: it could have been created manually, the client could have
created it as p[art of a direct client DNS update, or something got
messed up when the lease expired and dhcpd was not able to remove both
the A and TXT records. There is no requirement that a direct client
update will create the TXT record, eg Windows only creates the A
record. This is purely a mechanism that dhcpd uses.


For example, calling your new client mail.company.com and then putting
it on the network. If the DHCP server/client just blindly updated DNS
then your actual mailserver DNS records would be hijacked and everyone
would now be pointing at the new client.


Grüße

Friedrich