Virtualmin on DreamHost CloudCompute

bislinks's picture
Submitted by bislinks on Sat, 01/21/2017 - 15:37 Pro Licensee

This is regarding virtualmin running centos 7 on a cloudcompute at DreamHost.

The domain assigned is a1z.us. I am able to access virtualmin using its public IP 208.113.167.22. But not via a1z.us:10000

both nameservers, a.a1z.us and b.a1z.us for a1z.us point to the same above IP

For some reason, a1z.us is not served by them when I ping or check on mxtoolbox (Unable to resolve "a1z.us" to an IP address.)

Update: a1z.us is registered at DreamHost.

ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 208.113.167.22  netmask 255.255.252.0  broadcast 208.113.167.255
        inet6 fe80::f816:3eff:fee8:f396  prefixlen 64  scopeid 0x20<link>
        inet6 2607:f298:5:101d:f816:3eff:fee8:f396  prefixlen 64  scopeid 0x0<global>
        ether fa:16:3e:e8:f3:96  txqueuelen 1000  (Ethernet)
        RX packets 3473124384  bytes 3924616201671 (3.5 TiB)
        RX errors 0  dropped 1300431  overruns 0  frame 0
        TX packets 1215281  bytes 750597034 (715.8 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 621927  bytes 172972796 (164.9 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 621927  bytes 172972796 (164.9 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
Status: 
Closed (fixed)

Comments

Submitted by JamieCameron on Sat, 01/21/2017 - 15:58

Is the a1z.us hosted by your VIrtualmin system? If so, make sure your firewall allows requests to port 53 (for DNS serving) on both TCP and UDP protocols.

bislinks's picture
Submitted by bislinks on Sat, 01/21/2017 - 16:03 Pro Licensee

On their security rules, 'ingress' TCP 53 is 0.0.0.0; which i assume the port is open.

'Egress' TCP 53 is 0.0.0.0 which I just opened.

I do not see UDP anywhere in the rules they have provided.

bislinks's picture
Submitted by bislinks on Sat, 01/21/2017 - 16:05 Pro Licensee

Update: i found udp and opened it just now.

bislinks's picture
Submitted by bislinks on Sat, 01/21/2017 - 16:55 Pro Licensee

The DNS port was open. TCP 53 Ingress was open.

My bad, UDP did not occur to me at all.

I had more than ten conversations ( tickets and chats ) with tech support, no one even mentioned port 53!

Thanks Joe. You did it.

You guys rock!

Submitted by JamieCameron on Sat, 01/21/2017 - 17:40

Status: Active » Fixed