Virgin Media Community

[Tambhoy]

Can I get port 53 unblocked for a Web server?

[MOD EDIT: Subject title changed for clarity]

[jem101]

---

@Tambhoy wrote:

Can I get port 53 unblocked for a Web server?

---

53 isn't blocked by VM, only the ports used for SMB and NetBIOS are. So if you can't access that port externally then something else is going on.

[Client62]

Port 53 is for DNS, requests to say 8.8.8.8 Google DNS are not blocked.

[Tambhoy]

I get this message when i try to port forward

The configured port range cannot contain one of the following reserved ports: 53,135,137,139,161,162

[Client62]

Are you intending to offer a public DNS service ? 

[Tambhoy]

No, I am trying to set up a web server to host a small personal website but cannot get the dns to resolve

[jem101]

---

@Tambhoy wrote:

I get this message when i try to port forward

The configured port range cannot contain one of the following reserved ports: 53,135,137,139,161,162

---

Ah right, I see, that's not actually VM blocking the port as such, but the firmware on the hub not allowing you to port forward that number. Yes I know the distinction is a bit vague but realistically there is absolutely nothing that VM can or will do. The firmware for the hub will need to be rewritten to allow this and pushed out to all the hubs, and the chances of that happening are somewhat less than Jacob Rees-Mogg joining the UK Communist Party!

Your only option is to get your own router with fewer restrictions, put the VM hub into modem mode and doing all the port forwarding on your own router.

[gitty]

A note: Something else is wrong. You don't need to forward port 53 for your setup (as I understand it from the short description).

[legacy1]

if you webserver is on 80 or 443 port 53 has nothing to do with that unless you run it on that port.

maybe your problem is thier is no NAT loopback support on the hub?

[Tambhoy]

The domain name registrar can't resolve the dns on port 53. i have now sorted some of it with cloudflare