I'm using the free xsnews ipv6 service. They have 4 AAAA DNS records on reader.ipv6.xsnews.nl:
$ dig reader.ipv6.xsnews.nl AAAA +short
2001:67c:174:101::5
2001:67c:174:101::2
2001:67c:174:101::3
2001:67c:174:101::4
Sometime one (or more) of those IP-addresses isn't working properly. I see that SABnzbd then tends to stick to an IP-address, rather than trying to see if the "other" ones will work.
Is there a setting that can help SABnzbd switch to an other IP quicker? Or is this behavior by design?
ipv6 failover
Forum rules
Help us help you:
Help us help you:
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: ipv6 failover
SABnzbd has no knowledge about the different addresses.
The way this provider implements load balancing is rather crude,
offloading the problem to clients.
What you can do is define 4 different servers each with its own numerical IP address.
Set one as primary and the rest as backup.
Also make sure each one is set as "optional".
If one is down, SABnzbd will ignore it after some time.
The way this provider implements load balancing is rather crude,
offloading the problem to clients.
What you can do is define 4 different servers each with its own numerical IP address.
Set one as primary and the rest as backup.
Also make sure each one is set as "optional".
If one is down, SABnzbd will ignore it after some time.