DHCP server as a DDNS forwarder

Another interesting case today: After an IP address renewal, some printers’ FQDNs could no longer be resolved. This was a random occurrence, although some printers were affected more than others.

It turns out that once in a while the queues on the DHCP server get full and the DNS server never gets the information that the records need to be refreshed.

 

https://blogs.technet.microsoft.com/networking/2016/11/25/dynamic-dns-registration-process-can-cause-queue-build-up-and-failures/

Turning on DDNS manually on the printer and flapping the printer port seems to help.

 

@update April 11, 2018

Actually, this was caused by two hosts that went haywire and sent DHCP requests with empty hostnames. The Bluecat server v8.1.1 is still vulnerable and its DDNS process crash when it receives such requests. The requests were sent every minute by two hosts, so the process crashed twice per every minute.

Troubleshooting method:

  • find dhcp ”top talkers”
  • analyse the error logs on the dhcp server

 

 

 

Skomentuj

Wprowadź swoje dane lub kliknij jedną z tych ikon, aby się zalogować:

Logo WordPress.com

Komentujesz korzystając z konta WordPress.com. Wyloguj /  Zmień )

Zdjęcie na Google

Komentujesz korzystając z konta Google. Wyloguj /  Zmień )

Zdjęcie z Twittera

Komentujesz korzystając z konta Twitter. Wyloguj /  Zmień )

Zdjęcie na Facebooku

Komentujesz korzystając z konta Facebook. Wyloguj /  Zmień )

Połączenie z %s