Hi BIND expert,
I could not have sent the followings thru https://www.isc.org/bind-
subscription-contact/
due to error on the site.
--
I am a S/W engineer who is working on BIND, especially named in Seoul/Korea.
I've got reports from a customer regarding stucked "named" pr
Thank you for your response.. I thought of that earlier, but when I run the
exact same configure options on an older machine of ours (for 9.10.1) it
creates the output files just fine.. That is where it confused me.
Thanks
On Thu, Mar 17, 2016 at 5:18 PM, Mark Andrews wrote:
>
> *Think* about
I think I Know why it worked on the old server.. it is because there is an
existing Makefile already.. I am going to rename the existing makefile and
see if it creates one. If it doesnt, then I will know that the no-create
option is the culprit!
Thanks for your help.. I will report back with what
Hello all
I am trying to compile Bind 9.10.3-P4 from source and whenever I try to run
the following:
./configure --sbindir=/usr/sbin --sysconfdir=/etc/bind --with-openssl
--disable-openssl-version-check --no-create --no-recursion
I receive the following error after the configuration script is f
--no-create is for when you want to tinker with the final results built
into config.status prior to building the Makefiles.
I've committed changes to no run "make clean" if --no-create is set.
Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742
*Think* about the arguments you are passing to configure. You told configue
to NOT CREATE the makefiles.
Mark
In message
, Majid Mir writes:
>
> Hello all
>
> I am trying to compile Bind 9.10.3-P4 from source and whenever I try to run
> the following:
>
> ./configure --sbindir=/usr/sbin --s
Mark.
I owe you a virtual beer.. You were right! Thank you
Sorry I am still a n00b at this at times
On Thu, Mar 17, 2016 at 5:24 PM, Majid Mir
wrote:
> I think I Know why it worked on the old server.. it is because there is an
> existing Makefile already.. I am going to rename the existing mak
If I'm not mistaken, ms-self means that the client's hostname must match the
name of the record being updated. This is not the case in the reverse space,
where record names end in in-addr.arpa instead of cp.test.
Your DHCP server should own the reverse space. I don't know how else to manage
thi
Hello,
I am running bind 9.8 with GSS-TSIG on a SuSE Enterprise 11 PL 1 Server.
For my forward zones I have the following rules:
zone"cp.test" {
type master;
file "forward/cp.test";
notify yes;
update-policy {
On Thu, Feb 17, 2011 at 09:53:43AM -0500, Ryan Novosielski wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Glad to hear it was a help.
>
> Does anyone happen to know if anything changed for .gov addresses just
> last week? This problem appears to have come out of the clear blue sky
>
al Message-
> From: bind-users-bounces+jlightner=water@lists.isc.org
> [mailto:bind-users-bounces+jlightner=water@lists.isc.org] On Behalf
> Of Ryan Novosielski
> Sent: Thursday, February 17, 2011 9:54 AM
> To: Xiaoxu Huang
> Cc: bind-users@lists.isc.org
> Subject: Re:
=water@lists.isc.org] On Behalf
Of Ryan Novosielski
Sent: Thursday, February 17, 2011 9:54 AM
To: Xiaoxu Huang
Cc: bind-users@lists.isc.org
Subject: Re: Please Help
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Glad to hear it was a help.
Does anyone happen to know if anything changed for .gov
>
> -Original Message-
> From: bind-users-bounces+xhuang=graphnet@lists.isc.org
> [mailto:bind-users-bounces+xhuang=graphnet@lists.isc.org] On Behalf Of
> Ryan Novosielski
> Sent: Wednesday, February 16, 2011 5:47 PM
> To: bind-users@lists.isc.org
> Subject:
-bounces+xhuang=graphnet@lists.isc.org] On Behalf Of
Ryan Novosielski
Sent: Wednesday, February 16, 2011 5:47 PM
To: bind-users@lists.isc.org
Subject: Re: Please Help
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I asked this same question this week. Check the list archives.
On 02/16/2011 05
Sent: Wednesday, February 16, 2011 5:47 PM
To: bind-users@lists.isc.org
Subject: Re: Please Help
On 02/16/11 23:24, Xiaoxu Huang wrote:
> From couple of our DNS servers, we are failed to get correct DNS answer
> like followings:
>
> 1) From server A
> # nslookup
> Default Server:
On 02/16/11 23:24, Xiaoxu Huang wrote:
> From couple of our DNS servers, we are failed to get correct DNS answer
> like followings:
>
> 1) From server A
> # nslookup
> Default Server: localhost
> Address: 127.0.0.1
> > www.nyc.gov
> Server: localhost
> Address: 127.0.0.1
> *** localhost can't f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I asked this same question this week. Check the list archives.
On 02/16/2011 05:24 PM, Xiaoxu Huang wrote:
> From couple of our DNS servers, we are failed to get correct DNS answer
> like followings:
>
> 1) From server A
>
> # nslookup
>
> Default
>From couple of our DNS servers, we are failed to get correct DNS answer like
followings:
1) From server A
# nslookup
Default Server: localhost
Address: 127.0.0.1
> www.nyc.gov
Server: localhost
Address: 127.0.0.1
*** localhost can't find www.nyc.gov: Non-existent host/domain # ns
Ken Lai wrote:
Scott Haneda wrote:
99% of the time openDNS works by just pointing some agent to their ip
space.
That 1% of the time, openDNS tries to make DNS responses that are
modified in a way to try to help you.
Maybe this is your issue?
Googl.com being common enough they elect to retu
Scott Haneda wrote:
99% of the time openDNS works by just pointing some agent to their ip
space.
That 1% of the time, openDNS tries to make DNS responses that are
modified in a way to try to help you.
Maybe this is your issue?
Googl.com being common enough they elect to return the google.co
http://www.xname.org
other dns service
On Sun, 19 Jul 2009 11:20:32 -0700, Scott Haneda
wrote:
> 99% of the time openDNS works by just pointing some agent to their ip
> space.
>
> That 1% of the time, openDNS tries to make DNS responses that are
> modified in a way to try to help you.
>
> Maybe
99% of the time openDNS works by just pointing some agent to their ip
space.
That 1% of the time, openDNS tries to make DNS responses that are
modified in a way to try to help you.
Maybe this is your issue?
Googl.com being common enough they elect to return the google.com's
answer istead
imple question, please help
my bind server have a default option
forwarders { 208.67.222.222; 208.67.220.220; };
to send all query to OpenDNS.
but some answer could not access, while a answer can which solved by another
server
i put these in the config:
zone "x.com" {
type forwar
my bind server have a default option
forwarders { 208.67.222.222; 208.67.220.220; };
to send all query to OpenDNS.
but some answer could not access, while a answer can which solved by another
server
i put these in the config:
zone "x.com" {
type forward;
forwarders { x.x.x.x; };
};
bu
24 matches
Mail list logo
