More than one domain with DNS Resolver / Forwader?
-
WTH are you doing there? So, you top secret censored hostname is in some .ninja "I have invented this" domain, and you are passing godknowswhat.jp to clients? Your DNS resolver/forwarder knows nothing about godknowswhat.jp, sure like hell it won't register any leases there. Untick that box about DHCP leases registration.
-
override – my bad ;) Will watch that in the future... heheheehe Sorry KOM...
Also you do understand that .jp is a valid public TLD... Not something I would suggest you use on your internal hosts for resolution.. How about you use .somethingnotvalidonpublic as your tld this removes a lot of problems!!!
-
I actually own those domains.
-
WTH are you doing there? So, you top secret censored hostname is in some .ninja "I have invented this" domain, and you are passing godknowswhat.jp to clients? Your DNS resolver/forwarder knows nothing about godknowswhat.jp, sure like hell it won't register any leases there. Untick that box about DHCP leases registration.
So apart from you assuming that I don't know how domains work do you have any actual suggestions to fix my problem that you restated at the end of your post? How do I let the resolver know that I also have the domain godknowswhat.jp as you put it?
-
Host overrides in the DNS Resolver, bro. What's so hard?
-
. How about you use .somethingnotvalidonpublic as your tld this removes a lot of problems!!!
I would consider that for my home network but some of the services in my lab I do want to expose to public Internet. I thought it'd be easier that the public domain reflects the internal domain as well.
-
Neither the forwarder, not the resolver will do any zone transfers to public DNS servers. Plus I completely fail to see why on earth should the public DNS point to your RFC1918 IPs. It will be completely broken.
-
Neither the forwarder, not the resolver will do any zone transfers to public DNS servers. Plus I completely fail to see why on earth should the public DNS point to your RFC1918 IPs. It will be completely broken.
I am well aware of that they wont transfer to the public DNS.
-
Well friends it looks like its a bug in pfSense.
https://forum.pfsense.org/index.php?topic=86791.0
https://redmine.pfsense.org/issues/1819
Thanks to those who actually tried to help.
-
I didn't see that is was dynamic updates from DHCP to forwarder/resolver.
Considering it's been a bug since 2.1 you can see how many people must rely on such functionality.
-
I didn't see that is was dynamic updates from DHCP to forwarder/resolver.
Considering it's been a bug since 2.1 you can see how many people must rely on such functionality.
Yeah I see how my use scenario is somewhat unique, hence why doktornotor is chewing me out.
-
Saw you linked to my post on the topic. Honestly I think this should be considered a true bug. The DHCP to DNS register scripts should never assume the FQDN pfsense resides in is the same for all DHCP clients. While i'm sure most home users are not doing complicated separated networks this is a very common thing in the enterprise world. (Don't lambaste me about doing DNS/DHCP with AD Domain Controller, I don't want to hear it and its not my use-case)
Anyways to the point, I think that redmine bug report needs to be updated and attached to the current release because its likely being ignored due to old version number.
Slightly off topic, I have been battling terrible unbound performance since the RC, I have updated root-hints and my DNS querys continually timeout requiring re-querying many times to finally get response. Perhaps i have the cache times set too low but still why would unbound be timing out all the time.
-
Have you debugged all the root hints you've updated to be sure they're all responding? Sniff port 53 on WAN and see where the problem really lies.
-
"why would unbound be timing out all the time."
You have shitty wan connectivity? Your hitting shitty nameservers? Nameservers are outside your region? Last root hint update was May 23, 2015 so not something that needs to be updated all that often. Are you having issues with IPv6 connectivity and your trying to hit the roots via ipv6?
Lots of reasons why you could be having timeout issues to be honest.. Did you edit the cache time?? Not something you should normally have to adjust?
So you have your DCs that are doing dns forward to your unbound on pfsense - maybe something in that process is slow?
