Bug 1438398 - iPXE itself does not support multiple DNS servers
Summary: iPXE itself does not support multiple DNS servers
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipxe
Version: 7.5-Alt
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Neil Horman
QA Contact: Raviv Bar-Tal
URL:
Whiteboard:
Depends On:
Blocks: 1401126 1402557
TreeView+ depends on / blocked
 
Reported: 2017-04-03 10:52 UTC by Marek Hulan
Modified: 2019-05-09 14:31 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-09 10:59:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
draft patch 0 for dns2 option (4.32 KB, patch)
2018-09-04 17:48 UTC, Neil Horman
no flags Details | Diff

Description Marek Hulan 2017-04-03 10:52:53 UTC
Description of problem:

iPXE itself does not support multiple DNS servers.  

Version-Release number of selected component (if applicable):

all

How reproducible:

100%

Steps to Reproduce:

try to configure multiple nameservers

Actual results:

there's no such option

Expected results:

user can configure multiple nameservers as kernel options, an example template that is normally used to create iPXE configuration can be found at https://github.com/theforeman/community-templates/blob/develop/provisioning_templates/iPXE/kickstart_default_ipxe.erb

Additional info:

This was requested by customer as an enhancement of Satellite 6 iPXE provisioning. Please see BZ 1402557 for more information.

Comment 2 Marek Hulan 2017-04-03 10:54:20 UTC
Another request that would benefit from this is BZ 1401126

Comment 3 Neil Horman 2018-08-17 13:38:04 UTC
This would likely best be implemented as a second config option (dns2 or some such), as the entire code base is written to assume a fixed set of dns servers. Does that seem reasonable?

Comment 4 Marek Hulan 2018-08-18 02:11:32 UTC
It's totally fine to have dns2= as long as it's then configured as secondary dns server. Thanks

Comment 5 Neil Horman 2018-09-04 17:48:58 UTC
Created attachment 1480857 [details]
draft patch 0 for dns2 option

This patch is by no means complete, but I wanted to get it to you early.  It currently will fail if the dns2 option is not configured, and may time out early, but if you could please give it a test and confirm that it sends out packets to the backup dns server if the primary server fails to respond, I would appreciate it.

Comment 6 Marek Hulan 2019-01-11 12:02:54 UTC
I'm sorry, I'm unable to test the patch in foreseeable future.

Comment 17 Neil Horman 2019-05-07 17:50:29 UTC
ping, there has been no traction on this in 2 months.  Is anyone going to test this or should we close it?

Comment 19 Neil Horman 2019-05-09 10:59:14 UTC
Lukas:

1) This is an RFE.  ipxe not supporting two nameservers is why it was open, and why I wrote the attached patch over 8 months ago
2) Ive written the patch and had intentions to post it to the ipxe community once it got some testing
3) The customers requested this as an RFE, but appears completely unable/unwilling to test the proposed patch out
4) I'm the ipxe engineer waiting to get this tested.  I gave it priority and then no one was able to follow up on it.

I've left this sitting open for a year and no one has touched the work I put into it.  Closing since it seems clear this isn't a priority.

Comment 20 Lukas Zapletal 2019-05-09 14:31:12 UTC
Apologies Neil, I should have read the bug top to bottom. Frankly, I don't believe it's important to provide this feature for provisioning phase. However now that I see you already wrote some code and I totally do not want to let any code to be thrown away, I can test this. But some questions:

You introduced new setting called dns2 however documentation (http://ipxe.org/cfg/dns) says: When multiple DNS servers are specified, only the first server will be used. I think there is a mechanism or intention by authors to support multiple "dns" options or maybe values separated by space or comma? Can you tell?

Would it be possible to write some debug message when there is a DNS failover for easier testing?


Note You need to log in before you can comment on or make changes to this bug.