Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DHCP Options - DNS Servers #407

Closed
wispr opened this issue Feb 21, 2018 · 3 comments
Closed

DHCP Options - DNS Servers #407

wispr opened this issue Feb 21, 2018 · 3 comments

Comments

@wispr
Copy link

@wispr wispr commented Feb 21, 2018

Trying to find the correct option in FM to set the DNS servers in a given subnet in DHCP. Sample config from ubuntu wiki is below, but the option for domain-name-servers seems to be missing.

Added: same thing with default gateways, specifically option routers

Sample /etc/dhcpd.conf

default-lease-time 600;
max-lease-time 7200;
option subnet-mask 255.255.255.0;
option broadcast-address 192.168.1.255;
option routers 192.168.1.254;
option domain-name-servers 192.168.1.1, 192.168.1.2;
option domain-name "mydomain.example";

subnet 192.168.1.0 netmask 255.255.255.0 {
range 192.168.1.10 192.168.1.100;
range 192.168.1.150 192.168.1.200;
}

@WillyXJ
Copy link
Owner

@WillyXJ WillyXJ commented Feb 21, 2018

Big oversight you found. Not only is domain-name-servers missing, but routers is missing, too!

@wispr
Copy link
Author

@wispr wispr commented Feb 21, 2018

Ok, well glad I'm not crazy. We can manually add them to the conf file on the server and all works as it should. But as soon as the config change is written from FM, it overwrites and then it stops working. Push it in the next update and we'll keep testing.

WillyXJ pushed a commit that referenced this issue Feb 22, 2018
@WillyXJ
Copy link
Owner

@WillyXJ WillyXJ commented Jan 11, 2019

This is now fixed in fmDHCP 0.2 and later.

@WillyXJ WillyXJ closed this Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants