Hi, I've got a mail problem on my server, but don't see what the real problem is.
dnsstuff.com reports the following:
No nameservers respond to queries via TCP. If no nameservers respond to TCP connections, this means that standard zone transfers (usually for slave DNS server replication) and most DNSSEC functions will not work. This can cause difficult to diagnose issues with those protocols. The nameservers that failed TCP queries are:
ns2.penghosting.nl. | 88.208.193.146 ns1.penghosting.nl. | 88.208.193.145
and
No nameservers provided an SOA record for the zone. You should configure your nameservers to have a master slave relationship. The update of the zone information to the slave nameservers should be handled through the SOA record.
and
No MX records exist within the zone. This is legal, but if you want to receive E-mail on this domain, you should have MX record(s). The program can't continue in a case like this, so we are assuming you don't receive mail on this domain.
Now, mail does 'work', but it can take hours for a mail to arrive.
In DNS Records of the domain on the server, I see:
mail A - IPv4 Address 88.208.193.145 georgefoto.nl MX - Mail Server 1 mail.georgefoto.nl.
So I don't know why dnsstuff can't 'see' the MX records.
Anybody an idea what I should do next to make this work as it should?
Thanks!
hmm that's a bit weird,
http://www.viewdns.info/dnsreport/?domain=georgefoto.nl
doesn't have the same problems with mx or so, only this one:
Oops! We couldn't connect to the following nameservers using TCP on port 53:
ns1.penghosting.nl. ns2.penghosting.nl.
And by the way, I ran some mail tests and it seems to work fine, although last night there was a problem. Only thing I did was restart bind service.
Sorry people, I guess you shouldn't read this anymore, there seems to be no problem anymore. It's ok to remove this topic moderator... Again: I'm sorry for abusing your time.
Howdy,
It's no problem at all! You're always welcome to post questions here, no need to feel bad now that it's working.
One note -- there' a number of reasons to not have BIND listening on port 25 TCP, so you might see that error from some DNS testing services.
That's just needed for zone transfers between DNS servers... so only your slave DNS server needs to be able to access that. It looks like you don't have a slave DNS server, so in that case you can completely ignore that message.
Have a good one!
-Eric