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
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 -->
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 -->
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 -->
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 -->
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 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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
Try restarting znc
It just uses
getaddrinfo()to resolve DNS, as the majority of other software...it didnt seem to pick up any of my dns changes until i restarted it. only then did it start resolving hosts again. idk
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
had this happen again on another server. i set up
unboundto manage my dns requests and every application was able to start resolving hosts using the new resolvers but znc wouldnt. it needed to be restartedI think
/etc/resolv.confhad 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.kk ill try that next time