Whenever I try to do a checkup of my MX records I am getting the message that my domain does not resolve to an IP or that the DNS server is non authoritative. This causes e-mails not to arrive.
Topology: domain.be =>points to => dns1.mydnsserver.be and dns2.mydnsserver.be On the DNS server I have following zone:
zone "domain.be" {
type master;
file "/var/named/domain.be.hosts";
allow-transfer {
127.0.0.1;
localnets;
};
};
In that zone I have following records:
$ttl 38400
@ IN SOA dns1.mydnsserver.be. root.dns1.mydnsserver.be. (
1467744776
10800
3600
604800
38400 )
@ IN NS dns1.mydnsserver.be.
@ IN NS dns2.mydnsserver.be.
domain.be. IN A xx.xx.xx.xx
www.domain.be. IN A xx.xx.xx.xx
ftp.domain.be. IN A x.xx.xx.xx
m.domain.be. IN A x.xx.xx.xx
localhost.domain.be. IN A 127.0.0.1
mail.domain.be. IN A x.xx.xx.xx
domain.be. IN MX 5 mail.domain.be.
domain.be. IN TXT "v=spf1 a mx a:domain.be ipx.xx.xx.xx ?all"
What can possibly be wrong?
Where exactly are you getting this error?
I don't see anything wrong really with your zone. The MX record for "remisan.be" (I suppose that is your domain in question?) points to the correct hostname, and "mail.remisan.be" points to the IP 5.9.8.18 (is that IP correct?).
Also www.intodns.com can't find problems with your zone.
Note: According to the .be nameservers, the responsible nameservers for "remisan.be" are not servers of yours, but those:
Maybe you set the glue records at your registrar incorrectly?
hemm. embarrassing. I forgot to rename 2 of the domains. The domain you looked up is on my server, but I have urgently pointed the DNS to a professional DNS server (cloudflare) in order not to miss any more mails ...
However, I seem to be having the same problem with tons of other domains on the same server. The dns server is on the same server as the webserver. The dedicated server has 1 IP and 2 virtual IP's: 1 for webserver, 1 for second DNS and 1 ip for ssl cert.
The cloudflare service is working fine, but in due time, I want to completely get rid of it, so I need to get the DNS working properly.
Thanks already for your help :)
Since you're hosting public services (at least I assume you do), domain names and IP addresses are no secrets. :) In fact, I need to know them to do any meaningful tests here.
Can you reiterate what the problem exactly is? Where did you do this "MX checkup"? What domains are not working? The one you posted, since you modified the glue records, are unusable for a test really.
Thanks for your reply. The following are some of the domains currently having issues and which are still on the same DNS server: gsdns.be fraksken.be tguldenvlies.be they should be pointing to ns1.gswp.be and ns2.gswp.be (which might be working now since I put gswp.be back to cloudflare)
I checked with various online tools including http://www.webmaster-toolkit.com/mx-record-lookup.shtml http://www.dnsqueries.com/en/mx-lookup.php
I can't see any problems with the MX records for any of these domains... Neither with dig, nor with the "webmaster-toolkit" website. MX records exists for all of them and point to "mail.domain". That in turn points to the IP 5.9.8.29.
What issues exactly are you having, let's say with fraksken.be?
That will probably be since gswp.be is now pointing to a valid DNS server, distributing correct DNS values for the other domains. I will change the DNS server for fraksken.be to demonstrate what happens. This can take an hour or 2 though...
Great, so since I am using a fully qualified DNS server for my main NS, all the domains are resolving. For the time being I can work with that.
Thanks for the help. I will pick this back up when I managed to bind the new IP to my server (that one is still giving issues)