Issue with AT&T IPs?

John W. Blue john.blue at rrcic.com
Tue Dec 5 17:41:35 UTC 2017


DNS, by design, is generally speaking agnostic when it comes to providing answers to DNS questions.  It would have to be a very deliberate edit to the "allow-query" option in the conf file to enable your construct of a "DNS blacklist".  In an enterprise environment this type of defensive action seems best played at the edge where the firewalls live based upon actionable data and not in a conf file.  But that is just me.

I read where a packet capture was performed but does no response include absence of reset packets?

What did a traceroute show?

Can you place a rule to allow unfiltered traffic in and out from one of your IP's for testing?

I am big fan of copying n pasting but it appears that you didn't clean it all up when composing this email the BIND group.  You indicate to the admins of quickfix8.com that quickfix8.com's servers are "refusing" the query.  So which is it?  No response or refusing?  Because getting refused answer is better than nothing at all.

In the end the issue may just resolve itself.

:D

Good hunting.

John

From: bind-users [mailto:bind-users-bounces at lists.isc.org] On Behalf Of Lightner, Jeffrey
Sent: Tuesday, December 05, 2017 10:24 AM
To: bind-users at isc.org
Subject: Issue with AT&T IPs?

We're having issues send email to a user @SIDDHAFLOWERS.COM

Investigation here shows that the issue we have is querying your name servers (both by name and by IP) are refusing to respond to our name servers.

Their name servers:
NS1.QUICKFIX8.COM
NS2.QUICKFIX8.COM

Our name servers:
DSWADNS1.WATER.COM
DSWADNS2.WATER.COM

We find other name servers such as those as Google are able to query their name servers.   Based on that I determined their name server IP (for both) is 74.124.202.236.   However, if I attempt to reach port 53 (DNS) on that IP from our name servers it simply fails to connect.   Our Network Security engineer did a capture and shows we send packets but never get a response.

Interestingly further testing shows this is an issue from any of our AT&T provided IPs:
12.44.84.194
12.44.84.213
12.44.84.214
12.44.84.216
But not from separate QTS Datacenter provided IPs:
209.10.103.136
209.10.103.148

I've reached out to the folks at QuickFix and am waiting to hear back but we've seen a similar issue on another domain using separate name servers.    Is it possible there is some sort of blacklist for DNS (not email) that people might be subscribing to that would cause them to block AT&T IPs?  We can do queries from our DNS to most domains but have identified these 2 as problems so suspect there might be others.

By the way, I can reach their mail server via command line connection to port 25 on its IP.   The issue here is purely in querying the DNS servers which of course means mail programs can't determine the MX records themselves.

Last night I did see some posts suggesting commenting out query-source but testing that didn't do anything.   We do have our query-source setup for random outbound ports and I verified last night that it still works based on the test site for that.

Most of what I find about blacklisting is about spam blacklisting of mail servers not blacklisting of DNS server queries and it is the latter we are experiencing.


CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20171205/658d58ad/attachment-0001.html>


More information about the bind-users mailing list