uhm - look at the bottom - *they have* a zero TTL after named-compilezone
Am 05.06.2014 16:48, schrieb Reindl Harald:
Hi
how is that below possible?
* ns2.thelounge.net = Master
* ns1.thelounge.net = Slave
* both are using the same packages (VMwware clones)
* i removed the zone file on
what the hell invents $TTL 0 ; 0 seconds lines before
each CNAME block while on the master there is exactly
one TTL line with 86400 on top of the file?
_
master-zone:
[root@ns2:~]$ cat
On Thu, Jun 05, 2014 at 05:21:47PM +0200, Reindl Harald wrote:
what the hell invents $TTL 0 ; 0 seconds lines before
each CNAME block while on the master there is exactly
one TTL line with 86400 on top of the file?
The way named writes a zone file is not the way I would do it.
Records are
Am 05.06.2014 17:58, schrieb /dev/rob0:
On Thu, Jun 05, 2014 at 05:21:47PM +0200, Reindl Harald wrote:
what the hell invents $TTL 0 ; 0 seconds lines before
each CNAME block while on the master there is exactly
one TTL line with 86400 on top of the file?
The way named writes a zone file
Cisco routers do have the ability to doctor DNS packets when doing NAT.
When it doctors it sets the TTL to 0 but I dont know why it would only do
it on CNAME records.
On Jun 5, 2014 12:43 PM, Reindl Harald h.rei...@thelounge.net wrote:
Am 05.06.2014 17:58, schrieb /dev/rob0:
On Thu, Jun 05,
Am 05.06.2014 18:48, schrieb Ben Croswell:
Cisco routers do have the ability to doctor DNS packets when doing NAT
argh - and it is on by default
no ip nat service alg udp dns
no ip nat service alg tcp dns
When it doctors it sets the TTL to 0 but
I dont know why it would only do it on CNAME
6 matches
Mail list logo
