1
General Discussion / Re: DNS not resolving after reboot
« Last post by Sparkey on Today at 06:49:35 pm »Thanks!
I assume it is not resolving from the Wan site to get to the pool?
0.opnsense.pool.ntp.org
2024-04-05T12:17:03-05:00 Informational ntpd 174.53.169.69 local addr [REDACTED] -> <null>
2024-04-05T12:16:43-05:00 Informational ntpd 135.148.100.14 local addr [REDACTED] -> <null>
2024-04-05T12:16:02-05:00 Informational ntpd 69.10.223.131 local addr [REDACTED] -> <null>
2024-04-05T12:15:51-05:00 Informational ntpd 44.190.40.123 local addr [REDACTED] -> <null>
as well as warning
024-04-05T11:49:32-05:00 Error ntpd daemon child exited with code 1
2024-04-05T11:49:32-05:00 Error ntpd unable to bind to wildcard address :: - another process may be running - EXITING
2024-02-21T13:45:49-06:00 Error ntpd daemon child exited with code 1
2024-02-21T13:45:49-06:00 Error ntpd unable to bind to wildcard address :: - another process may be running - EXITING
2024-01-31T12:58:06-06:00 Error ntpd daemon child exited with code 1
2024-01-31T12:58:06-06:00 Error ntpd unable to bind to wildcard address :: - another process may be running - EXITING
2024-01-30T10:43:04-06:00 Error ntpd daemon child exited with code 1
2024-01-30T10:43:04-06:00 Error ntpd unable to bind to wildcard address :: - another process may be running - EXITING
2024-01-30T10:36:31-06:00 Error ntpd daemon child exited with code 1
2024-01-30T10:36:31-06:00 Error ntpd unable to bind to wildcard address :: - another process may be running - EXITING
2023-12-12T14:45:19-06:00 Error ntpd daemon child exited with code 1
2023-12-12T14:45:19-06:00 Error ntpd unable to bind to wildcard address :: - another process may be running - EXITING
2023-11-09T21:38:06-06:00 Error ntpd daemon child exited with code 1
2023-11-09T21:38:06-06:00 Error ntpd unable to bind to wildcard address :: - another process may be running - EXITING
2023-11-07T08:14:36-06:00 Error ntpd error resolving pool 3.opnsense.pool.ntp.org: Name does not resolve (
I assume it is not resolving from the Wan site to get to the pool?
0.opnsense.pool.ntp.org
2024-04-05T12:17:03-05:00 Informational ntpd 174.53.169.69 local addr [REDACTED] -> <null>
2024-04-05T12:16:43-05:00 Informational ntpd 135.148.100.14 local addr [REDACTED] -> <null>
2024-04-05T12:16:02-05:00 Informational ntpd 69.10.223.131 local addr [REDACTED] -> <null>
2024-04-05T12:15:51-05:00 Informational ntpd 44.190.40.123 local addr [REDACTED] -> <null>
as well as warning
024-04-05T11:49:32-05:00 Error ntpd daemon child exited with code 1
2024-04-05T11:49:32-05:00 Error ntpd unable to bind to wildcard address :: - another process may be running - EXITING
2024-02-21T13:45:49-06:00 Error ntpd daemon child exited with code 1
2024-02-21T13:45:49-06:00 Error ntpd unable to bind to wildcard address :: - another process may be running - EXITING
2024-01-31T12:58:06-06:00 Error ntpd daemon child exited with code 1
2024-01-31T12:58:06-06:00 Error ntpd unable to bind to wildcard address :: - another process may be running - EXITING
2024-01-30T10:43:04-06:00 Error ntpd daemon child exited with code 1
2024-01-30T10:43:04-06:00 Error ntpd unable to bind to wildcard address :: - another process may be running - EXITING
2024-01-30T10:36:31-06:00 Error ntpd daemon child exited with code 1
2024-01-30T10:36:31-06:00 Error ntpd unable to bind to wildcard address :: - another process may be running - EXITING
2023-12-12T14:45:19-06:00 Error ntpd daemon child exited with code 1
2023-12-12T14:45:19-06:00 Error ntpd unable to bind to wildcard address :: - another process may be running - EXITING
2023-11-09T21:38:06-06:00 Error ntpd daemon child exited with code 1
2023-11-09T21:38:06-06:00 Error ntpd unable to bind to wildcard address :: - another process may be running - EXITING
2023-11-07T08:14:36-06:00 Error ntpd error resolving pool 3.opnsense.pool.ntp.org: Name does not resolve (