System\GeneralSetup\DNS Server Settings
-
Are you logged in as admin or another user?
If it's another user, does that user have access to make config changes?
Check the logs to see if it's logging a failure when you save.
-
@jimp I login under another user name, with full Admin privileges. No issues with changes in any other areas of pfSense+
-
@BobL4002 I still can not reproduce this. Created a testuser, put it in the admins group and added dns with a fqdn and saves and leave and come back and still there.
-
@BobL4002 said in System\GeneralSetup\DNS Server Settings:
@jimp I login under another user name, with full Admin privileges. No issues with changes in any other areas of pfSense+
By "full admin privileges" do you mean you made them only a member of the
adminsgroup?Or did you select all privileges manually and add them to the user?
If the latter, the user would have also been assigned the "Deny Config Write" privilege and it would behave as you describe.
-
@jimp I am member of Admin group with full privileges. I even logged out and back in as Admin and issue still persists.
-
@BobL4002 could it be something in your browser.. If you look at your config history, do you see that the value gets written?
example.. here is diff on the config when I added new dns and fqdn as testuser
-
@johnpoz I toyed around with the System\GeneralSetup\DNS Server Settings and resolved issue. I had to provide Hostname for the topmost DNS server 127.0.0.1 "localhost.com" and then all entries were retained/displayed even after logout/login. I guess there needs to be entry for each DNS server for system to hold/display the info. Strangely enough, even if it is not displayed when I saved the .xml file to my desktop and examined it, the Hostnames were saved, even though they did not display.
Thanks for assist.
-
That seems like unexpected behaviour. A regression of this maybe?: https://redmine.pfsense.org/issues/9898
Do you have multiple gateways?
-
@BobL4002 why should you even have a 127.0.0.1 listed there.. You don't need to put that there..
I don't forward, only resolve - only place 127.0.0.1 is listed is on behavior dropdown
-
If it was upgraded from a much earlier version it might have had localhost set there. At one time that was a valid setting.
-
@stephenw10
I did upgrade from earlier versions, not sure if "localhost" was input then or not.Thanks
-
@johnpoz
I believe it was there by default when I first started with pfSense and I have seen it listed in various articles/videos I watched, just assumed it was required in the listing in order to be "defaulted" to.Thanks for input.
-
Yes, this is likely to have been hitting this: https://redmine.pfsense.org/issues/14288
