net. 3600IN A 198.7.30.6
;; Query time: 12 msec
;; SERVER: 192.16.0.5#53(192.16.0.5)
;; WHEN: Tue Aug 22 09:45:04 AEST 2017
;; MSG SIZE rcvd: 175
> From: Mark Andrews
> To: U Zee
> Cc: Grant Taylor ; "bind-users@lists.isc.org"
>
> Sent: Mon
e was just too much traffic. So its possible, my grep for lenovo
didn't show related packets But I will never know now
From: Mark Andrews
To: U Zee
Cc: Grant Taylor ; "bind-users@lists.isc.org"
Sent: Monday, August 14, 2017 3:00 AM
Subject: Re: DNS not resolvin
In message <1396839156.197734.1502489970...@mail.yahoo.com>, U Zee via
bind-users writ
es:
> Thanks for the suggestion Grant.
> Here's what I get for the recursive server's capture: ( I queried from
> the recursive server itself from another ssh session so it is the client
> as well)
>
> # tcpdum
ng specific that might help us diagnose further?
Thanks
From: Grant Taylor via bind-users
To: bind-users@lists.isc.org
Sent: Friday, August 11, 2017 7:06 PM
Subject: Re: DNS not resolving for a particular domain only
On 08/11/2017 06:49 AM, U Zee via bind-users wrote:
> Any ideas please??
On 08/11/2017 06:49 AM, U Zee via bind-users wrote:
Any ideas please???
I'm seeing different A records returned depending on where I query from.
As such I can only speculate that something related to DNS for a CDN is
not working as desired.
I'd suggest a packet capture of the client's DNS t
Hi All,
We are experiencing a weird issue for the past week or two.
We run bind9 on RHEL/CentOS and one of our international offices that has their
own auth and caching servers cannot resolve lenovo.com for some odd reason. If
that office clients use google DNS it works but using their own DNS c
6 matches
Mail list logo