March 13, 20224 yr I recently setup a custom docker bridge (VLAN 30) on my unraid server. The bridge works properly but the unraid server gets an IP assignment on the VLAN as well as the LAN. This is causing the pfsense firewall to assign improper DNS entries which results in warnings from FCP. How can I stop the server management from getting an IP on the VLAN? I think that will resolve this issue. 🤞 brunnhilde-diagnostics-20220313-1027.zip
March 13, 20224 yr Author Maybe I have this fixed. In settings>docker "Host access to custom networks" was set to "Enabled". I have changed that to "Disabled" and rebooted the server. FCP is no longer sending an error for DNS. Maybe someone can confirm that this is all that's needed???
March 13, 20224 yr Author 2 hours ago, wgstarks said: Maybe I have this fixed. In settings>docker "Host access to custom networks" was set to "Enabled". I have changed that to "Disabled" and rebooted the server. FCP is no longer sending an error for DNS. Maybe someone can confirm that this is all that's needed??? Well, that didn't work. FCP error returned after a few hours. Next plan is to set a DNS host override in pfsense. I think this will work since it forces all queries to resolve to an IP set in the override. Edit: It would still be nice if I could find a way to isolate the server management from this (or any) VLAN. Browsing the VLAN IP assigned to my server sends me to the unraid login page. Edited March 13, 20224 yr by wgstarks
March 13, 20224 yr To put the details in one thread, I'll copy the FCP warning you posted here: https://forums.unraid.net/topic/47266-plugin-ca-fix-common-problems/page/65/?tab=comments#comment-1106146 Quote Using DNS server 10.0.1.1, the DNS entry for 'Brunnhilde.dahoney.me' resolves to 10.0.30.109. If this url resolves correctly for your client computers using a different DNS server, you can probably ignore this warning. Otherwise, you should ensure that it resolves to 10.0.1.20. So FCP does a dnslookup for Brunnhilde.dahoney.me. It expects the result to be 10.0.1.20 but for some reason it sometimes comes back as 10.0.30.109. As long as the Unraid server is the only system that gets the incorrect IP address I think you can ignore this FCP warning. But if your clients also get the incorrect IP address and are unable to access the webgui that then is a bigger problem.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.