@jimp said in DHCP allowing double entries for a static IP address: There are use cases where someone may want to use multiple MACs for the same IP address, such as roaming between wired/wireless. It's been this way since 2.4.3: https://redmine.pfsense.org/issues/8220 Thank you. That clears that up.

All good points. Sorry, I asked the question before fully thinking it through and hate to waste your time during what I'm sure is an unusually demanding period support-wise. I appreciate the responses though.

@ralphys thanks for this long answer! I will run some tests as soon as I get around to it! Reporting back here.

Easiest way to resolving leak of Private IP is by setting X-Forwarded VIA Header Mode to "off". Located Proxy Server: General Settings/ General tab. Problem Solved.

I will do as you both suggested when I get home this evening. Most of the rules you see is based on the configuration AirVPN suggested. I'm not an expert with any of this, nor do I claim to be. I try to do my best and learn along the way. I removed all of the alias. That rule is now stale. All of this as flawed as it may be, was working and I haven't made any changes. Thanks or your help

@johnpoz Thanks for that. Success. :)

Hi, @thompsonm said in DHCP service won't start: Any suggestions? Post screenshots of your igb1.2 and igb1.4 LAn settings and DHCP server settings for both interfaces ?

You will likely have to detail this "design" with a detailed diagram.

What is the DHCP server logging?

@johnpoz said in DNS Resolver not working: This is OLD... But same sort of problem it looks like with your roots.. https://forum.netgate.com/topic/78531/unbound-cannot-start-in-2-2-release/2 can't hurt to try this https://forum.netgate.com/post/510554 Thank you! I will try this on Monday. We didn't setup this equipment so I am playing catch-up. I love the idea of this open source firewall though, and so far the community seems great!

Me again, after backing the switch firmware right down to 3.8.6 the switch asks for an address and gets one from pfSense. So I think the issue is with the switch, no idea why it an address from another DHCP but there you go. Thanks all again.

@aeleus said in Dynamic DNS removes all A records on GoDaddy when updating the root domain: It seems it is a bug with GoDaddy's API. Here's their response to my inquiry: "Our team is aware [of] this issue and working on getting this resolved at this time. But we do not have a full ETA at this time. " UPDATE: It looks like GoDaddy has fixed the issue. You can now update "@" records.

@_neok said in DNS configuration tip request: So external DNS queries are resolved by my pfSense. Where did you get that idea from.. Out of the box MS dns would resolve not forward so pfsense would have zero to do with your AD resolving google. Did you have forwarder setup in your AD dns?