Cogeco → My Cogeco IP address is not resolving today

Is there a Cogeco DNS issue happening today? DNS is not able to resolve my Cogeco host name, which is causing annoying delays in my mail delivery, etc. For example, here's a message from my mail server log:

Jul  8 11:55:40 mail postfix/submission/smtpd[3234]: warning: hostname d24-xx-xx-xx.home1.cgocable.net does not resolve to address 24.xx.xx.xx: Temporary failure in name resolution
 

Here is nslookup output:

 nslookup d24-xx-xx-xx.home1.cgocable.net
Server:         127.0.0.1
Address:        127.0.0.1#53
 
** server can't find d24-xx-xx-xx.home1.cgocable.net: NXDOMAIN
 

I tried using a few different DNS servers to make sure it's not just my stuff that's broken.

It means I have to wait until DNS lookup times out every time I want to send an email. Everything was working fine yesterday. Is this a known issue at Cogeco?

something funny (routing? remote issues?) was going on earlier, but i seem fine now. did your bind configuration change perhaps?

I'm pretty sure it's a Cogeco issue. My bind configuration hasn't changed. Plus, I've tried it on multiple DNS servers to see if it was on my end.

I'd recommend calling into commercial technical support and see what they say.

I'm not a commercial client. I still have access to commercial tech support?

Why are you running a mail server on a home connection?

That's what I was wondering.

and this show why you don't.

I'm not running a mail server on a home connection. My mail server is in a data centre. However, it does reverse DNS lookups on all connections. When I send mail from my home connection, my mail server tries to do a DNS lookup for my IP address. It can not find an A record that matches the reverse lookup and then delays my mail delivery.

What did I write that indicated that I'm running a mail server on a home connection? If I was doing that, my mail server wouldn't need to do a lookup to my IP address would it?

If your authenticated by other means (username/pass) why does it need to do a lookup? seems misconfigured.

Because mail servers shouldn't care about name resolution from client unless its anti spam measures, but if its a client connection with authentication the authentication is the anti spam measure and name resolution is pointless.

It's standard Postfix configuration. Postfix does NS lookup on all connecting IP addresses, which it then uses for all kinds of other checks. This happens before doing authentication on submissions.

It is also standard and default configuration for SSHd to do an IP lookup for various purposes. Logging into any remote server is now subject to this delay unless the server is explicitly configured to skip DNS checks.

My server configuration isn't really the issue though. The problem is that there is no record corresponding to my IP address in Cogeco's DNS server. This is new as of yesterday. I'm just trying to help out by reporting the issue.

Problem resolved by Cogeco tech support. Thanks!