I have setup MIAB to use some custom dns to point to a vps for a a few things and to my home lan (cname to a dyndns acct), but after several hours, I am still not getting the dns to work out right. Is it just a “give it some more time” issue or do I have some things setup wrong?
Here is what I have added to the custom DNS, the ipv4 is the vps, the ipv6 is also said vps, and the dyndns should be apparent. Long story short, I copied FIRST the data from my registrar, then updated the ns entries hoping that would be a simpler route to get things done, as well as backed up the settings, so if need be I can revert to them, but eliminating MIAB from the mix (undesired). After checking on the old zone file I downloaded, the TTL is indeed 3600 across the board, so technically it should have updated, right?
@.schotty.com A 72.14.183.210 [delete]
@.schotty.com AAAA 2600:3c00::f03c:91ff:fedf:048f [delete]
@.schotty.com TXT google-site-verification=n1_Pi9YCbVG_vaQlYBX3_-N5zdb3cDwEnWPxwUJeU8w [delete]
voice.schotty.com A 72.14.183.210 [delete]
voice.schotty.com AAAA 2600:3c00::f03c:91ff:fedf:048f [delete]
mc.schotty.com CNAME schotty.dyndns-home.com. [delete]
shadow.schotty.com CNAME schotty.dyndns-home.com. [delete]
www.schotty.com CNAME @. [delete]
www.shadow.schotty.com CNAME schotty.dyndns-home.com. [delete]
schotty.com A 72.14.183.210 [delete]
schotty.com AAAA 2600:3c00::f03c:91ff:fedf:048f [delete]
:EDIT: FWIW here is my firewall rules in case I am just blind and missing something there:
andrew@mx:~$ sudo ufw status
[sudo] password for andrew:
Status: active
To Action From
22 ALLOW Anywhere
53 ALLOW Anywhere
25/tcp ALLOW Anywhere
587 ALLOW Anywhere
993 ALLOW Anywhere
995 ALLOW Anywhere
4190/tcp ALLOW Anywhere
80 ALLOW Anywhere
443 ALLOW Anywhere
22 (v6) ALLOW Anywhere (v6)
53 (v6) ALLOW Anywhere (v6)
25/tcp (v6) ALLOW Anywhere (v6)
587 (v6) ALLOW Anywhere (v6)
993 (v6) ALLOW Anywhere (v6)
995 (v6) ALLOW Anywhere (v6)
4190/tcp (v6) ALLOW Anywhere (v6)
80 (v6) ALLOW Anywhere (v6)
443 (v6) ALLOW Anywhere (v6)
andrew@mx:~$