NoIP.com dynamic round robin not updating correctly

A Former User

Hello,

I am using a round robin with NoIP.com dynamic DNS service. I want a dns name to round robin to both of my WAN connections.

so I have 2 WAN connections and they should be updating the following:

lixwanmulti.hopto.org@SERVER-1
lixwanmulti.hopto.org@SERVER-2

however they are only updating SERVER-1. SERVER-2 is not touched by pfSense. I have also tried replacing the @ with %40 and it does the same thing, only updates SERVER-1

I currently have a ticket open with NoIP.com but they said I should also talk with pfSense to find if they might be able to help me also.

If anyone can shed some light with what the problem may be I would appreciate it.
Thanks,
Keith

Nachtfalke

Hi,

sorry that I hijack this thread and cannot help you on your topic but I have a question:

I have 2 WAN interfaces on pfsense. At the moment I reach every interface with a different dynamic DNS like fro, the internet:

server1.noip.com which is WAN1 on pfsense
server2.noip.com which is WAN2 on pfsense
server3.noip.com which is WAN3 on pfsense

My question:
Is it possible to only have one dynami DNS like:

myservers.noip.com which does round robin for WAN1, WAN2 and WAN3?

Is this something I need to configure on NO-IP.com website?

Thank you for your help!

A Former User

It is should be possible with what I mentioned in my post.

So far the support with pfsense is pretty horrible unless you are willing and able to pay for it. I guess the makers of pfsense are like any other company out there. They offer a "free" service and then shaft anyone who uses it and expect them to support themselves.

So the word from no-ip.com tech support is the pfsense is not sending over the correct format so it can't update anything other than the 1st server you have listed. Hopefully some of the developers read this so they can fix the bug soon. It would be very handy to use this feature.

doktornotor

@holygoatnickels:

So far the support with pfsense is pretty horrible unless you are willing and able to pay for it. I guess the makers of pfsense are like any other company out there. They offer a "free" service and then shaft anyone who uses it and expect them to support themselves.

Hmmmm wow… wondering which are those better alternative solutions that provide bugfixes within hours from reporting. Just the recent examples I filed myself:

https://redmine.pfsense.org/issues/3090
https://redmine.pfsense.org/issues/3074

So the word from no-ip.com tech support is the pfsense is not sending over the correct format so it can't update anything other than the 1st server you have listed. Hopefully some of the developers read this so they can fix the bug soon.

Maybe the awesome no-ip tech support could provide patches so that people can use their commercial services better. Somehow, I cannot find any such ticket…

phil.davis

I don't see any code in pfSense yet to allow the dynamic DNS update to send multiple IP addresses to any of the dynamic DNS providers. In pfSense 2.1-RC0 you can have dynamic DNS attached to a gateway group, but in that case it keeps the IP address updated to the public IP of the highest tier WAN in the gateway group that is up.
On the No-IP Update Protocol page http://www.noip.com/integrate/ it doesn't say how to keep a round-robin group up-to-date. Can it be provided a list of address in "myip=". Otherwise there would have to be a way of removing an individual address from the current list, then adding the new one.
It would be a good start to know exactly what the update protocol is for multi-IP hosts/round robin.

I also noticed that the current updating address is https://dynupdate.no-ip.com/nic/update but the pfSense code is still using:

$server = "http://dynupdate.no-ip.com/ducupdate.php";

Which I guess still works fine, for backward compatibility with devices that had this built into them in past years. Might need to be updated to the new one to get new functionality.

A checkbox could be added to flag that the dynamic DNS should try to set a list of all the IP addresses of the interfaces in that gateway group that are up. The checkbox would be enabled when you select a provider that is supported for this feature. Then the underlying code could implement it.

Adding functionality has to be done by one of: yourself; a kind volunteer; someone paid a bounty to do it; commercial support guys (they have to eat) - if you have some coding skills then you can make the changes yourself and submit them!

scammarano

Hi, did you solve this problem?

can help me?