Hello Johnny,
That appears to be it, our network DNS resolvers were caching an old record
from the looks of it.
I've cleared the cache, and everything is now working perfectly.
Thank you (all) for the help, I wasn't even aware that the 204.15.73.243
address was no longer valid.
On 21 October 2015 at 05:35, Johnny Hughes <johnny@xxxxxxxxxx> wrote:
> On 10/20/2015 01:28 PM, Jonathan Billings wrote:
> > On Tue, Oct 20, 2015 at 12:29:06PM -0500, Johnny Hughes wrote:
> >> Those 3 addresses are good, the 204.15.73.243 is incorrect.
> >
> > 204.15.73.243 reverse resolves to centos.at.multacom.com.
> > multacom is a CentOS Sponsor according to:
> > https://www.centos.org/sponsors/
> >
> > An outdated config somewhere?
> >
> I don't think so on our end, but that was at one time a good address.
>
> Maybe the site in question has a static address added in a hosts file, etc.
>
>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> https://lists.centos.org/mailman/listinfo/centos
>
>
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
https://lists.centos.org/mailman/listinfo/centos
