On Feb 5, 2016, at 6:09 PM, Noel Butler wrote:
> Why point them to an IP at all, just use TTL and SOA , no A no nothing else.
>
> They'll get NXDOMAIN when trying to look it up, problem solved.
One might point such domains to a local webserver which has been configured
to reply to all image req
On 06/02/2016 07:28, Olliver Schinagl wrote:
; BIND db file for ad servers - point all addresses to an invalid IP
$TTL864000 ; ten days
@ IN SOA ns0.example.net. hostmaster.example.net. (
2008032800 ; serial number YYMMDDNN
On 06/02/2016 07:25, Olliver Schinagl wrote:
I have configured my ad zone as a 'regular' set of zones all pointing
to the same 'null' zone and the only problem I really have is that the
newer binds no longer allows you to to do that, point to the same null
poppycock
our caching resolver loads
Hey Grant,
On 05-02-16 22:25, Olliver Schinagl wrote:
Hey Grant,
On 30-01-16 03:39, Grant Taylor wrote:
On 01/23/2016 01:47 PM, Olliver Schinagl wrote:
recently I updated to bind-9.10 and noticed that an illegal setup was
finally disallowed. Good things, but I (and others I'm sure) kind of
mi
Hey Mark,
On 05-02-16 22:47, Mark Andrews wrote:
Read the error message. It will tell you where a write instance
is and a read instance is or where two write instances are. In
this case it is on lines 7 and 3 of junk.conf (junk.conf:7 and
junk.conf:3).
% cat junk.conf
zone "a"
Read the error message. It will tell you where a write instance
is and a read instance is or where two write instances are. In
this case it is on lines 7 and 3 of junk.conf (junk.conf:7 and
junk.conf:3).
% cat junk.conf
zone "a" IN {
type master;
Hey Mark,
On 23-01-16 23:13, Mark Andrews wrote:
In message <56a3e6c7.5020...@schinagl.nl>, Olliver Schinagl writes:
Hi list,
recently I updated to bind-9.10 and noticed that an illegal setup was
finally disallowed. Good things, but I (and others I'm sure) kind of
miss-used this ability. With
Hey Grant,
On 30-01-16 03:39, Grant Taylor wrote:
On 01/23/2016 01:47 PM, Olliver Schinagl wrote:
recently I updated to bind-9.10 and noticed that an illegal setup was
finally disallowed. Good things, but I (and others I'm sure) kind of
miss-used this ability. With the change however, I am now
I agree that it could be the NAT firewall: some firewalls have features to
network-address-translate the answer portion of DNS responses.
Or with bind “views" (or “RRL") you could deliberately make it give
differing answers, but you’d know.
The firewall documentation might help.
Or you can test wh
9 matches
Mail list logo
