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

#1
22.1 Legacy Series / Re: DNS aliases not resolving
March 15, 2022, 01:22:24 AM
I got the same addresses via console over opnsense.

# dig +short outlook.microsoft.com
40.112.72.205
40.76.4.15
40.113.200.201
13.77.161.179
104.215.148.63


But these addresses don't show up in the Alias Overview(IP entries). I tried different forms URL, URLS. Only got the error alias resolve error outlook (error fetching alias url outlook.microsoft.com)  The url was only an example, because all domains which I tried ending up in this error. So in short, when adding domains into aliases for bringing the rules more dynamic against changing IPs, the IP wouldn't resolve.

Well, I tried for diagnostics the DNS lookup via webgui - works fine like the dig command. But always getting the fetching error when resolve it via aliases. Since now, no further diagnostics because I don't know where to start.

But I guess in general it's working, because else my clients and the firewall itself couldn't resolve it correctly. But where does the error hit in ? Script error ? False internal configuration?

#2
22.1 Legacy Series / Re: DNS aliases not resolving
March 06, 2022, 03:59:14 PM
Anyone ?

I am grateful for any help.
#3
22.1 Legacy Series / DNS aliases not resolving
March 05, 2022, 10:15:12 PM
Hello everyone,

I've similar issues as already raised up in 21.7 on 22.1.

https://forum.opnsense.org/index.php?topic=24265.msg116146#msg116146

When I'm using DNS aliases, for example outlook.microsoft.com the system can't resolve the addresses. In the logs I get:

   Error /update_tables.py alias resolve error outlook (error fetching alias url outlook.microsoft.com)

I'm using DNS over TLS via unbound DNS. DNS resolving for clients and Firewall itself is working, and I don't use or configured WireGuard at the moment.

Also tried the option:  Do not use the local DNS service as a name server for this system
Didn't give effect to it.

Have I missed something?


#4
Hello everyone,

I'm new to OpnSense and want to add a network area from a device which I cannot maintain in general.
So I decided to do a 1:1 Nat to mirror a subnet /24 to the other one.

I'm not sure if I'm able to do a 1:1 nat with a Trunk Interface. I've selected the interface which I configured the VLAN

for now, I configured an IP alias: 192.168.179.254/24

And the 1:1 nat with targeting to 192.168.99.1/24

But there is no connection, yet.

Any hints/ideas ?

Thank you in advance