Cannot access Gigahub behind internal DNS

[SneakOdyssey]

Does anyone out there use an internal DNS for accessing things locally?

I notice I cannot properly access the gigahub's UI using my internal DNS address I gave it - but can using the IP. The DNS I am using is on my Synology NAS - and I was able to access the Rogers router I had before switching to Bell recently.

When I attempt to access the gigahub's interface behind my DNS name I get this initialization error:

When I access it via the IP address - it initializes fine and I can login to it.

Any thoughts on why this might be?

[Vanadiel · Accepted solution]

Not sure how you configured it, but you cannot point the home hub DNS to a LAN IP DNS server.

[SneakOdyssey]

Hi @Vanadiel , 

I did see that in other posts. I have my own router configured and the internal DNS on that, and I'm not using the gigahub as my main router. the gigahub still is using the default Bell DNS. 

However I have my internal DNS from my Synology giving a domain name to 192.168.2.1 to access the gigahub - and it loads - but not entirely.

So if I navigate to 192.168.2.1 - I can access the gigahub fine. But If I navigate to gigahubinternaldomain - my DNS points to 192.168.2.1 - but fails to fully initialize the UI for me. it loads up the screenshot above.

[Vanadiel]

Which DHCP server are you using, the one from the hub or your own?

[SneakOdyssey]

I'm accessing it from my own DHCP from my own router.