ended up learning how to create alias hosts with a ton of websites. and sent them over a different gateway
brain got some new wrinkles this morning. thumbsup :)
If you let me know the IP via PM I'll drop it from the ban list... probably from a spam account.
Cheers,
Franco
i would rather keep the spammers out. it was a IVPN wireguard tunnel used at the time, so def shared address
been wanting to set this up for a while. its strange only a few websites still do not work, im guessing they don't have their domain setup correctly. no clue and not that important to me :)
is there a way to decrease the time it checks for hostname updates under alias? or is 5-6 minutes expected
2026-02-09T04:58:01-05:00
Notice
firewall
resolving 199 hostnames (265 addresses) for webtowan took 0.84 seconds
2026-02-09T04:52:01-05:00
Notice
firewall
resolving 199 hostnames (274 addresses) for webtowan took 1.01 seconds
2026-02-09T04:46:01-05:00
Notice
firewall
resolving 199 hostnames (267 addresses) for webtowan took 1.03 seconds
2026-02-09T04:40:01-05:00
Notice
firewall
resolving 198 hostnames (264 addresses) for webtowan took 1.21 seconds
2026-02-09T04:34:01-05:00
Notice
firewall
resolving 198 hostnames (267 addresses) for webtowan took 0.74 seconds
2026-02-09T04:28:01-05:00
Notice
firewall
resolving 200 hostnames (266 addresses) for webtowan took 0.73 seconds
2026-02-09T04:22:01-05:00
Notice
firewall
resolving 201 hostnames (266 addresses) for webtowan took 0.91 seconds
2026-02-09T04:16:01-05:00
Notice
firewall
resolving 199 hostnames (266 addresses) for webtowan took 0.75 seconds
2026-02-09T04:10:01-05:00
Notice
firewall
resolving 200 hostnames (261 addresses) for webtowan took 0.75 seconds
2026-02-09T04:04:01-05:00
Notice
firewall
resolving 198 hostnames (259 addresses) for webtowan took 0.79 seconds
2026-02-09T03:58:01-05:00
Notice
firewall
resolving 199 hostnames (260 addresses) for webtowan took 0.83 seconds
2026-02-09T03:52:01-05:00
Notice
firewall
resolving 200 hostnames (260 addresses) for webtowan took 0.81 seconds
2026-02-09T03:46:01-05:00
Notice
firewall
resolving 199 hostnames (265 addresses) for webtowan took 1.02 seconds
2026-02-09T03:40:01-05:00
Notice
firewall
resolving 199 hostnames (263 addresses) for webtowan took 0.92 seconds
2026-02-09T03:34:01-05:00
Notice
firewall
resolving 199 hostnames (263 addresses) for webtowan took 0.74 seconds
2026-02-09T03:28:02-05:00
Notice
firewall
resolving 198 hostnames (255 addresses) for webtowan took 1.35 seconds
2026-02-09T03:22:02-05:00
Notice
firewall
resolving 200 hostnames (262 addresses) for webtowan took 1.01 seconds
2026-02-09T03:16:01-05:00
Notice
firewall
resolving 198 hostnames (266 addresses) for webtowan took 0.79 seconds
Ok makes sense.
I think the update frequency is hardcoded. Would make sense to raise a ticket to discuss this. In general the system is configurable but the GUI doesn't show.
Cheers,
Franco
Edit: I just found that it depends on Type
URL Table: Refresh Frequency
I only have 1 alias where Type = Host(s). I change the default value here:
Firewall: Settings: Advanced
Aliases Resolve Interval [default (300s).]
my value = 14400
The new value is honored. Is this something different than the original post?
It's going to be configurable in 26.1.2, see https://github.com/opnsense/core/issues/9767
Yay for tickets :D
Cheers,
Franco
Quote from: vimage22 on Today at 02:43:15 PMEdit: I just found that it depends on Type
URL Table: Refresh Frequency
I only have 1 alias where Type = Host(s). I change the default value here:
Firewall: Settings: Advanced
Aliases Resolve Interval [default (300s).]
my value = 14400
The new value is honored. Is this something different than the original post?
great question. I just changed my setting to 604800
I should know fairly quickly
well. I didn't know that option was there, its been 40+ minutes and a new log has not appeared
@franco this is my fault ill let your team decide on that GitHub request.
at the same time. if someone thinks its better to have a faster check for host alias update times. please education me, I am all ears on this subject. I am not a firewall expert I lean on the community