Status, I am receiving emails and my old DNS server is hacked to point to my MiaB. I have updated my registrar, name.com, and that SHOULD propagate and make MiaB as my nameserver with a couple secondaries. But I am having problems with both secondaries and want to add BuddyNS as a secondary. I have set up my account with them, pointing my domain (htt-consult.com) to MiaB (klovia.htt-consult.com). But the challenge is setting them up as a nameserver using the Custom DNS page.
BuddyNS does not seem to have a “simple” FQDN to put into the nameserver dialog as I do for ns1.mudkips.net & puck.nether.net. Per:
There is a lot to configure for NSD, which is outside the MiaB control.
Thus how do I setup the AXFR for BuddyNS?
I also set up puck.nether.net as a secondary, and it does not seem to be getting zone updates. No response from the email addr of the maintainer. He may have been away for the weekend…
Any guidance on how to troubleshoot transfers with puck is appreciated.
For AXFR, see the documentation on the Custom DNS page: “To enable zone transfers to additional servers without listing them as secondary nameservers, prefix a hostname, IP address, or subnet with xfr:, e.g. xfr:10.20.30.40 or xfr:10.0.0.0/8.”
I’m also seeing zone update issues with puck. At the moment I was sitting that one out.
Yeah, you create one string, starting with the nameservers you selected. It seems like you take a lot of them. Are you sure you can configure that many at name.com (your domain registrar? I’m used to being limited to three or four, five tops. But I’m not using name.com, so what do I know.
I would suggest using all ipv4 addresses with the axfr part of the string. Beforehand, you don´t know which server will be making the request.
The string then becomes:
<buddyns_nameserver_1> <buddyns_nameserver_2> axfr:108.61.224.67 axfr:116.203.6.3 axfr:107.191.99.111 axfr:193.109.120.66 axfr:23.27.101.128 axfr:192.184.93.99 axfr:103.25.56.55 axfr:216.73.156.203 axfr:37.143.61.179 axfr:195.20.17.193 axfr:45.77.29.133 axfr:116.203.0.64 axfr:167.88.161.228 axfr:199.195.249.208 axfr:104.244.78.122
For your information: mail-in-a-box will also add the nameserver you provide (e.g. puck.nether.net) to the axfr allowed list. Thus it might work anyway, because those axfr ip addresses buddyns mentions are probably translated to the list of dns servers they offer (I did not check). But by following the buddyns advice to allow all those ip addresses for axfr, you can be (more) sure it won´t fail.
I am pretty much populated around according to that checker.
I am having an internal problem, but it does not feel like DNS, but my internal firewall. I can’t get to my printer subnet. I think I made a change there yesterday… Sigh…
Anyway my outstanding DNS challenge is www.htt-consult.com as I asked at the beginning.
Solved my printer problem by going into the room they are in and seeing the powerstrip plug kicked out.
But back to www.mydomain.
Hey, it works. You have to set 2 custom records
mydomain A record
and
www.mydomain A record or CNAME record.
well, that went well.
I should probably leave things alone for a couple days and then see what is still not right.
I DON’T like what roundcube has done and don’t see a way to change it. The UI is so wasteful of space. I like how it was back in 1.0 over this 1.6 version.
I DO need to spin up a full local DNS resolver, but that is outside of MiaB. I was/am looking a KaliLinux on one of my Cubieboards, but can’t get the build working, so may end up buying a RPi4 for running unbound.
