@DaHai wrote:
octoprint: - host: Hevo.localhostor
octoprint: - host: Hevo.asgardNo longer work. They used to. Now I get:
Endpoint: job Failed to update OctoPrint status. Error: HTTPConnectionPool(host=‘hevo.localhost’, port=80): Max retries exceeded with url: /api/job (Caused by NewConnectionError(’<urllib3.connection.HTTPConnection object at 0x72f37f10>: Failed to establish a new connection: [Errno -2] Name does not resolve’))
Connection lost. Reconnecting…Or
Endpoint: job Failed to update OctoPrint status. Error: HTTPConnectionPool(host=‘hevo.asgard’, port=80): Max retries exceeded with url: /api/job (Caused by NewConnectionError(’<urllib3.connection.HTTPConnection object at 0x72f37e10>: Failed to establish a new connection: [Errno -2] Name does not resolve’))
Connection lost. Reconnecting…My pfSense router is set up to assign DNS server 172.27.3.3 to hassio.asgard.
My local domain is .asgard
My dnsmasq on my Pi is set to foward all .localhost and .asgard domain requests to 172.27.3.1 (my pfSense router with DNS Resolver running.
My Pi-Hole (on 172.27.3.3) Logs don’t even show Hassio querying for a DNS for hevo.asgard or hevo.localhostI saw this thread: Name resolution problem since 0.97.2
But executing it as a shell command fails with 'No such file or directory ‘hassio’
And executing it from SSH fails with ‘dns’ invalid option.
I’m running Supervisor 200
This used to work, but lately, it has stopped and the only way I can get it to work is to hard-code the actual IP address for hevo.asgard - which it just not acceptable as it negates the whole purpose of a local DNS resolver.
Looks like the Supervisor auto updates?
How do I turn that OFF!?
Any help is greatly appreciated.
Posts: 5
Participants: 1