ently map to the IP
> addresses that do not belong to this domain controller. The invalid IP
> addresses are 10.1.1.1; 10.2.2.2.
>
> *Impact*: Other member computers and domain controllers in the domain or
> forest might not be able to locate this domain controlle
Site is based in Korea based on the IP and whois, so it does sound like
some sort of access controls are in place on one end or the other. I was
able to access the site.
-Will
On Fri, Nov 18, 2011 at 9:30 AM, Jan-Piet Mens wrote:
> > I have found that www.thisisgame.com does not reso
in 38 ms
thisisgame.com. 1800IN A 1.234.35.120
thisisgame.com. 1800IN NS ns1.thisisgame.com.
;; Received 82 bytes from 1.234.35.141#53(ns1.thisisgame.com) in 187 ms
-Will
On Fri, Nov 18, 2011 at 9:27 AM, Will Lists wrote:
> Maybe a network/firewa
172800 IN NS ns1.thisisgame.com.
;; Received 66 bytes from 192.35.51.30#53(f.gtld-servers.net) in 60 ms
- Will
On Fri, Nov 18, 2011 at 9:23 AM, King, Harold Clyde (Hal) wrote:
> This is the trace I get trying to resolve the domain.
>
> dig +trace thisisgame.com
>
uot; records.
If not a match then don't do anything.
This was just a quick process I white-boarded so I am pretty sure it's not
going to work out this way when all is said and done.
Thanks.
-Will
___
Please visit https://lists.isc.org/ma
Ah, never mind that last question. Brain hadn't been put in gear yet. :-)
-Will
On Wed, Nov 16, 2011 at 7:21 AM, Will Lists wrote:
> Just for for my own knowledge, as I haven't had the issue (yet), what log
> would this error appear in?
>
> Thanks.
>
> -Will
>
Just for for my own knowledge, as I haven't had the issue (yet), what log
would this error appear in?
Thanks.
-Will
On Wed, Nov 16, 2011 at 7:18 AM, Evan Hunt wrote:
>
> > can we have a paradigm shift from ISC please? instead of falling over
> > dead with insist/as
?
named[16593]: success resolving 'ns2.gslb.com/A' (in 'gslb.com'?) after
disabling EDNS
-- ?
Thanks
-Will
On Tue, Nov 1, 2011 at 9:13 AM, Ben Croswell wrote:
> If a given forwarder is "bad " it get its round trip time, rtt, set high
> and will not be
.
-Will
On Tue, Nov 1, 2011 at 8:54 AM, Ben Croswell wrote:
> If you have a global forwarder in place there are two options that affect
> its use. Forward first, the default, and forward only.
> Forward first will exhaust the forwarders you have and then attempt to
> follow NS reco
"...";
The hints DB file is current as of the version of BIND in use (2011060800).
Thanks.
-Will
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc
on in Windows nslookup and fortunately the bad characters made the
record easy to spot in the list.
I don't know that this scenario would cause your situation, but it was close
so I thought it might be of some help.
-Will
-Original Message-
From: bind-users-bounces+lists
On Dec 3, 10:00 pm, Kevin Darcy <[EMAIL PROTECTED]> wrote:
> will wrote:
> > For bureaucratic reasons I can not multi-home the slave name server;
> > however, I can multi-home the master name server.
>
> > I understand from reading the 'DNS for Rocket Sci
For bureaucratic reasons I can not multi-home the slave name server;
however, I can multi-home the master name server.
I understand from reading the 'DNS for Rocket Scientist' that when
using a 'view' statement to setup a split DNS to control visibility
that the slave server
13 matches
Mail list logo
