I have recently changed the IP address of my news server, also updated
the DNS entry. Issue is, the sites I peer with seem to update the IP
address associated to the hostname, meaning that my server cannot
recieve feeds from them, nor are they pulling feeds from mine.
Does anyone have experience with that issue? Don't want to wait a few
days just to find out they have to restart INN or something in that
way.
Does anyone have experience with that issue? Don't want to wait a few
days just to find out they have to restart INN or something in that way.
Does anyone have experience with that issue? Don't want to wait a few
days just to find out they have to restart INN or something in that way.
I didn't check the "current" code (still running inn < 2.3 with real tradspool (i.e no changed overview file naming scheeme)), but in the past
inn did the name/ip resolution _only_ at startup (it's not a bug, it's a feature)
Elia wrote:
Does anyone have experience with that issue? Don't want to wait a few
days just to find out they have to restart INN or something in that
way.
I didn't check the "current" code (still running inn < 2.3 with real tradspool (i.e no chnaged overview file naming scheeme)), but in the
past inn did the name/ip resolution _only_ at startup (it's not a bug,
it's a feature); so yes - you likely have to inform your peers about the ip-change so they can restart thier instances.
I have recently changed the IP address of my news server, also updated
the DNS entry. Issue is, the sites I peer with seem to update the IP
address associated to the hostname, meaning that my server cannot
recieve feeds from them, nor are they pulling feeds from mine.
Elia <me@elia.li> writes:
I have recently changed the IP address of my news server, also updated
the DNS entry. Issue is, the sites I peer with seem to update the IP
address associated to the hostname, meaning that my server cannot
recieve feeds from them, nor are they pulling feeds from mine.
Does anyone have experience with that issue? Don't want to wait a few
days just to find out they have to restart INN or something in that
way.
Depends on the server, but with INN, the peer must use ctlinnd to reload incoming.conf. Many servers do this automatically once a day. Because of
this it’s worth a note to peers when you renumber (and also worth
keeping renumbering very rare!)
In my logs, there’s an outage for your server overnight between approximately 2330 and 0302 UTC (when my daily reload happens), after
which connectivity returns to normal.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 300 |
Nodes: | 16 (2 / 14) |
Uptime: | 61:50:10 |
Calls: | 6,712 |
Files: | 12,244 |
Messages: | 5,355,818 |