On Mon, Jul 13, 2009 at 4:39 PM, Zack Githinji <zachgithinji@gmail.com> wrote:

[snip]

issue 2:
Organization had a public ip A it was blacklisted, changed to B which has been in use all this time. when the server is set to B it cannot ping outside (out of local LAN). and it cannot be accessed.

Is IP B same subnet as IP A, and routed the same way?
How do you activate IP B? Please type the command you use here.
Also type the output pf 'netstat -rn' when IP A is active and also when IP B is active.

if u send mail u get the error "Host or domain name not found. Name service error for name=smtp.isp.com type=MX: Host not found, try again"

This means that routing is broken when IP B is active and so DNS resolution is not working since (it would appear) your DNS server is actually external to your network. If you were running a local cache, it would be a different error message.

if i set it to use A it delivers mail but cant Receive, it can ping outside and can also be accessed.

I find that quite odd - that it delivers mail, but cannot receive. So if you login to your gmail account and send an e-mail to youraddress@company.domain, you end up with or without an error? In the absence of an _immediate_ error, you need to call AK and ask them to check the listing in the queue for ukns1.accesskenya.com to see if the mail -s there. If it is, then you can do something to dequeue the mail. From your server, try this:

telnet ukns1.accesskenya.com 25
ETRN zimele.net
quit

If the AK server supports ETRN, that command should announce to it the resurgence of your server and e-mails should begin to flow.

PS: I think deploying IP B is actually a waste of time. Fix whatever is wrong with IP A and continue with business as usual:-)