|
|
|
albi90: Hi sultanoswing
If you put a dynamic DNS domain into to zone editor it should stay as the dynamic DNS not as the IP, the exception to this would be if you had that zone set to automatically update upon login or used the update API these will over-right the dynamic DNS with your current IP address.
I do like the idea of showing the IP address as well, i think i will put in the next up date a pop-over so when you mouse over a dynamic DNS you can see the real IP associated to the dynamic DNS.
Thanks
Jason K
charsleysa: URGENT:
As of 4:38pm September 6th 2014, all listed DNS servers are not responding to DNS requests. Pinging the servers is still successful.
I've had to fallback to Google DNS.
sultanoswing:albi90: Hi sultanoswing
If you put a dynamic DNS domain into to zone editor it should stay as the dynamic DNS not as the IP, the exception to this would be if you had that zone set to automatically update upon login or used the update API these will over-right the dynamic DNS with your current IP address.
I do like the idea of showing the IP address as well, i think i will put in the next up date a pop-over so when you mouse over a dynamic DNS you can see the real IP associated to the dynamic DNS.
Thanks
Jason K
Thanks - I'm not quite sure I've got my settings correct, or that I'm understanding exactly how the DDNS feature works.
I have disabled the "automatically update this zone" (i.e. it is showing in the blue drop down box).
I have entered my DDNS address into the IP/Dynamic DNS box as (an example, using this format) "http://myname.mydns.org"
Saving changes - now the DDNS remains in the IP/Dynamic DNS box. Great.
But, when I sign out and sign back in, I get "Your current IP address (123.45.67.89) was not found in your zones please pick a zone to assign it to:" in a lovely pink coloured box.
Do I need to do anything - or is this expected behaviour if the Dynamic DNS poller is working properly? If I click the blue "update" box at this point, then the IP address again takes over the domain name under "Zones".
Hopefully what I am trying to describe verbally makes sense - it's possibly a logic failure in my brain ;)
albi90: Hi charsleysa
I have found the issue, the patch we made on Friday broke the Zone IP validation and someone put an invalid IP in one of there zones causing the DNS configs to not validate correctly.
We have fixed the bug, removed the invalid IP and reloaded all the configs so everything should be operational now including custom domains.
like finding a needle in a haystack 1 IP in over 4000, I apologise for any inconvenience if there is anything that's not working still please let me know.
Thanks
Jason K
|
|
|