Re: Question abut reserv zone

Good morning, Am 2018-02-13 hackte Mark Andrews in die Tasten: > ISP’s are only scared of it because people may add “.sucks” as > the name in the > PTR record. ROTFL! > Mark Have a nice day -- Michelle KonzackMiila ITSystems @ TDnet GNU/Linux Developer 00372-54541400

Re: Question abut reserv zone

The reverse of a /8 is pretty big. I would do it as reverses of /16’s or /24’s. That also lets you mix and match management styles, but for a /24 which has multiple administrators DNS UPDATE is still the way to go. Machines should be updating their own PTR records using DNS UPDATE. DNS UPDATE

RE: Question abut reserv zone

You mean, don't slave 100.10.in-addr.arpa at all, and just maintain 10.in-addr.arpa locally? The problem the original poster may run into, however, is that there may be other records in 100.10.in-addr.arpa that change dynamically, and those changes may not be reflected if only 10.in-addr.arpa

Re: Question abut reserv zone

In this example since the address is the same I would just pick one name (the name the machine knows itself as) and use that name for the PTR record. I would also use DNS UPDATE to update the reverse zones rather than editing master files. You can delegate update authority down to the

Question abut reserv zone

Hi, I have a zone, we say abc.edu.au, all private address 10.0.0.0/8 is in this zone. So, I have a revers zoon 10.in-addr-arpa existed. I am the master. Now, there is a new zone required - ddd.abc.edu.au reverse should 100.10.in-addr-arpa; we are

Re: Minimum TTL?

From: "Reindl Harald" > To: bind-users@lists.isc.org > the ISP has no business to touch any package bewteen source and me > because he can't know the implications - he even must not know about > them because it#s not his business And yet they do (Supercookies?), and

Re: SOA Minimum comment in "dig" output

RFC 2308 "DNS NCACHE" defines the last field of the SOA RR as "the TTL of negative responses". On 12.02.18 10:29, Daniel Stirnimann wrote: Negative caching TTL is not defined as the last field of the SOA RR: yes, it is, as RFC 2308 section 4 says: The remaining of the current meanings,

Re: Saurabh: Error while adding the Domain into RPZ as Bad Name.

On 12.02.18 13:51, Saurabh Srivastava wrote: *I have faced one issue during the addition of one domain into My RPZ Server.* you don't have to put asterisks around your sentences. In fact, it makes them harder to read and understand. *The Domain name is "xmr.-eu1.nanopool.org

Re: SOA Minimum comment in "dig" output

Hello Carsten, > RFC 2308 "DNS NCACHE" defines the last field of the SOA RR as "the TTL of > negative responses". Negative caching TTL is not defined as the last field of the SOA RR: "When the authoritative server creates this record its TTL is taken from the minimum of the SOA.MINIMUM field

Re: SOA Minimum comment in "dig" output

Hi, here is a question I've got during a DNS training, and I still do not have a good answer: RFC 2308 "DNS NCACHE" defines the last field of the SOA RR as "the TTL of negative responses". ; << DiG 9.10.3-P4-Ubuntu << +noall +answer +multi +cmd soa example.com ;; global options:

Saurabh: Error while adding the Domain into RPZ as Bad Name.

Dear Bind-Users, Greeings of the Day!!! *I have faced one issue during the addition of one domain into My RPZ Server.* *The Domain name is "xmr.-eu1.nanopool.org ".* *I am trying to put the domain entry as *. xmr.-eu1.nanopool.org which gives me