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 - mdecou

#1
So I recently noticed some odd behavior with my DNS (unbound) as follows:

When pinging my domain name, (ie: ping myhost.net) the system returns 127.0.0.1 instead of my public IP address.
When pinging other hosts on the LAN, things go as expected.
If i ping a random host that does not exist (ie: ping fakehost) the system again returns 127.0.0.1 where I would expect it to return an error.

Is this expected behavior, or does it appear I have a configuration issue?

Thanks
#2
Hi,
I just moved from googledomains over to ClouDNS.   I am trying to get the ACME client setup, but cannot seem to get validation of the challenge to work.   Has anyone had success with this?    I was unable to find any documentation, other than ensuring that an API Auth-ID and password were set.

Thanks for any feedback.
#3
Hello,

I have seen a few posts online from a while back asking about support in ACME clients for Google Domains.   I am now looking into this and found on the Google Domains website that they now have an API for integration into ACME clients.   

Has anyone seen any updates regarding integration of Google Domains support within the ACME Client package in OPNSense?

Thanks
#4
Hello all,

I have just setup opnsense for the first time (long time pfSense user) and have found a bit of an odd behavior.   I have setup a host override in Unbound that identifies my LAN interface (192.168.1.1) as host "opnsense".

When I ping "opnsense", I get a reply from my WAN IP Adress.   I suspect there is a simple setting I need to set, but cannot find it.

Thanks for any help or suggestions.

Mike