Hi all.

I'm after some guidance as to the best way to implement the following.

I'm looking to move the Agency News NNTP server to a new domain name.

Current domain : news.bbs.geek.nz
New domain : news.bbs.nz

The IPv4 and IPv6 addresses associated with the current domain are also assigned to the new domain and remain unchanged.

I realise config settings in INN will need to be updated but am unsure
when to apply those changes and what the immediate impact may be on peers?

I will retain what will become the old domain name for some time after cut
over and ensure the IP resolution remains unchanged to allow peers time to
make any changes in their config.

I've just sorted email for the new domain so am really at the point where
I would like to make some changes.

Any thoughts or guidance as to the best way to make things smooth for all connected peers with news.bbs.geek.nz would be appreciated :)

Thanks guys.

Best, Paul.

--
Agency News | news.bbs.nz

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Le 07-03-2018, Kerr Avon nous expliquait dans
news.admin.peering
(<p7o30g$3if$3@news.bbs.geek.nz>) :

Hi all.

Hi,

I'm after some guidance as to the best way to implement the following.

I'm looking to move the Agency News NNTP server to a new domain name.

Current domain : news.bbs.geek.nz
New domain : news.bbs.nz

The IPv4 and IPv6 addresses associated with the current domain are also assigned to the new domain and remain unchanged.

I realise config settings in INN will need to be updated but am unsure
when to apply those changes and what the immediate impact may be on peers?

If your peers are previously alerted about your domain change planed date
AND if they applied these changes to their config, this should be transparent for them.

In my case, it needs modification on the two INN conf files that
configure our mutual peering. Totally painless.

For others that will try to contact your server through the old domain
while it is disabled, they only will be unable to do so. That's all.

The important thing is to alert all your peers long enough before your

I will retain what will become the old domain name for some time after cut over and ensure the IP resolution remains unchanged to allow peers time to make any changes in their config.

It sounds wise as some newsmasters may forgot to apply the needed changes
at time ;-)

But while you will have changed the "path" your server may receive from misconffigured servers some articles that originating from your server.

Again, alert your peers say one month before the change take place to
prevent some unnecessary incoming traffic.

I've just sorted email for the new domain so am really at the point where
I would like to make some changes.

Any thoughts or guidance as to the best way to make things smooth for all connected peers with news.bbs.geek.nz would be appreciated :)

Here you are. But this a "peer point of view" only advice.
I'm wondering if there is not some précautionary measures to be taken
before changing you domain name, path and servername.

Bye.
--
Je ne connaîtrai rien de tes habitudes
Il se peut même que tu sois décédée
Mais j'demanderai ta main pour la couper
-- H.F. Thiéfaine, L'ascenceur de 22H43

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Wed, 07 Mar 2018 10:47:51 +0000, Doug713705 wrote:

If your peers are previously alerted about your domain change planed
date AND if they applied these changes to their config, this should be transparent for them.

In my case, it needs modification on the two INN conf files that
configure our mutual peering. Totally painless.

For others that will try to contact your server through the old domain
while it is disabled, they only will be unable to do so. That's all.

The important thing is to alert all your peers long enough before your

Yep agreed. I will post a formal update here and revise the info on the
website as well. I'll send emails to all the peers I have contact for and
set a date one month from when I send things out to when I cut over to the
new domain name and path.

I will retain what will become the old domain name for some time after
cut over and ensure the IP resolution remains unchanged to allow peers
time to make any changes in their config.

It sounds wise as some newsmasters may forgot to apply the needed
changes at time ;-)

Thanks, yes I'll keep the old domain name and IP addresses intact for
several months just to be sure. But hopefully most will cut over to the
new domain name sooner than later.

But while you will have changed the "path" your server may receive from misconffigured servers some articles that originating from your server.

Again, alert your peers say one month before the change take place to
prevent some unnecessary incoming traffic.

OK

Any thoughts or guidance as to the best way to make things smooth for
all connected peers with news.bbs.geek.nz would be appreciated :)

Here you are. But this a "peer point of view" only advice.
I'm wondering if there is not some précautionary measures to be taken
before changing you domain name, path and servername.

Hence the post here - thanks for your reply, you've been the only one so
far which surprised me, but I do appreciate the guidance :)

Bye.

Best, Paul




--
Agency News | news.bbs.nz

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)