next-server dns issue
Glenn.Satchell at uniq.com.au
Tue Jun 5 14:40:52 UTC 2007
>Subject: next-server dns issue
>From: Niklas Fondberg <niklas.fondberg at tilgin.com>
>To: dhcp-users at isc.org
>Date: Tue, 05 Jun 2007 13:14:30 +0200
>I've looked all over and tried all things but my conclusion is that
>dhcpd v.3 has a bug.
>Can you please confirm this by adding a dns entry like:
>nl-gv-pb-vcm2-353tr1.some.host.net resolves to 10.200.19.16
>The next-server field is not sent.
>This however works:
>nl-gv-pb-vcm-trniklastest.some.host.net resolves to 10.200.19.16
>Can it be that the numbers confuses the server?
Which specific version of dhcpd are you referring to? This is from the
Release Notes (RELNOTES file), so if you are using something older
than3.0.2 this might bethe problem:
Changes since 3.0.2
- Some inconsistencies in treating numbers that the lexer parsed as 'NUMBER'
or 'NUMBER_OR_NAME' was repaired. Hexadecimal parsing is affected, and
should work better.
More information about the dhcp-users