DNS resolution for private subdomain failing

[adrian878787]

Hub5. No parental controls

I have an Microsoft Azure-managed domain.  I've added a new subdomain, an A-record with local IP 192.168.0.100.  The subdomain is blocked by virgin media DNS.

Its been > 72 hours. I can see that the DNS name is available across the globe,  e.g. https://www.nslookup.io/domains/mysubdomainname/dns-propagation/a/.   And when I'm connected to EE I can nslookup it

From inside the hub5 zone I get dns timeout. I've tried overriding virgin media DNS and that doesn't work.  

What is strange that I can happily access another of my subdomains via the via home broadband network (a CNAME pointing at an Azure service)

I'm going to be creating a few of these a-records with internal IP.

Is there an article that explains how the DNS works and how I can easily unblock these. I tried emailing websafefeedback@virginmedia.co.uk without reply.

Kind regards,

Adrian

[Client62]

DNS Timeout has been attributed to the Hub 5 in Router mode before. As has DNS interception.

Try with the Connect app, is it possible to disable VM Smart Security i.e. to turn off the DNS redirection that is baked into the Hub 5 in Router mode ?   Does that help ?

Failing this the previous posts on this topic reported that Hub 5 in Modem mode does not perform DNS Redirection and that use of a Public DNS and DoT / DoH worked OK.

[Tudor]

It has been known for addresses to take up to 72 hours to be propagated on VM. 

[adrian878787]

Thanks for the feedback. Smart security is disabled. Was trying to avoid modem mode, the hub5 has been great for us, better than my spare router

[adrian878787]

Thanks, I said it was more than 72 hours, more like 96 now

[Gareth_L]

Hello adrian878787.

Thanks for your post and welcome to our community.

Sorry to hear about the issues you're having with your subdomain.

Would it be okay to ask if the fault has rectified itself now?

Gareth_L