Not able to resolve the tftp alias name

Glenn Satchell glenn.satchell at
Fri Dec 4 01:00:35 UTC 2015

When you specify the name in quotes it is passed as a string to the device
that is booting. That device has to resolve the name to an IP address.
Perhaps replace the string with the fully qualified name? Your pxe client
may not be smart enough to do a dns lookup.

Alternatively use the dhcp-function 'next-server' and do not use quotes
around the name. This way the dhcp server will resolve the name to an IP
and send the IP address in the dhcp response, eg:

next-server proj-1.ab.lab;


On Fri, December 4, 2015 1:51 am, karteek.challa at wrote:
> Hi all,
> I am facing a problem in resolving the tftp alias name using dhcp.
> I have the below configuration in dhcpd.conf:
> option domain-name "ab.lab";
> option domain-name-servers,;
> option tftp-server-name "proj-1";
> nslookup of proj-1:
>>nslookup proj-1
> Server:
> Address:
> Non-authoritative answer:
> proj-1.ab.lab        canonical name = cc675.ab.lab
> Name:   cc675.ab.lab
> Address:
> But the linux board booting got failed with error "Command tftp failed,
> with error unknown host proj-1.ab.lab."
> But when I give the "option tftp-server-name" in dhcp specifying
> the direct ip address, it is booting successfully and everything is fine.
> Could you please guide me whether I missed anything configuring in
> dhcpd.conf file or did I do anything wrong in configuration?
> BR,
> Karteek
> The information contained in this electronic message and any attachments
> to this message are intended for the exclusive use of the addressee(s) and
> may contain proprietary, confidential or privileged information. If you
> are not the intended recipient, you should not disseminate, distribute or
> copy this e-mail. Please notify the sender immediately and destroy all
> copies of this message and any attachments. WARNING: Computer viruses can
> be transmitted via email. The recipient should check this email and any
> attachments for the presence of viruses. The company accepts no liability
> for any damage caused by any virus transmitted by this email.
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at

More information about the dhcp-users mailing list