znc keeps using old system dns resolvers even after theyre changed? #690

Closed
opened 2026-10-05 04:38:53 +02:00 by adam · 7 comments
Owner

is that how znc works? because i was having trouble all day with my dns messing up so znc was unable to connect to anything. and then when i finally fixed the system dns, znc continued to not work until i restarted it. so it seemed like znc continued to use the old dns servers instead of getting the new system ones. not sure if this always happens or if it was a special case

<_status> ZNC 1.6.3 - http://znc.in
<_status> IPv6: yes, SSL: yes, DNS: threads, charset: no

CentOS 6.7

is that how znc works? because i was having trouble all day with my dns messing up so znc was unable to connect to anything. and then when i finally fixed the system dns, znc continued to not work until i restarted it. so it seemed like znc continued to use the old dns servers instead of getting the new system ones. not sure if this always happens or if it was a special case <_status> ZNC 1.6.3 - http://znc.in <_status> IPv6: yes, SSL: yes, DNS: threads, charset: no CentOS 6.7 <!-- github-sync-id:142800368 -->
adam closed this issue 2026-10-05 04:38:53 +02:00
Author
Owner

Try restarting znc

Try restarting znc <!-- github-comment-id:200062984 -->
Author
Owner

It just uses getaddrinfo() to resolve DNS, as the majority of other software...

It just uses `getaddrinfo()` to resolve DNS, as the majority of other software... <!-- github-comment-id:200064218 -->
Author
Owner

it didnt seem to pick up any of my dns changes until i restarted it. only then did it start resolving hosts again. idk

it didnt seem to pick up any of my dns changes until i restarted it. only then did it start resolving hosts again. idk <!-- github-comment-id:200075307 -->
Author
Owner

well if it does what every other software does maybe something else caused it somehow. now i know i can restart it if it happens again. so you can close this if you think theres no problem with znc

well if it does what every other software does maybe something else caused it somehow. now i know i can restart it if it happens again. so you can close this if you think theres no problem with znc <!-- github-comment-id:200075577 -->
Author
Owner

had this happen again on another server. i set up unbound to manage my dns requests and every application was able to start resolving hosts using the new resolvers but znc wouldnt. it needed to be restarted

had this happen again on another server. i set up `unbound` to manage my dns requests and every application was able to start resolving hosts using the new resolvers but znc wouldnt. it needed to be restarted <!-- github-comment-id:202456666 -->
Author
Owner

I think /etc/resolv.conf had some option for telling everything to always read it which is said to be a bad idea and searx says that you should service network restart.

I think `/etc/resolv.conf` had some option for telling everything to always read it which is said to be a bad idea and [searx](https://searx.me/?q=centos%20reload%20/etc/resolv.conf&categories=general) says that you should [service network restart](https://www.centos.org/forums/viewtopic.php?t=41520). <!-- github-comment-id:202763378 -->
Author
Owner

kk ill try that next time

kk ill try that next time <!-- github-comment-id:202812419 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/znc#690