|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: Postfix DNS Problem
From: Peter Voth (peterhvoth
gmail.com)
Date: Tue May 16 2006 - 07:42:15 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
I think propagation is okay - I can get the correct information with dig.
It's just that Postfix hasn't figured it out.
On 5/16/06, Pedro Vieira <pedro.vieira
filbox.com> wrote:
>
>
>
> Peter Voth wrote:
> > The DNS on my Postfix installation seems to be screwed up. The server
> > in question is handling mail for a subdomain of my company's main
> > domain. There's no problem with receiving mail, and I am able to send
> > mail to most domains (other than those that do reverse DNS - I haven't
> > finished setting that up yet), except for the parent domain.
> > According to the log, Postfix is trying to connect to the old mail
> > server's IP address when sending to that domain rather than the
> > currently active one. The old mail server is still part of the MX
> > record, it just now has a lower priority than the active one, but the
> > fact that there's no indication in the log that Postfix is even trying
> > the higher priority server makes me think it's that Postfix is using
> > the outdated DNS information.
> >
> > I get the right answer when I dig the MX record, so it doesn't seem
> > that DNS is messed up on the machine as a whole, and the fact that I
> > can receive mail argues against a problem with the zone file. Postfix
> > isn't running chrooted, but I've copied /etc/resolv.conf to the spool
> > directory, so that should have fixed the issue even if that was the
> case.
> >
> > The problem has survived several reboots and postfix reloads. At this
> > point, I'm stumped. Any hints or ideas?
>
>
> How long ago have you changed your DNS records? Maybe you have to wait a
> little more for the record to end propagation.
> First find what dns servers are being used by the one who are resolving
> incorretly your ip, then try to dig those servers and see what happens...
>
> I know that's not too much, but it's all I can think of right now..
>
> Pedro
>
>
>
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]