4 Oct
2010
4 Oct
'10
12:44 p.m.
Hi,
Right now I think I have bind and reverse dns setups
that work. Now all
I need is to have the root(a)exoco.net respond. I'll attend to that in
another email.
What do you want RDNS to resolve to? It is currently still resolving to
the bitfolk defaults:
-----
212.13.195.120
Server: 10.197.2.125
Address: 10.197.2.125#53
Non-authoritative answer:
120.195.13.212.in-addr.arpa name = mb.vps.bitfolk.com.
-----
Here's what I get for your forward zone:
-----
server a.authns.bitfolk.com
Default server:
a.authns.bitfolk.com
Address: 212.13.194.70#53
Default server: a.authns.bitfolk.com
Address: 2001:ba8:1f1:f019::53#53
Server: a.authns.bitfolk.com
Address: 212.13.194.70#53
** server can't find exoco.net: NXDOMAIN
server ns.exoco.net
Default server:
ns.exoco.net
Address: 212.13.195.120#53
Server: ns.exoco.net
Address: 212.13.195.120#53
exoco.net
origin = ns.exoco.net
mail addr = admin.exoco.net
serial = 2010100401
refresh = 7200
retry = 600
expire = 604800
minimum = 3600
exoco.net nameserver = ns.exoco.net.
exoco.net nameserver = b.authns.bitfolk.com.
exoco.net nameserver = c.authns.bitfolk.com.
exoco.net nameserver = a.authns.bitfolk.com.
exoco.net mail exchanger = 0 smtp.exoco.net.
exoco.net mail exchanger = 50 backup.mail.bitfolk.com.
Name: exoco.net
Address: 212.13.195.120
-----
It doesn't look like {a,b,c}.authns.bitfolk.com are authoritative for
your domain yet.
You should also reconsider listing backup.mail.bitfolk.com in the MX
records until you've got the relay on smtp.exoco.net working. This will
simplify the routing.
Be aware that some mailers might send mail to the A record rather than
the MX record.
Good luck with getting the rest configured.
Regards,
@ndy
--
andyjpb(a)ashurst.eu.org
http://www.ashurst.eu.org/
0x7EBA75FF