[no subject]

In message , hugo hugoo writes: > > Doug > > The problem is that the parent zone and the subzone are on the same name se= > rver. > > If I do a dig @name_server subzone NS or dig @name_server zone NS ... = > I receive the same NS answer. Hugo, you asked this before and you got a number o

Re:

On 3/19/2012 3:58 PM, hugo hugoo wrote: > Doug, > > The problem is that the parent zone and the subzone are on the same name > server. > > If I do a dig @name_server subzone NS or dig @name_server zone NS > ... I receive the same NS answer. Then you would need access to the text files. --

RE:

Doug, The problem is that the parent zone and the subzone are on the same name server. If I do a dig @name_server subzone NS or dig @name_server zone NS ... I receive the same NS answer. > From: do...@dougbarton.us > To: hugo...@hotmail.com > CC: cat...@isc.org; bind-users@lists.isc.org

Re:

On 3/19/2012 10:08 AM, hugo hugoo wrote: > Hello, > > I have correctly understood the need to have the NS of a subdomain in > the parent domain to avoid any malfunction with a future migratio to DNSSEC. > > But can anybody give me a clear method to detect such missconfiguration? > Is this possi

Re: reverse dns for IPV6 ranges

On Mon, 19 Mar 2012, hugo hugoo wrote: Jay, - Can you give me an example of such configuration? Sure. Say I use a DHCP pool of :a123:b456::/96 within each /64 subnet. For example: subnet DHCP pool _ ___ 2001:db8:0:a::/64 2001:d

Re: reverse dns for IPV6 ranges

On 3/19/12 11:58 AM, "Peter Andreev" wrote: > 2012/3/19 hugo hugoo >> Jay, >> >> - Can you give me an example of such configuration? >> >> As anyone else some examples of IPV6 reverse configuration used in >> production environment? >> >> Thanks for sharing your experience... > > We use IPv6

Re: "rndc reconfig" vs. "rndc reload"

Yeah, I'm familiar with the improvements to "reconfig". You all have answered my questions. To be clear, the issue was that "reload" by itself was taking way too long. We have already implemented changes for when the *list of zones* has not changed, we do "reload " for each individually-chang

Re: Name Resolution issue with one domain

On 19/03/2012 21:28, babu dheen wrote: Babu, > Dear Support, > > I am trying to resolve www.dubaiairport.com from my GW BIND server > as below. But not getting any output > > $ dig A www.dubaiairport.com > ; <<>> DiG 9.3.4-P1 <<>> A www.dubaiairport.com > ;; global options: printcmd > ;; co

Re: Name Resolution issue with one domain

On 03/19/12 13:28, babu dheen wrote: Dear Support, I am trying to resolve www.dubaiairport.com from my GW BIND server as below. But not getting any output $ dig A www.dubaiairport.com ; <<>> DiG 9.3.4-P1 <<>> A www.dubaiairport.com

Name Resolution issue with one domain

Dear Support,    I am trying to resolve www.dubaiairport.com from my GW BIND server as below. But not getting any output    $ dig A www.dubaiairport.com ; <<>> DiG 9.3.4-P1 <<>> A www.dubaiairport.com ;; global options:  printcmd ;; connection timed out; no servers could be reached   Whereas, whe

Re: zone transfer with DIG: SOA duplicate

On 3/19/12 10:49 AM, "hugo hugoo" wrote: > thanks for this quick answer. > I am a liitle bit lost... > > What is the starting and ending SOA record? > > In the original zone, there is ony one SOA record... FWIW, When transferring it is normal to get the SOA as first and last record. Use +on

Re: reverse dns for IPV6 ranges

2012/3/19 hugo hugoo > Jay, > > - Can you give me an example of such configuration? > > > > As anyone else some examples of IPV6 reverse configuration used in > production environment? > > Thanks for sharing your experience... > > Hugo, > We use IPv6 in production environment. It was a real hea

Re: zone transfer with DIG: SOA duplicate

> What is the starting and ending SOA record? > > In the original zone, there is ony one SOA record... The "starting" SOA is the SOA in your zone. The final SOA is used to indicate end-of-transfer and is a copy of the first; you can safely ignore it or, as Michael pointed out, supress it.

Re: zone transfer with DIG: SOA duplicate

On 19/03/2012 18:49, hugo hugoo wrote: > thanks for this quick answer. > I am a liitle bit lost... > > What is the starting and ending SOA record? > > In the original zone, there is ony one SOA record... The SOA record at the end signals the end of the zone transfer. Regards, Anand

RE: zone transfer with DIG: SOA duplicate

Hello, thanks for this quick answer. I am a liitle bit lost... What is the starting and ending SOA record? In the original zone, there is ony one SOA record... Hugo, > Date: Mon, 19 Mar 2012 10:41:22 -0700 > From: mich...@rancid.berkeley.edu > To: hugo...@hotmail.com > CC: bind-users

Re: zone transfer with DIG: SOA duplicate

On 03/19/12 10:33, hugo hugoo wrote: Dear all, I have this strange behaviour when I do a zone transfer with the following commande: dig @name_server zone_name AXFR ==> I received 2 SOA records (duplicates). One SOA record is at the end of the received information. Is this normal? Yes. I

zone transfer with DIG: SOA duplicate

Dear all, I have this strange behaviour when I do a zone transfer with the following commande: dig @name_server zone_name AXFR ==> I received 2 SOA records (duplicates). One SOA record is at the end of the received information. Is this normal? Thanks for any feedback, Hugo,

RE: reverse dns for IPV6 ranges

Jay, - Can you give me an example of such configuration? As anyone else some examples of IPV6 reverse configuration used in production environment? Thanks for sharing your experience... Hugo, > Date: Mon, 12 Mar 2012 16:28:53 -0500 > From: jay-f...@uiowa.edu > To: hugo...@hotmail.co

RE:

Hello, I have correctly understood the need to have the NS of a subdomain in the parent domain to avoid any malfunction with a future migratio to DNSSEC. But can anybody give me a clear method to detect such missconfiguration? Is this possible with dig or is it ony possible with the access to