From Newsgroup: uk.telecom.broadband

We will be getting our new CityFibre FTTP connection on Wednesday.

Currently we have PlusNet FTTC with a static IPV4 address, the new
(IdNet) FTTP connection also has a static IPV4 address.

The system has a domain name hosted at Gandi internet and, obviously,
I will need to change the settings of the zone file there to point to
the new IP address. There will be a period while the new address
propagates when both addresses will exist.

So, is there any way that I can set things up so that connections (in particular SMTP mail, I run Postfix as a mail server) to either
address will still reach my system?

If I configure just one of the two WAN facing routers to provide DHCP
services can I then connect the LAN side of the two routers together
and get what I want? Then wait until the new IPV4 address for my
domain has propagated and, when it has, disable the FTTC router and
transfer DHCP/DNS etc. wholly to the FTTP router.

Does this have a hope of working or have I overlooked something?
--
Chris Green
-+
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.broadband

Chris Green <cl@isbd.net> wrote:

We will be getting our new CityFibre FTTP connection on Wednesday.

Currently we have PlusNet FTTC with a static IPV4 address, the new
(IdNet) FTTP connection also has a static IPV4 address.

The system has a domain name hosted at Gandi internet and, obviously,
I will need to change the settings of the zone file there to point to
the new IP address. There will be a period while the new address
propagates when both addresses will exist.

So, is there any way that I can set things up so that connections (in particular SMTP mail, I run Postfix as a mail server) to either
address will still reach my system?

If I configure just one of the two WAN facing routers to provide DHCP services can I then connect the LAN side of the two routers together
and get what I want? Then wait until the new IPV4 address for my
domain has propagated and, when it has, disable the FTTC router and
transfer DHCP/DNS etc. wholly to the FTTP router.

Does this have a hope of working or have I overlooked something?

If you have one router you can in principle configure it with two upstream routes. ie you get two WAN IPv4 addresses, and you can decide where the traffic gets routed - ie you write a default route which says to send
traffic to the upstream route of ISP A rather than ISP B.

But I think you have two ISP routers which are both doing NAT, so you are
not exposed to the WAN side of things?

First of all, make sure the IP address ranges don't clash. They need to be entirely separate subnets - eg 192.168.1.x/24 and 192.168.2.x/24.

You can't connect the two networks together but what
you can do is connect both networks to the same server if it has two
ethernet ports. Then your mail server gets IP addresses in both 192.168.1.x and 192.168.2.x ranges and you can configure port-forwards/etc to those addresses.

If the mail server only has a single ethernet port you can do something
similar with VLAN tags, if you have a switch that supports VLANs. The mail server needs to accept tagged frames and be set up so that VLAN 11 carries traffic for 192.168.1.x and VLAN 22 carries traffic for 192.168.2.x. You
then set up virtual interfaces like eth0.11 and eth0.22 on the server and proceed as the previous paragraph.

Alternatively what you could do is configure the second router as a WAN-side route of the first. ie the first router things it has two WAN routes, but
in reality one of them is the LAN-side of the second router. You'd get double-NAT that way, but maybe that's ok.

Really depends on how much control you have over the pieces (locked down ISP routers?). Seems more work than you really need unless the overlap period
is going to be a long time.

Theo
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.broadband

Theo <theom+news@chiark.greenend.org.uk> wrote:

Chris Green <cl@isbd.net> wrote:

We will be getting our new CityFibre FTTP connection on Wednesday.

Currently we have PlusNet FTTC with a static IPV4 address, the new
(IdNet) FTTP connection also has a static IPV4 address.

The system has a domain name hosted at Gandi internet and, obviously,
I will need to change the settings of the zone file there to point to
the new IP address. There will be a period while the new address propagates when both addresses will exist.

So, is there any way that I can set things up so that connections (in particular SMTP mail, I run Postfix as a mail server) to either
address will still reach my system?

If I configure just one of the two WAN facing routers to provide DHCP services can I then connect the LAN side of the two routers together
and get what I want? Then wait until the new IPV4 address for my
domain has propagated and, when it has, disable the FTTC router and transfer DHCP/DNS etc. wholly to the FTTP router.

Does this have a hope of working or have I overlooked something?

If you have one router you can in principle configure it with two upstream routes. ie you get two WAN IPv4 addresses, and you can decide where the traffic gets routed - ie you write a default route which says to send
traffic to the upstream route of ISP A rather than ISP B.

But I think you have two ISP routers which are both doing NAT, so you are
not exposed to the WAN side of things?

First of all, make sure the IP address ranges don't clash. They need to be entirely separate subnets - eg 192.168.1.x/24 and 192.168.2.x/24.

You can't connect the two networks together but what
you can do is connect both networks to the same server if it has two
ethernet ports. Then your mail server gets IP addresses in both 192.168.1.x and 192.168.2.x ranges and you can configure port-forwards/etc to those addresses.

If the mail server only has a single ethernet port you can do something similar with VLAN tags, if you have a switch that supports VLANs. The mail server needs to accept tagged frames and be set up so that VLAN 11 carries traffic for 192.168.1.x and VLAN 22 carries traffic for 192.168.2.x. You then set up virtual interfaces like eth0.11 and eth0.22 on the server and proceed as the previous paragraph.

Alternatively what you could do is configure the second router as a WAN-side route of the first. ie the first router things it has two WAN routes, but
in reality one of them is the LAN-side of the second router. You'd get double-NAT that way, but maybe that's ok.

Thanks for the various approaches.

Really depends on how much control you have over the pieces (locked down ISP routers?). Seems more work than you really need unless the overlap period
is going to be a long time.

All the routers are 'mine' :-) However, as you say, it's probably not
worth doing anything complicated as the upstream mail servers should
cope OK with mine not being available for a short while. In fact
that's upstream mail server (in the singular), all my mail comes via
Mystic Beasts who host the domains I use for mail. Thus I can just
wait for the IP change to propagate to them and then switch the system
from the FTTC router to the FTTP router.
--
Chris Green
-+
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.broadband

Chris Green wrote:
[snip]

All the routers are 'mine' :-) However, as you say, it's probably not
worth doing anything complicated as the upstream mail servers should
cope OK with mine not being available for a short while. In fact
that's upstream mail server (in the singular), all my mail comes via
Mystic Beasts who host the domains I use for mail. Thus I can just
wait for the IP change to propagate to them and then switch the system
from the FTTC router to the FTTP router.

Easy if you assume 3 things:

1. At least one router has dual WAN capability, i.e. VDSL (for FTTC) and Ethernet for FTTP.

2. The FTTP service is presented to you via an ONT (Optical Network Termination) using Ethernet. This is typically what is provided by
Openreach, for all their customers (which I think includes IDNet).

3. Both WAN services will run concurrently for a few days at least.

Set up this router to use both WAN connections, and open the necessary
ports to allow your email traffic in. Specify the Plusnet connection to
be the priority, and IDNet as the failover.

You hosting service should be able to specify (at least) two IP
addresses in the MX record. Ask them to specify your Plusnet address as
the highest priority, and the IDNet address as a lower priority. I
imagine they show a third address for their mailserver, so that if yours
is not available mail is received by theirs.

When the FTTP service goes live, get the hosting service to swap the
first two priorities in the MX record. And switch the priorities in
your router to the IDNet address has priority.
--
Graham J
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.broadband

Graham J <nobody@nowhere.co.uk> wrote:

Chris Green wrote:
[snip]

All the routers are 'mine' :-) However, as you say, it's probably not worth doing anything complicated as the upstream mail servers should
cope OK with mine not being available for a short while. In fact
that's upstream mail server (in the singular), all my mail comes via
Mystic Beasts who host the domains I use for mail. Thus I can just
wait for the IP change to propagate to them and then switch the system
from the FTTC router to the FTTP router.

Easy if you assume 3 things:

1. At least one router has dual WAN capability, i.e. VDSL (for FTTC) and Ethernet for FTTP.

Yes, I just looked, my Asus DSL-AC68U can use one of its ethernet
sockets for WAN failover or load balancing.

2. The FTTP service is presented to you via an ONT (Optical Network Termination) using Ethernet. This is typically what is provided by Openreach, for all their customers (which I think includes IDNet).

We're getting CityFibre but as far as I'm aware they provide an ONT
too.

3. Both WAN services will run concurrently for a few days at least.

Yes, the FTTC will continue until I port the landline number across to
a VOIP service so the FTTC will stop when I decide.

Set up this router to use both WAN connections, and open the necessary
ports to allow your email traffic in. Specify the Plusnet connection to
be the priority, and IDNet as the failover.

Simple enough, firewall and port forwarding are already set up as
required.

You hosting service should be able to specify (at least) two IP
addresses in the MX record. Ask them to specify your Plusnet address as
the highest priority, and the IDNet address as a lower priority. I
imagine they show a third address for their mailserver, so that if yours
is not available mail is received by theirs.

But the MX record points to a host name (the host name of my home
server) not an IP address. I'll be changing the A record to point to
my new iDNet IP address instead of the old Plusnet one. I can't point
the MX record to an IP address.

I have access to the DNS settings myself, I don't have to ask Gandi
internet to change it for me.


I suspect in fact that all I need to do is (as you suggest above) set
up my router to have two WAN inputs, one the (existing) VDSL/FTTC one
and the other the FTTP one. Connect the ONT to the ethernet WAN, and
that's it, incoming SMTP connections on either WAN input will get
delivered to my mail server.
--
Chris Green
-+
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.broadband

On 30/09/2025 14:47, Graham J wrote:

Chris Green wrote:
[snip]

All the routers are 'mine' :-)-a However, as you say, it's probably not
worth doing anything complicated as the upstream mail servers should
cope OK with mine not being available for a short while.-a In fact
that's upstream mail server (in the singular), all my mail comes via
Mystic Beasts who host the domains I use for mail.-a Thus I can just
wait for the IP change to propagate to them and then switch the system
from the FTTC router to the FTTP router.

Easy if you assume 3 things:

1. At least one router has dual WAN capability, i.e. VDSL (for FTTC) and Ethernet for FTTP.

2.-a The FTTP service is presented to you via an ONT (Optical Network Termination) using Ethernet.-a This is typically what is provided by Openreach, for all their customers (which I think includes IDNet).

3.-a Both WAN services will run concurrently for a few days at least.

Set up this router to use both WAN connections, and open the necessary
ports to allow your email traffic in.-a Specify the Plusnet connection to
be the priority, and IDNet as the failover.

You hosting service should be able to specify (at least) two IP
addresses in the MX record.-a Ask them to specify your Plusnet address as the highest priority, and the IDNet address as a lower priority.-a I
imagine they show a third address for their mailserver, so that if yours
is not available mail is received by theirs.

When the FTTP service goes live, get the hosting service to swap the
first two priorities in the MX record.-a And switch the priorities in
your router to the IDNet address has priority.

That's exactly what I did a couple of years ago when I had FTTP from
IDNet installed. Worked perfectly!

However you have explained it much more succinctly than I could have done!

David
--
David Rance writing from Caversham, Reading, UK


--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.broadband

On 30/09/2025 15:54, Chris Green wrote:

Graham J <nobody@nowhere.co.uk> wrote:

Chris Green wrote:
[snip]

All the routers are 'mine' :-) However, as you say, it's probably not
worth doing anything complicated as the upstream mail servers should
cope OK with mine not being available for a short while. In fact
that's upstream mail server (in the singular), all my mail comes via
Mystic Beasts who host the domains I use for mail. Thus I can just
wait for the IP change to propagate to them and then switch the system
from the FTTC router to the FTTP router.

Easy if you assume 3 things:

1. At least one router has dual WAN capability, i.e. VDSL (for FTTC) and
Ethernet for FTTP.

Yes, I just looked, my Asus DSL-AC68U can use one of its ethernet
sockets for WAN failover or load balancing.

2. The FTTP service is presented to you via an ONT (Optical Network
Termination) using Ethernet. This is typically what is provided by
Openreach, for all their customers (which I think includes IDNet).

We're getting CityFibre but as far as I'm aware they provide an ONT
too.

Yes, they do.>

3. Both WAN services will run concurrently for a few days at least.

Yes, the FTTC will continue until I port the landline number across to
a VOIP service so the FTTC will stop when I decide.

Set up this router to use both WAN connections, and open the necessary
ports to allow your email traffic in. Specify the Plusnet connection to
be the priority, and IDNet as the failover.

Simple enough, firewall and port forwarding are already set up as
required.

You hosting service should be able to specify (at least) two IP
addresses in the MX record. Ask them to specify your Plusnet address as
the highest priority, and the IDNet address as a lower priority. I
imagine they show a third address for their mailserver, so that if yours
is not available mail is received by theirs.

But the MX record points to a host name (the host name of my home
server) not an IP address. I'll be changing the A record to point to
my new iDNet IP address instead of the old Plusnet one. I can't point
the MX record to an IP address.

I have access to the DNS settings myself, I don't have to ask Gandi
internet to change it for me.

I suspect in fact that all I need to do is (as you suggest above) set
up my router to have two WAN inputs, one the (existing) VDSL/FTTC one
and the other the FTTP one. Connect the ONT to the ethernet WAN, and
that's it, incoming SMTP connections on either WAN input will get
delivered to my mail server.

--
David Rance writing from Caversham, Reading, UK


--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.broadband

On 29/09/2025 22:31, Chris Green wrote:

We will be getting our new CityFibre FTTP connection on Wednesday.

Currently we have PlusNet FTTC with a static IPV4 address, the new
(IdNet) FTTP connection also has a static IPV4 address.

The system has a domain name hosted at Gandi internet and, obviously,
I will need to change the settings of the zone file there to point to
the new IP address. There will be a period while the new address
propagates when both addresses will exist.

So, is there any way that I can set things up so that connections (in >particular SMTP mail, I run Postfix as a mail server) to either
address will still reach my system?

If I configure just one of the two WAN facing routers to provide DHCP >services can I then connect the LAN side of the two routers together
and get what I want? Then wait until the new IPV4 address for my
domain has propagated and, when it has, disable the FTTC router and
transfer DHCP/DNS etc. wholly to the FTTP router.

Does this have a hope of working or have I overlooked something?

When you point a domain at a new IP address,the A and MX records propagates
very quickly. When I did a brief experiment in self hosting, I think I used
this site to check:

https://dnschecker.org/

Unless you have something critical in your network, it probably isn't worth
the effort.
--
--
A PICKER OF UNCONSIDERED TRIFLES
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.broadband

Jason H <jason_hindle@yahoo.com> wrote:

On 29/09/2025 22:31, Chris Green wrote:

We will be getting our new CityFibre FTTP connection on Wednesday.

Currently we have PlusNet FTTC with a static IPV4 address, the new
(IdNet) FTTP connection also has a static IPV4 address.

The system has a domain name hosted at Gandi internet and, obviously,
I will need to change the settings of the zone file there to point to
the new IP address. There will be a period while the new address >propagates when both addresses will exist.

So, is there any way that I can set things up so that connections (in >particular SMTP mail, I run Postfix as a mail server) to either
address will still reach my system?

If I configure just one of the two WAN facing routers to provide DHCP >services can I then connect the LAN side of the two routers together
and get what I want? Then wait until the new IPV4 address for my
domain has propagated and, when it has, disable the FTTC router and >transfer DHCP/DNS etc. wholly to the FTTP router.

Does this have a hope of working or have I overlooked something?

When you point a domain at a new IP address,the A and MX records propagates very quickly. When I did a brief experiment in self hosting, I think I used this site to check:

https://dnschecker.org/

Unless you have something critical in your network, it probably isn't worth the effort.

Yes, I think you're probably right. The only 'critical' service is my
SMTP server to which my domain hosting (Mythic Beasts) sends my
E-Mails. I'm sure their servers are set up well such that they will
retry sending a few times (with increasing delays) before bouncing any
E-Mail.
--
Chris Green
-+
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.broadband

Chris Green wrote:

[snip]

Yes, I think you're probably right. The only 'critical' service is my
SMTP server to which my domain hosting (Mythic Beasts) sends my
E-Mails. I'm sure their servers are set up well such that they will
retry sending a few times (with increasing delays) before bouncing any E-Mail.

Look at the MX record to find out what is going on there.

If there is one record and it points to Mythic Beasts, you must ask them
what happens when their server can't find yours. For example, does it actually retry as you suggest?

If there is one record and it points to your FTTC IP address, then when
your IP is not available mail will bounce: the sending server will
report non-delivery to the originator of the email.

If there is more than one record, does the primary record point to your existing FTTC IP address? If so, what does the secondary record point
to? I imagine this might be Mythic Beasts. So if your server isn't accessible mail is delivered to the Mythic Beasts server, and the same question arises as above.
--
Graham J
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.broadband

Graham J <nobody@nowhere.co.uk> wrote:

Chris Green wrote:

[snip]

Yes, I think you're probably right. The only 'critical' service is my
SMTP server to which my domain hosting (Mythic Beasts) sends my
E-Mails. I'm sure their servers are set up well such that they will
retry sending a few times (with increasing delays) before bouncing any E-Mail.

Look at the MX record to find out what is going on there.

If there is one record and it points to Mythic Beasts, you must ask them what happens when their server can't find yours. For example, does it actually retry as you suggest?

If there is one record and it points to your FTTC IP address, then when
your IP is not available mail will bounce: the sending server will
report non-delivery to the originator of the email.

That's not what is supposed to happen with SMTP, and that's what I
meant by "set up well". If an SMTP server cannot send a message on to
a destination SMTP server it is supposed to back off and try again
after an interval. This should be done a (small) number of times
before reporting failure back to the originator.
--
Chris Green
-+
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.broadband

Chris Green wrote:

[snip]

If there is one record and it points to your FTTC IP address, then when
your IP is not available mail will bounce: the sending server will
report non-delivery to the originator of the email.

That's not what is supposed to happen with SMTP, and that's what I
meant by "set up well". If an SMTP server cannot send a message on to
a destination SMTP server it is supposed to back off and try again
after an interval. This should be done a (small) number of times
before reporting failure back to the originator.

There will be many sending SMTP servers and not all of them will be "set
up well" in the way you suggest. So to guarantee receipt of all emails
"your" SMTP server should be always available. With any luck this is
true for Mythic Beasts. So all emails go to the Mythic Beasts SMTP
server, and from there they are sent to your SMTP server when it becomes available. So the only SMTP server that has to be "set up well" is the
one at Mythic Beasts.
--
Graham J

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.broadband

On 2025-10-02, Chris Green <cl@isbd.net> wrote:

Graham J <nobody@nowhere.co.uk> wrote:

Chris Green wrote:

[snip]

Yes, I think you're probably right. The only 'critical' service is my
SMTP server to which my domain hosting (Mythic Beasts) sends my
E-Mails. I'm sure their servers are set up well such that they will
retry sending a few times (with increasing delays) before bouncing any
E-Mail.

Look at the MX record to find out what is going on there.

If there is one record and it points to Mythic Beasts, you must ask them
what happens when their server can't find yours. For example, does it
actually retry as you suggest?

If there is one record and it points to your FTTC IP address, then when
your IP is not available mail will bounce: the sending server will
report non-delivery to the originator of the email.

That's not what is supposed to happen with SMTP, and that's what I
meant by "set up well". If an SMTP server cannot send a message on to
a destination SMTP server it is supposed to back off and try again
after an interval. This should be done a (small) number of times
before reporting failure back to the originator.

I think mythic-beasts will retry delivery for 4 days and then bounce
back email undeliverable. But you can ask them - they generally respond
fairly quickly and are helpfull.

I am with MB and similarly have email forwarded by them. When my home
server died while I was away on holiday for a week, I lost 3 days of
email. When I got home and got the server back up, the last 4 days worth
of emails all came in. Now I have all my incoming email sent to my
server AND to an MB mailbox as a backup, and I periodically prune in
backup MB mailbox to keep the latest 4 weeks of emails.

--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.broadband

Jim Jackson <jj@franjam.org.uk> wrote:

On 2025-10-02, Chris Green <cl@isbd.net> wrote:

Graham J <nobody@nowhere.co.uk> wrote:

Chris Green wrote:

[snip]

Yes, I think you're probably right. The only 'critical' service is my >> > SMTP server to which my domain hosting (Mythic Beasts) sends my
E-Mails. I'm sure their servers are set up well such that they will
retry sending a few times (with increasing delays) before bouncing any >> > E-Mail.

Look at the MX record to find out what is going on there.

If there is one record and it points to Mythic Beasts, you must ask them >> what happens when their server can't find yours. For example, does it
actually retry as you suggest?

If there is one record and it points to your FTTC IP address, then when >> your IP is not available mail will bounce: the sending server will
report non-delivery to the originator of the email.

That's not what is supposed to happen with SMTP, and that's what I
meant by "set up well". If an SMTP server cannot send a message on to
a destination SMTP server it is supposed to back off and try again
after an interval. This should be done a (small) number of times
before reporting failure back to the originator.

I think mythic-beasts will retry delivery for 4 days and then bounce
back email undeliverable. But you can ask them - they generally respond fairly quickly and are helpfull.

I am with MB and similarly have email forwarded by them. When my home
server died while I was away on holiday for a week, I lost 3 days of
email. When I got home and got the server back up, the last 4 days worth
of emails all came in. Now I have all my incoming email sent to my
server AND to an MB mailbox as a backup, and I periodically prune in
backup MB mailbox to keep the latest 4 weeks of emails.

Yes, I do similar, I have an account on another server to which my
mail is also sent and deleted after some time (can't remember what
time exactly).
--
Chris Green
-+
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.broadband

Graham J <nobody@nowhere.co.uk> wrote:

Chris Green wrote:

[snip]

If there is one record and it points to your FTTC IP address, then when
your IP is not available mail will bounce: the sending server will
report non-delivery to the originator of the email.

That's not what is supposed to happen with SMTP, and that's what I
meant by "set up well". If an SMTP server cannot send a message on to
a destination SMTP server it is supposed to back off and try again
after an interval. This should be done a (small) number of times
before reporting failure back to the originator.

There will be many sending SMTP servers and not all of them will be "set
up well" in the way you suggest.

Ah, but **only** the Mythic Beasts ones will send to my server, as I
explained further up all the domains I actually use for E-Mail
addresses are hosted at Mythic Beasts. I know that their SMTP servers
are set up correctly, I asked them.
--
Chris Green
-+
--- Synchronet 3.21a-Linux NewsLink 1.2

From Newsgroup: uk.telecom.broadband

On 30/09/2025 15:54, Chris Green wrote:

Graham J <nobody@nowhere.co.uk> wrote:
You hosting service should be able to specify (at least) two IP
addresses in the MX record. Ask them to specify your Plusnet address as
the highest priority, and the IDNet address as a lower priority. I
imagine they show a third address for their mailserver, so that if yours
is not available mail is received by theirs.

But the MX record points to a host name (the host name of my home
server) not an IP address. I'll be changing the A record to point to
my new iDNet IP address instead of the old Plusnet one. I can't point
the MX record to an IP address.

Horse has bolted, but the fact MX records typically point to a hostname
should not have presented a problem. I don't see any need for messing
around with WAN connectivity and what you wanted to achieve could have
been done entirely in DNS (unless I'm missing something!)

I would have created two sets of MX records in DNS. Primary resolving to Plusnet IP, secondary to City Fibre IP.

This would have routed mail to the Plusnet IP whilst your server was
connected to that line.

When swapped over to the City Fibre line, any sending MTA with stale DNS records would have tried the Plusnet IP first, found no SMTP service at
that address and failed back to the City Fibre IP.

Once confident all mail was being received to your server on the City
Fibre line, then it would just have been a case of deleting the MX
records for the Plusnet IP.

e.g.

MX PRI5 smtp1.domain.tld
MX PRI10 smtp2.domain.tld
A smtp1.domain.tld <plusnet_IP>
A smtp2.domain.tld <city_fibre_IP>
--
Bob Pullen
--- Synchronet 3.21a-Linux NewsLink 1.2