Nameserver glue records are incorrect. The ns1:box:tornmedia:com and ns2:box:tornmedia:com nameservers must be configured at your domain name registrar as having the IP address 126.96.36.199. They currently report addresses of [Not Set]/[Not Set]. It may take several hours for public DNS to update after a change.
as well as:
This domain must resolve to your box’s IP address (188.8.131.52) in public DNS but it currently resolves to [Not Set]. It may take several hours for public DNS to update after a change. This problem may result from other issues listed above.
other domains have the same issue with still Not Set.
The main domain on the page is still erroring saying it is pointing to the old godaddy records.
Just curious if Godaddy for some reason hasn’t given up the records yet, or are the two fighting over the dns? I reran sudo mailinabox last night, but don’t see improvement.
I’m not familiar with the GoDaddy interface, but it seems your glue records are not configured, so the MiaB DNS server will not be used. The current DNS server is GoDaddy and for your domain points the A record to an IP address owned by GoDaddy, so I’m guessing you haven’t configured that DNS server, either.
@tiggertlee as @openletter pointed out you seemingly have missed the steps in the setup guide pertaining to the name servers and the glue records.
You’ll need to go to GoDaddy and first set the glue records:
You will enter records for both ns1.box.tornmedia.com and ns2.box.tornmedia.com with the IP address of your MiaB installation.
then … you will need to actually point your name servers to the MiaB installation.
Enter ns1.box.tornmedia.com and ns2.box.tornmedia.com.
Do you have a website active now? I do not see one currently
Are you hosting email for other domains with your MiaB as well as tornmedia.com? If so you have to decide where the DNS for those other domains is going to be handled. If ANY of those domains are email only domains I would personally have MiaB handle the DNS for those domains, but if they have web sites and other apps on the domains, I would use External DNS … if you want some help figuring out the best approach, come visit the Slack channel or start a new discussion on the topic.
I did have my webserver and email on Godaddy but have removed them…
I followed the instructions and added ns1 and ns2 to the “host file” section of godaddy, but seems godaddy hasnt finished propagation yet? I cant add them to the namserver, godaddy says “unknown ns1…”
I am guessing the ns1 and ns2 hostnames/IPs I created on godaddy just havent propagated yet…
I will eventually host other domain emails, right now just trying to get tornmedia configured, would be very happy cutting godaddy completly out of the loop except as registrar. Really appreciate the feedback
I am going to be very blunt here. GoDaddy sucks! Period. Where other providers take mere seconds to update DNS they take minutes and sometimes hours. So, you have no choice but to wait … eventually it will be updated.
When looking at your domain’s glue records earlier I saw something that absolutely made me cringe. This should NEVER be in glue records.
I have broken this off to another reply as it is important NOW to make some decisions. In a perfect world, the best solution would be to have a domain exclusively for email services. It certainly is the easiest. So is tornmedia.com that domain? You will want the MiaB to handle the DNS for it’s domain and have all other domains whose email is being served by MiaB to have their DNS hosted externally.
The simple reason for this is that MiaB is a single point of failure. If it is down for whatever reason, and it is hosting DNS for multiple domains, those will go down as well (subject to caching of DNS). If email goes down for a few minutes or a few hours, it is not the catastropic loss that everything going down would be. I always recommend, regardless of the situation, when MiaB is hosting DNS for it’s domain or for other domains, that Secondary DNS be instituted as well.
In this case, yes. Not that it is going to matter. Let me explain.
When DNS is pointed to an external (not the registrar) nameserver, then NO, because you will tell NameSilo to use x nameservers and they will transfer the domain with the nameservers set
But in your case, you don’t have a web site live, and no mail either, so there is nothing that is going to matter at this moment. If you were using external DNS then there would be NO downtime.
Now, some tricks of the trade. … my last (yeah I used to use them too) move from GoDaddy took 30 minutes. Here is how. (From NameSilo support)
When Will My Transfer Finish?
Once our system submits the transfer to the central registry, there are a few factors that will determine exactly when the transfer will complete. If your current registrar allows, you may be able to approve the transfer request from your account on their site. Assuming you do and the transfer will complete within an hour…
GoDaddy IS a participating registrar. You can complete the process from their side HOWEVER they send you an email that your transfer will complete within 5 days with the option to ‘click here to cancel’. CLICK THERE! You will then be taken to where you can cancel or push the domain immediately. Yes, they intentionally mislead people.
Just for the record … for the GoDaddy fans who will come and say that I am making this up. I just checked your Glue records again NOW and this is what I see. Notice the time stamp. I am in CET (UTC +1).
Migration away from GoDaddy to NameSilo is complete. Seems to have updated the ns’ almost instantly. I am guessing the DNS’ will need a little time to pick everything up, the admin console is showing checks instead of X’s.
I reran the install, then rebooted. I am assuming that was good to do ?
Probably not necessary … but certainly did not hurt anything. I don’t know if your VPS has IPv6 support, or not. If you do you may want to add the IPv6 address to the Glue records.
So the only other thing I would strongly recommend is setting up Secondary DNS. Sadly, I am in the middle of something right now, so can’t really write out a simple plan for you to follow. But I’ll do it tomorrow. After all, you’re gonna be busy firing GoDaddy!
While I use GoDaddy, I’m not necessarily a great fan. While adding DNSSEC records is fairly painless, removing said records can be a pain.
I had to get support to do it for me. I might move my domains to my current VPS provider (1&1 Ionos)
I would however point out that while GoDaddy’s system allows you to update your Glue records. It’s important to understand that the Glue records themselves are actually held on the TLD’s nameservers. For .com this is verisign.
I’d also point out that a 48 hour TTL for these records is not unusual. In fact it’s the norm. This is down to the way DNS is meant to work.
The idea is that certain records are less likely to change. So rather than make a lookup every time, the DNS resolvers at your ISP or other public DNS service cache the results. As the location of a domains authoritative nameservers are less likely to change than, say the address of it’s website, then these records have a longer lifespan. This reduces the load on the higher level nameservers.
I don’t disagree with this, however it IS unusual for a domain registrar to list their name servers as the glue for a domain … that is not acceptable. And the icing on the cake was that they set the records for 48 hours. A record that they should NOT have touched in the first place!
Not to get too off-topic, but one really should NOT have their domain registrations hosted by a service provider that they are using. And, btw 1&1 Ionos is only slightly better than GoDaddy. Maybe 1% better.