PfSense blocking nameservers on Virtualmin?
-
Thank you for providing the name servers.
Unfortunately, the name server settings are not easy to find.
I remember seeing your mentioned name server settings through the steps of setting up the 1st domain, however I expected the settings to be provided at the end of the setup process.
Unfortunately, the settings weren't provided at the end of the setup process, so I clicked 'back' several time to see the previous setup step with your mentioned name server settings, but they were no longer shown.I checked your website and the Free DNS link and the settings aren't there either, so basically the navigation path to the settings could improve for some user friendly navigation.
-
Thank you for providing the name servers.
Unfortunately, the name server settings are not easy to find.
I checked your website and the Free DNS link and the settings aren't there eitherOh really? This is what is shown directly after logon… I'd frankly call that damn impossible to miss!
-
Yes, that looks very clear.
However the issue is navigating to find that specific nameserver information.I just did a login as your example looks very easy to see the information after login, however this doesn't appear for me when I login.
Anyways, 1st issue is to fix pfSense to allow DNS packets through port 53.
2. Let modem login with default username and password which works when connected to this local computer, but when connected to pfSense, I access the modem from this local computer through pfSense, but the modem default username and password won't work.
3. Fix my DNS settings.
4. Use your DNS settings if I can't get mine to work.
-
"1st issue is to fix pfSense to allow DNS packets through port 53."
Dude there is NOTHING to fix with pfsense - YOU CAN NOT forward packets pfsense does not SEE!!! Your MODEM is not in DMZ mode, your not sending udp/tcp 53 to pfsense - so what is there to fix on pfsense????
As to not logging into your modem when you connect pfsense - come on, really? That makes NO sense at all.. Did you try a different browser? Why don't you sniff the traffic and validate what what pfsense sends to your modem.. If pfsense was mangling the login – then most likely any website on the planet that was http would would not log in.
Did you clear your browser cache? Or you using proxy on pfsense? I did not notice it when was on.
I can assure you that name servers are right there on the page dns.he.net, screaming at you to what Nameservers to point to -- but once you create a zone.. Then it goes away.. But will be listed in the zone!!
So clearly you didn't bother reading what you were looking at before you clicked clicked and then didn't even look to what you were creating.. They are impossible to miss when looking at your zone.
Dude I really do want to help you -- but its becoming a PITA!! Every single time I connect to via TV there is something wrong, you can not login to your box running centos (dns server) Was pfsense mangling that password inside a ssh session as well? Mouse doesn't work, You can not login to your modem.. etc.. etc.. etc..
This is really freaking basic shit here.. First your "modem" needs to send the traffic to pfsense!!! Set DMZ to your pfsense wan IP.. 192.168.0.2 I believe. Then create the forward/nat - this is like 2 clicks. Put your IP you want to send to, and what service (dns) and pick udp/tcp
Your now done -- this is 1 minute of work.. We have been dicking with this for what a month? I have tried to help you - to be honest I think your just freaking trolling having a laugh on us.. Nobody can be this dense..
-
Okay, well, the website seems to be showing now.
However only the home page, the others won't load outside the WAN.
I don't have any time to get into the details right now, but thought I would update. -
Yeah NO – your dns is NOT responding.. So I don't know what you think is working.. But your domain still points to same IP it did, and NO it does not respond to dns query.
; <<>> DiG 9.9.3-rpz2+rl.13214.22-P2-Ubuntu-1:9.9.3.dfsg.P2-4ubuntu1.1 <<>> @124.xx.xx.67 www.yourdomain.tld
; (1 server found)
;; global options: +cmd
;; connection timed out; no servers could be reached -
One year later: cannot check whether it works since the domain expired. :D
-
I really want to help the guy - so I have been TV'd in and accessed his modem before, but now it seems pfsense is messing with the password so it doesn't work? :rolleyes:
I have been remote to his system like 5 times now and every single time is something else that prevents me from doing the most basic things. He can not ssh to his server, he can not login to virtualmin, mouse doesn't work so I can not control. It did work until he reset his modem again.
This is like 2 minutes
Set modem to DMZ (since he does not want to bridge?? or can not?) to his pfsense wan - setup forward on pfsense (click) = done.. It is frustrating to say the least.. He clearly should not be hosting anything off his own connection. Be it dns or some site be it even for his own access