On Feb 17, 2018, at 06:04, Reindl Harald wrote:
> "Is google just b0rked?" is mostly wrong to start with
As I said, that seems unlikely. But the different behavior from multiple large
DNS services was odd.
> Delegation
>
> Failed to find name servers of david-dodge.com/IN.
I may have been muc
On 2018-02-17 (02:48 MST), Niall O'Reilly wrote:
>
> In my not-very-extensive experience, Google's 8.8.8.8 service seems to have
> limited tolerance of badly-behaving authority servers; in such a case, it
> seems to give up early and report SERVFAIL.
>
> As it happens, there seem to be problem
Hi there,
On Sat, 17 Feb 2018, LuKreme wrote:
... Is google just b0rked? ...
You might need to look closer to home.
You claim three nameservers, but it appears that they're all on the
same network segment - a *really* bad idea - and one of them doesn't
respond to DNS requests, using IPs loca
On 16 Feb 2018, at 23:23, LuKreme wrote:
> Is google just b0rked? (Seems unlikely) or is there something in the
> configuration for the dns that they don't like?
In my not-very-extensive experience, Google's 8.8.8.8 service seems to have
limited tolerance of badly-behaving authority servers; in
I have a domain that I host for a friend that he is not able to access
suddenly. We thought it was SSL related, but after gettting more information
his work computers are not getting an IP address (he can access it from home).
I checked quadnines, openDNS, and google dns. The first two responde
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
On 2013-11-11 12:11, S. Jeff Cold wrote:
...
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 22495
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;jeffdiss.org. IN A
...
BIND's configuration file is :
$TTL 3600
$ORIGIN jeffdiss.org.
; St
If you have "check-mx fail;" in named.conf then the zone will not load and
you will get SERVFAIL. The default is "check-mx warn;".
12-Nov-2013 07:40:07.546 zone jeffdiss.org/IN: jeffdiss.org/MX
'mail.jeffdiss.org' has no address records (A or )
12-Nov-2013 07:40:07.546 zone jeffdiss.org/IN:
On Nov 11, 2013, at 12:11 PM, S. Jeff Cold wrote:
> I have two DNS servers both running Debian Linux 7.2.0, BIND 9.8.4 in a
> private LAN. I set up an unregistered domain to see how things would run.
> When I run dig on the domain just to see if it will resolve, I get this error:
[ SERVFAIL
I have two DNS servers both running Debian Linux 7.2.0, BIND 9.8.4 in a private
LAN. I set up an unregistered domain to see how things would run. When I run
dig on the domain just to see if it will resolve, I get this error:
; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> jeffdiss.org
;; global options
$ whois jatec.us
--snip--
Domain Status: inactive
Name Server: ICEMAN.JATEC.US
--snip--
Domain Registration Date:Fri Oct 03 21:05:39 GMT
2008
Domain Expiration Date: Fri Oct 02 23:59:59 GMT
2
> [mailto:bind-users-boun...@lists.isc.org] On Behalf Of
> Matthew Pounsett
> Sent: Thursday, January 29, 2009 1:49 PM
> To: S. Jeff Cold
> Cc: bind-users@lists.isc.org
> Subject: Re: my DNS not resolving
>
>
> On 29-Jan-2009, at 13:49, S. Jeff Cold wrote:
>
> > BIN
On 29-Jan-2009, at 13:49, S. Jeff Cold wrote:
BIND List,
I have a server running OpenSuse 11.1 with BIND 9.5.0P2-18.1.
This server has a dedicated IP address from my ISP. I want this
server to resolve my registered domain jatec.us. The server has
internet connectivity. If I dig j
BIND List,
I have a server running OpenSuse 11.1 with BIND 9.5.0P2-18.1. This server
has a dedicated IP address from my ISP. I want this server to resolve my
registered domain jatec.us. The server has internet connectivity. If I dig
jatec.us, I get:
xx
19 matches
Mail list logo