Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - Verxion

#1
Yes, it is (as I had written in the post above) the FW IP.

I was doing it because of that video that I linked.  From what I'd read, it is there to allow any DHCP client to make (over TCP/UDP) their DNS (over port 53) requests from the OPNSense box....

-Verxion
#2
IPv4 TCP/UDP * * {FW IP} 53(DNS) * *
LAN * * * LB_GW *

-Verxion

P.S. THANK YOU for your help - I truly appreciate it!!!
#3
I did.  I followed the steps in this video:

https://youtu.be/CcXYiFj9mBA?si=oofB_qGx566OsQKc

-Verxion
#4
I'm having a LOT of trouble doing what feels like it should be incredibly simple...

I've got all my home lab devices pointed to my OPNsense server for DHCP, as their gateway, and their DNS.

...they all get IPs (I have them each set up with static assignment in DHCPv4), they all end up with the OPNsense server IP for DNS... but NONE of them can resolve hosts.

If I ssh into the OPNsense server itself, then I can resolve hosts just fine, including any manually defined local aliases (I specify them in Overrides), but none of the DHCP clients can resolve IPs from hostnames.

I'm really struggling with how to get this resolved.... Here are the pertinent bits of configuration:

Systems->Settings->General->DNS Servers is set with 8.8.8.8 (WAN1_GW) and 8.8.4.4 (WAN2_GW)

Services->DHCPv4->LAN->DNS has OPNsense IP address

DHCP enabled for LAN interface, all potential clients have static assignment based on MAC address

Unbound DNS enabled items:
  Register DHCP Leases
  Register DHCP Static Mappings
  Flush DNS Cache during reload

Again - IP resolution is working from OPNsense server but not from ANY DHCP client.

Thanks so much for any help anyone can provide!!  :)

-Verxion