On 5/1/12 2:32 PM, "Augie Schwer" wrote:
>> Contrary to what a lot of other people have suggested, it is in fact
>> possible using the socket API to bind() to IPs which aren't explicitly
>> created, due to special handling on the loopback interface. This can
>> certainly be done under Linux, for e
On Tue, May 1, 2012 at 2:00 AM, Phil Mayers wrote:
> Which operating system are you running?
Linux, I'm sorry I did not mention that earlier as it may have saved
some confusion.
> Contrary to what a lot of other people have suggested, it is in fact
> possible using the socket API to bind() to IP
Chris Thompson wrote:
> Our regular DNS changes (via [scripted] nsupdate) always add the SOA
> explicitly (it's going to change anyway, after all), setting the serial
> to the Unix time(2) value. BIND may have been incrementing the serial
> itself as a result of re-signing activity, but we assume
Hello,
I am trying to increase forwarder timeout in bind 9 (recursive query). Does
anyone know which part of code is dealing with timeouts? I was unable to
conclude by quick look at the source. I will appreciate any hints.
Regards,
--
Stefan Certic
Routo Telecommunications Ltd
2nd Floor
Ki
On 5/1/12 8:10 AM, "Anand Buddhdev" wrote:
> On 01/05/2012 16:36, Chris Thompson wrote:
>
>> Our regular DNS changes (via [scripted] nsupdate) always add the SOA
>> explicitly (it's going to change anyway, after all), setting the serial
>> to the Unix time(2) value. BIND may have been incrementin
On 01/05/2012 16:36, Chris Thompson wrote:
> Our regular DNS changes (via [scripted] nsupdate) always add the SOA
> explicitly (it's going to change anyway, after all), setting the serial
> to the Unix time(2) value. BIND may have been incrementing the serial
> itself as a result of re-signing act
On May 1 2012, Phil Mayers wrote:
On 01/05/12 11:20, cloud cache wrote:
But, how will I know the current serial number of the zone, if the zone
has been changing frequently?
In the past, I've used a script that queries the SOA just before doing
the update (which is safe, because in a race c
In article ,
Larry Brower wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 04/30/2012 07:13 PM, Augie Schwer wrote:
> > Thanks for the reply, please see my previous e-mail about the address
> > being perfectly pingable on that interface.
> >
>
> Whats that have to do with any
On 01/05/12 11:20, cloud cache wrote:
But, how will I know the current serial number of the zone, if the zone
has been changing frequently?
In the past, I've used a script that queries the SOA just before doing
the update (which is safe, because in a race condition you'll be "too
low" and fa
On 05/01/2012 10:00 AM, Phil Mayers wrote:
So you might be being a bit too clever, and foxing the named socket code
I'm afraid.
That should of course be "the named socket code is foxing you". Sigh.
___
Please visit https://lists.isc.org/mailman/listi
On 04/30/2012 10:56 PM, Augie Schwer wrote:
I must be doing something wrong, because what I want to do doesn't
seem that difficult.
I have a range of IPs bound to a local interface:
lo:1 Link encap:Local Loopback
inet addr:10.0.0.1 Mask:255.255.255.224
And I want to convince B
On 04/27/2012 02:37 AM, cloud cache wrote:
Hello,
How to use nsupdate to dynamic update the SOA records?
For example, I want to update the zone's contact email and main NS
As others have pointed out, you just need to use "nsupdate" and send a
valid SOA.
NOTE: "valid" means "must have a seri
12 matches
Mail list logo
