Messages

1

23.1 Legacy Series / Re: Unbound Log pythonmod dnsbl_module TypeError

« on: May 16, 2023, 03:50:36 pm »

I changed the log level verbosity and logs started flowing again. I'm not going to argue with it, but it seems to have rotated the logs as well so perhaps there was something in the log that was not parsable by the python module.

2

23.1 Legacy Series / Unbound Log pythonmod dnsbl_module TypeError

« on: May 15, 2023, 04:10:38 pm »

When I look at Unbound logs I only see the below code block, nothing more, on a single page. The system appears to be working as far as DNS and routing traffic. The OPNsense Unbound DNS is pointing to a PiHole on another host. I have tried rebooting opnsense, also tried restarting unbound from the web ui, but this message is all that is in the log section.

Setup:

Code: [Select]

OPNsense 23.1.7_3-amd64
FreeBSD 13.1-RELEASE-p7
OpenSSL 1.1.1t 7 Feb 2023
Intel(R) Celeron(R) G5905 CPU @ 3.50GHz (2 cores, 2 threads)


Code: [Select]

TypeError: an integer is required (got type NoneType)
os.write(self._pipe_fd, res.encode())
File "dnsbl_module.py", line 226, in log_entry
logger.log_entry(query)
File "dnsbl_module.py", line 547, in operate
2023-05-04T22:41:56-04:00 Error unbound [77322:0] error: pythonmod: python error: Traceback (most recent call last):
2023-05-04T22:41:56-04:00 Error unbound [77322:0] error: pythonmod: Exception occurred in function operate, event: module_event_moddone
2023-04-25T17:02:32-04:00 Error unbound [53030:1] error: duplicate forward zone . ignored.
2023-04-25T17:02:32-04:00 Error unbound [53030:0] error: duplicate forward zone . ignored.
2023-04-25T16:01:41-04:00 Error unbound [82376:1] error: duplicate forward zone . ignored.
2023-04-25T16:01:41-04:00 Error unbound [82376:0] error: duplicate forward zone . ignored.
2023-04-25T16:01:37-04:00 Error unbound [73365:1] error: duplicate forward zone . ignored.
2023-04-25T16:01:37-04:00 Error unbound [73365:0] error: duplicate forward zone . ignored.
2023-04-25T15:21:09-04:00 Error unbound [43100:1] error: duplicate forward zone . ignored.
2023-04-25T15:21:09-04:00 Error unbound [43100:0] error: duplicate forward zone . ignored.
2023-04-25T14:41:53-04:00 Error unbound [27984:1] error: duplicate forward zone . ignored.
2023-04-25T14:41:53-04:00 Error unbound [27984:0] error: duplicate forward zone . ignored.
2023-04-25T14:41:50-04:00 Error unbound [23086:1] error: duplicate forward zone . ignored.
2023-04-25T14:41:50-04:00 Error unbound [23086:0] error: duplicate forward zone . ignored.


3

General Discussion / Plex.direct trying all local docker ip addresses

« on: April 23, 2023, 01:35:23 am »

Running OPNsense 23.1.6-amd64

I just switched out my router for an opnsense setup and followed a few guides on getting plex to work. One of the steps was to set plex.direct as a private domain in Services > Unbound DNS > Advanced.

I also set a host override:

Code: [Select]

plex.direct private-domain A (IPv4 address) 192.168.1.150

Now when I'm trying to connect to plex from within my LAN it takes a really long time to load anything and from the Unbound Reporting it seems that all of the docker ip addresses are being tried during resolution.

Code: [Select]

172-28-0-1.abcdefghijklmnopqrstuvwxyz012345.plex.direct. Pass Recursion NOERROR 58ms 300
2023-04-22 19:26:46 mediabox.localdomain A 172-28-0-1.abcdefghijklmnopqrstuvwxyz012345.plex.direct. Pass Recursion NOERROR 24ms 86400
2023-04-22 19:26:46 mediabox.localdomain AAAA 192-168-1-150.abcdefghijklmnopqrstuvwxyz012345.plex.direct. Pass Recursion NOERROR 139ms 300
2023-04-22 19:26:46 mediabox.localdomain A v4.plex.tv. Pass Recursion NOERROR 152ms 60
2023-04-22 19:26:46 mediabox.localdomain AAAA 192-168-176-1.abcdefghijklmnopqrstuvwxyz012345.plex.direct. Pass Recursion NOERROR 215ms 300
2023-04-22 19:26:46 mediabox.localdomain A 192-168-176-1.abcdefghijklmnopqrstuvwxyz012345.plex.direct. Pass Recursion NOERROR 110ms 86400

Not quite sure what is happening here.