DHCP server does not update DNS

[Simon Hobson]

Richard Allen wrote:

>... and we also located the network issue witch turned out to be a rogue
>dhcp relay

I keep a piece of "clue by four" in the office. I've come close to 
using it once or twice ;-)

>Dec 21 16:02:24 wanda dhcpd: DHCPRELEASE of 172.23.101.114 from
>00:0f:fe:80:50:3e (censored5) via eth0 (found)
>
>Dec 21 16:02:54 wanda dhcpd: DHCPDISCOVER from 00:0f:fe:80:50:3e via
>172.23.100.254
>Dec 21 16:02:55 wanda dhcpd: DHCPOFFER on 172.23.101.114 to
>00:0f:fe:80:50:3e (censored5) via 172.23.100.254
>Dec 21 16:02:55 wanda dhcpd: DHCPREQUEST for 172.23.101.114 (172.29.100.96)
>from 00:0f:fe:80:50:3e (censored5) via 172.23.100.254
>Dec 21 16:02:55 wanda dhcpd: DHCPACK on 172.23.101.114 to 00:0f:fe:80:50:3e
>(censored5) via 172.23.100.254
>Dec 21 16:02:57 wanda named[31310]: client 172.23.101.114#19576: update
>'censored.com/IN' denied
>
>Now 172.23.100.254 is the proper relay agent it should be using when
>traversing broadcast domains.
>There was however no attempt made to register this into DNS.

I think you are now down to sniffing packets to see what options 
are/aren't present. That looks normal for a situation where client 
and server have agreed that the client will update DNS.


-- 
Simon Hobson

Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed
author Gladys Hobson. Novels - poetry - short stories - ideal as
Christmas stocking fillers. Some available as e-books.