Split DNS (I know, I know)…
-
Ok, so I have done this and it's behaving oddly.
When I designate a port number:
home.example.us:xxxx
I get nothing, just a timeout.
When I type just the address without the port it brings up the pfsense box login (10.0.1.1). It seems to me that if I just type in the address is should at least point to the host's designated ip (10.0.1.5) and show the NAS box login.
The host is setup according to the pfesense documentation in the DNS Forwarder.
This is the issue I was having before.
-
Do you have multiple local interfaces and subnets? You need proper firewall rules if so.
-
It's an APU with a very simple setup:
1 WAN (re0)
1 LAN (bridged over re1, re2) with a Ubiquity WAP plugged into re2 and the NAS into re1. The rest of the house is wifi. -
Well, something is keeping the traffic from getting to the host. Check your firewall logs.
-
I have, checked both and nothing looks to be tied to what I'm trying to do. The firewall logs show literally hundreds of the entry shown in the attached screenshot.
 -
That's DHCP on WAN. Unfortunate but completely unrelated to your problem.
-
Yeah, figured that out just before I read your comment.
So, I have DNS Forwarded on with:
"Register DHCP leases in DNS forwarder" Checked
"Register DHCP static mappings in DNS forwarder" CheckedThe host override for the dyn address is configured.
DNS in general settings is listed as follows (to be pushed to clients)
1. 10.0.1.1
2. 8.8.4.4
3. 156.154.71.1The macbook is not configured for it's own DNS it's only pulling from pf dhcp (so when you open that settings box DNS reflects the 10.0.1.1).
When I type the domain home.example.us into the browser is pulls up the pfsense web GUI (10.0.1.1). To me it should pull up 10.0.1.5 as the forwarder is configured to do so.
Ran a traceroute:
Traceroute has started… traceroute to home.example.us (184.167.179.204), 64 hops max, 72 byte packets 1 host-184-167-179-215.csp-wy.client.bresnan.net (184.167.179.215) 3.954 ms 1.046 ms 1.163 msSo, it would seem that the DNS on PF is not doing it's job as this should come back with the box redirecting this host to a 10.0.1.5. No?
Firewall logs are clean and nothing shows the activity.
What I think is happening is PF is passing the host along to the DYN service which is then boomeranging the browser back to the WAN IP, hence the PF web GUI when I type it in.PF Doesn't respond to port 80 on the WAN.When I add ports is just hangs as always, but I think it logical to conclude that the PF box is not redirecting the host as it should?
-Colter
-
Redirecting what?? Are you really uisng home.example.com???
dude from a cmd line if you ping home.example.com and it doesn't return the private IP you put in the over ride then you did it WRONG!!!
This not freaking brain surgery here!!
I like to help people but sometimes I just am at complete loss for words how simple this is!! If its not working - is your client even using pfsense for dns?? Did you put your over ride in the forwarder section and your using the resolver "unbound" ?
-
You cannot push DNS servers to clients that will return different answers to the same queries and expect things to work. You can leave the pfSense DNS servers alone (Though I have no idea why you have 10.0.1.1 listed there. It should probably be removed.)
In your DHCP settings, tell the server to push the IP address of pfSense to your clients - usually the same IP as the default gateway. Nothing else. If you want two internal DNS servers, then you have to configure another one that will return the same answers to the same queries.
-
johnpoz:
No, no I am not. I replaced my DYN address with example.us for my own comfort reasons.
While I appreciate your input, try not to be rude to me. Humbly, I'm actually a very smart person and it's worth noting that I have felt frustrations with others when I find their problems elementary/minuscule in nature; but try to not degrade people.
I understand that there is a problem within the settings. What I can't find is where that error is as even everything you stated I have gone over and have a full understanding of.
If you read the last post I wrote you will see that I covered the part about ensuring my client (macbook) is using pfsense as it's primary DNS server, and the forwarder is setup with the host I am attempting to intercept.
I would say the only part about what you've stated that I don't connect to is this "unbound" terminology. I haven't seen that referenced in the literature I've read so far.
It's easy to be smart, it's harder to be kind. Especially when it's text on a screen with a shade of anonymity.
Thank you for your insights, I do appreciate what was constructive. :)
Derelict:
Thank you. I'll make the edits. I put the 10.0 in the list to just ensure the clients where getting the pfsense box as the first source (another member thought it worth the test). I'll fiddle with DHCP to ensure clients are getting the proper DNS.
-
If you read the last post I wrote you will see that I covered the part about ensuring my client (macbook) is using pfsense as it's primary DNS server, and the forwarder is setup with the host I am attempting to intercept.
There is no "interception" involved. When an internal host asks for the IP address of server1.example.com, it should get the internal address in response.
When an external host asks the global DNS for the IP address of server1.example.com, it should get the external address.
It's really that simple. Drop-dead easy with host overrides in pfSense's DNS Forwarder or DNS Resolver.
-
Ok, got that, poorly expressed on my part, but I understand that premise.
I did an NS lookup and this is what I get from the mac:
Samuels-MBP:~ Colter$ nslookup > home.example.us Server: 10.0.1.1 Address: 10.0.1.1#53 Non-authoritative answer: Name: home.example.us Address: 184.167.179.215I checked and double checked that DNS is properly set on the mac to the PFsense box. The forwarder is on and configured to the exact point of the PF documentation with the host and everything as specified.
-
"to is this "unbound" terminology. I haven't seen that referenced in the literature I've read so far. "
Really haven't seen this anywhere? If you do a search on the forums for unbound, there are 13 pages of results.. On the 2.2 new stuff doc
https://doc.pfsense.org/index.php/2.2_New_Features_and_Changes
DNS Resolver (unbound) enabled for new installs. #3396
DNS Forwarder (dnsmasq) disabled for new installs. #3396Dude post up pictures of your over ride!!
-
What, exactly, is entered in the host override in the forwarder. In that case you want:
Host: home
Domain: example.us
IP Address: internal_ip_address -
"to is this "unbound" terminology. I haven't seen that referenced in the literature I've read so far. "
Really haven't seen this anywhere? If you do a search on the forums for unbound, there are 13 pages of results.. On the 2.2 new stuff doc
https://doc.pfsense.org/index.php/2.2_New_Features_and_Changes
DNS Resolver (unbound) enabled for new installs. #3396
DNS Forwarder (dnsmasq) disabled for new installs. #3396Dude post up pictures of your over ride!!
I am reading and following this: https://doc.pfsense.org/index.php/Why_can%27t_I_access_forwarded_ports_on_my_WAN_IP_from_my_LAN/OPTx_networks%3F
I wouldn't have searched for "unbound" on the forums as it's term I haven't learned yet..
What, exactly, is entered in the host override in the forwarder. In that case you want:
Host: home
Domain: example.us
IP Address: internal_ip_addressExactly that, to the T.
-
"Exactly that, to the T. "
No you don't or it would be working.. You sure you have the forwarder enabled and not the resolver (unbound).. Lets see your services tab, and your over ride tab.. I showed you mine..
See attached, the difference in the forwarder screen and the resolver screen, notice the forwarder part of the resolver.. If your putting the over rides in the wrong section they they will not work.
-
Sorry. Always works for me.
If you're using 2.1 do this:
Diagnostics > Command Prompt
Execute Shell Command Command: dig @ip.address.of.forwarder.used.by.hosts.for.dns home.example.usIf you're using 2.2 do this:
Diagnostics > Command Prompt
Execute Shell Command Command: drill @ip.address.of.forwarder.used.by.hosts.for.dns home.example.usWhat does it say?
-
Ok, so running down the unbound resolver; it is indeed running.
The host settings I'm editing are in the services->DNS Forwarder. I noticed that in the Services->DNS Resolver under advanced there is also a host section that mimics what is found under the DNS Forwarder Section.
After some reading, the two are a one or the other scenario, yes? So, do I need to undo the Forwarder and enter the host into the Resolver to keep unbound running or should I disable unbound to revert back to dnsmasq (I did note that the documentation says to disable unbound to use resolver, but not that it's best practice if there is a better way).
Edit: after looking at John's screenshot I answered my own question maybe. Editing….
Edit 2:
Success!!! So it seems the entire issue was the confusion around the forwarder and the resolver and my lack of knowledge about the unbound change in 2.2. So John, thank you for pointing me in the right direction.
Derelict, thank you for your patience and continuing help.
-
Yes. With the forwarder disabled the forwarder host overrides do nothing. While you're in there go into the Advanced settings tab and check Harden Glue and Harden DNSSEC data. Another thread. Just trust me.
-
Yes. With the forwarder disabled the forwarder host overrides do nothing. While you're in there go into the Advanced settings tab and check Harden Glue and Harden DNSSEC data. Another thread. Just trust me.
Ok, done deal. Link to thread? Would love to know the why's.
