Re: generate the same answer to any query

4 msg	Problem with Authoritative PTR Records
4 msg	ACLs as external files

generate the same answer to any query
\ Dan Sabau (5 Mar 2007)
. \ David Nolan (5 Mar 2007)

2 msg	nsupdate strangeness v 9.2.3 vs. 9.3.x / 9.4.x
3 msg	Strange DNS Queries
2 msg	bind9.4
3 msg	problems reaching google
2 msg	Statistics query
2 msg	Bind Configuration in fedora core 6
16 msg	Are underscores no longer supported in Bind 9.4?
11 msg	BIND sending quesries to 127.0.0.2?
2 msg	bind 9.2 9.3 different behavior reverse DNS sub...
4 msg	rndc reload doesn't update zone
2 msg	Force reload when include changes
3 msg	Question about nameserver selection mechanism
3 msg	high availability configuration error?
1 msg	cache cleaner could not create iterator: out of...
8 msg	recursive queries fail with high load?
4 msg	Unexpected behaviour from the B root servers? A...
8 msg	Denial of Service

Subject:	Re: generate the same answer to any query
Group:	Bind-users
From:	David Nolan
Date:	5 Mar 2007

--On Monday, March 05, 2007 16:23:16 +0200 Dan Sabau <dan.sabau>
wrote:

> Hi,
> I'm new to this list so sorry if I ask something that was already posted.
> What I wont to do is something like this:
> for all the ip's that query my dns server return a valid replay and for
> some ip's to replay to the request with the same thing.
> To be more clear host A query's DNS server 1 and asks for
> www.google.com, what I wont to do is that DNS replay with 1.1.1.1 and
> not with google's ip. I know I have to work with view's that is not the
> issue, the issue is how do I do the thing that I've described befor in
> the google example.

In your named.conf:

view "fakedata" {
match-clients { IP-LIST-HERE; };
zone "." {
type master;
file "FAKE.zone";
};
};

in FAKE.zone:
$TTL 2
$ORIGIN .
@ IN SOA someserver.example.com host-master.example.com (1 1 1 1 1)
IN NS someserver2.example.com
IN NS someserver3.example.com

www.example.com IN A 1.1.1.2
captiveportal.example.com IN A 1.1.1.1
*.example.com IN A 1.1.1.1
*.com IN A 1.1.1.1
* IN A 1.1.1.1

(Adjust the fake date as desired of course, the key is that any domain you
put explicit entries in for must have its own wildcard entry, as with
*.example.com above.)

-David Nolan
Network Service
Carnegie Mellon University