Error message when loading target up in Framing 'The remote name could not be resolved: alaskybis.u-strasbg.fr'

[AL]

I am running NINA 1.10 HF1 and just today when at my observatory set to shoot a previously loaded target with no issues and framed with no issues is now generating an error message. I have tried other targets also and same error message.
I successfully found NGC 4435 and M101 in the Sky Atlas but when moving to framing to load up the image the error message appears: 'The remote name could not be resolved: alaskybis.u-strasbg.fr'

Anyone have a thought? I tried to reboot my computer and reload NINA. I even grabbed the coordinates from Cartes du Ciel and it transferred in just fine but again when moving to framing the same error message appeared. I have made no changes to my version of NINA, no changes to my equipment, nothing. Perhaps tomorrow morning it will work, who knows?

Thank you for your suggestions.

‌

[Stefan B]

sometimes the server there is not available. an alternative url is called when you upgrade to 1.10 HF3 Beta which has more uptime.

[AL]

Following up to the above issue, I tried to revert to my other observatory where the framing worked just fine and same error message pops up. So the issue is not related to the observatory settings.

[Dale Ghent]

It’s an issue with their server, not NINA or your local network. Unfortunately we have no control over its availability, but have provided a fallback method to another, backup server of theirs in 1.10 HF3, as Stefan mentioned. You can update to the 1.10 HF3 beta if you would like to have this now.

[AL]

Thanks Stefan. I thought the external server could be hence the tomorrow morning thought.
I am a bit cautious on upgrading because I ran into problems when moving to 1.10 HF2 with my Altair 26c camera. Apparently, Altair needs to provide a kit and I am not aware if they have done that. Any issues that yo have heard of with HF3 and the Altair? Once everything works I get a bit risk averse unfortunately.

[AL]

OK thanks Dale for the prompt reply. Tomorrow night is my plan for a clear night. Is this something, the external server, that could resolve in 24 hours or less? I know that is very specific and hard to know but based on prior experience if you have a guess. Thanks. I am in remote area of Vermont looking to use the dark skies here, but it is snowing today!! So I will ski in the morning and image at night if possible.

[Dale Ghent]

[daleg@iridium]~$ host -t ns u-strasbg.fr
u-strasbg.fr name server ns1.u-strasbg.fr.
u-strasbg.fr name server ns2.u-strasbg.fr.
u-strasbg.fr name server shiva.jussieu.fr.

[daleg@iridium]~$ dig +noall +answer @ns1.u-strasbg.fr a alaskybis.u-strasbg.fr
alaskybis.u-strasbg.fr. 1800    IN  A   130.79.128.179

‌

It would appear that Uni. Strasbourg keeps a 1800 second time-to-live on their DNS records for the HIPs servers. If your local or ISP’s name server is negative-caching a “not found” result to its prior lookup of alaskybis.u-strasbg.fr, it should be expunged from the cache in, at most, 1800 seconds, which is 30 minutes.

[AL]

Got it, thank you

[AL]

Hi, I just restarted my NUC and loaded up NINA to see if anything changed, which it has not. Do I need to clear a cache manually, would that help? And lastly, would this also prevent plate solving from occurring? At least I have the coordinates of the object loaded into the sequence, and though I can’t exactly frame it, my guess it should be centered well enough to image. Thank you.

[Dale Ghent]

The inability to resolve the name of the HIPS server comes down to your local or ISP name servers. Your router could also be caching the negative result, but I don’t really wish to engage in general PC technical support here.

The (in)ability to use reach these services does not impact plate solving.

[AL]

Thank you Dale that is helpful. I will work it from my end. I might search user experiences with 1.10 HF3 beta to learn about anything that might pose a risk to my current setup which was working brilliantly.

[Dale Ghent]

The HF3 changelog doesn’t appear to be updated on the website yet, so you can find the current list of changes here:

https://bitbucket.org/Isbeorn/nina/src/e425251b484e569845d0f9bc8412fee9a8e17923/RELEASE_NOTES.md?at=hotfix%2F1.10_hf3

[AL]

I reset my modem at this remote location and the framing in NINA worked this time but using NASA because HIPS was returning an error. Thank you. All good here now. Have a good weekend.