dns latency

2019-04-12 Thread Paul A
This is not really a Bind issue, but can anyone else confirm latency when querying Comcast from the root down? I ask because this morning some of our customers Could not email @comcast addresses, looked at the mail server and domain not found. I suspect my cache for Comcast timeout and when my DN

Re: dns latency

2019-04-12 Thread Mark Andrews
Before you pay attention to the round trip time you need this fix from BIND 9.9.6 from nearly 5 years ago now (2014-07-31). 3903. [bug] Improve the accuracy of DiG's reported round trip time. [RT 36611] Mark > On 13 Apr 2019, at 12:59 am, Paul A wrote: > > Th

RE: dns latency

2019-04-12 Thread Paul A
Mark, per my previous email, this high latency only happens when digging for Comcast. I did not compile bind on this machine, I'm using the latest Bind package that came with CentOS 7, bind-chroot-9.9.4-73.el7_6.x86_64. Looking at the changelog for the RPM it doesn't mention any issue with dig and

Re: dns latency

2019-04-12 Thread Bob Harold
On Fri, Apr 12, 2019 at 12:37 PM Paul A wrote: > Mark, per my previous email, this high latency only happens when digging > for > Comcast. I did not compile bind on this machine, I'm using the latest Bind > package that came with CentOS 7, bind-chroot-9.9.4-73.el7_6.x86_64. Looking > at the chan

RE: dns latency

2019-04-12 Thread Paul A
Bob, I get no real latency doing this, previously I was pinging the GTLD with the high latency from the query and I was not seeing any latency with ping, thus why I emailed the list. Currently doing a dig +trace on comcast.net sees no issues, but per my emails below, there was high latency from

Strange DNSsec failure [was incorrectly sent Thursday night]

2019-04-12 Thread frnkblk
I've had DNSsec validation on our non-public resolvers for a year or two -- virtually no issues ... until Thursday. First hint was that I couldn't get the for dns.comcast.net. Later in the day our monitoring system alerted me to email in our outbound queue that could not deliver to comcast.n

RE: Strange DNSsec failure [was incorrectly sent Thursday night]

2019-04-12 Thread frnkblk
Just saw this posted on twitter, too, from this morning: https://twitter.com/janger/status/1116738060199186432 Frank -Original Message- From: bind-users On Behalf Of frnk...@iname.com Sent: Friday, April 12, 2019 10:00 PM To: bind-users@lists.isc.org Subject: Strange DNSsec failure [was

RE: RE: Strange DNSsec failure [was incorrectly sent Thursday night]

2019-04-12 Thread frnkblk
And this forum post: https://forums.xfinity.com/t5/Email-Web-Browsing/Unable-to-resolve-comcast-n et-DNS/td-p/3213070 Frank -Original Message- From: bind-users On Behalf Of frnk...@iname.com Sent: Friday, April 12, 2019 10:08 PM To: bind-users@lists.isc.org Subject: RE: Strange DNSsec fa

RE: RE: Strange DNSsec failure [was incorrectly sent Thursday night]

2019-04-12 Thread frnkblk
It looks like running with +trace results in a 15+ second timeout, whether it's to the local resolver or Google, whether I specify IPv4 or not. mail1:~# dig mx1.comcast.net +trace @127.0.0.1 ; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> mx1.comcast.net +trace @127.0.0.1 ;; global options: +cmd .