Jeremy Charles wrote [edited]:
> Here is what I want to happen:
> 1) Client sends query to my server for: bar.search4me.foo.com
>
> 2) My server recognizes search4me.foo.com to be "special"
> and issues queries to the up-stream DNS servers (the "real" DNS servers)
> to see if any of them exist:
> * bar.zone1.foo.com
> * bar.zone2.foo.com
> * bar.zone3.foo.com
>
> 3a) If any of those exist, my server returns the answer back to the client,
> pretending that it was the answer for bar.search4me.foo.com.
> (i.e The client has no idea it's actually getting bar.zone3.foo.com's
> information, for example. It doesn't care. Trust me.)
>
> 3b) If all of those get NXDOMAIN, my server returns NXDOMAIN back
> to the client. (Sorry, I tried, but I just couldn't find "bar"
> in any of the zones that I checked.)
>
> In other words... any query from a client that ends in "search4me.foo.com"
> should be interpreted as a request to perform a DNS suffix search order
> on behalf of the client.
since dnsmasq doesn't seem to handle it, maybe you should approach
the problem differently:
provide a zone "search4me.foo.com" automatically generated
by the contents of zones "zone1.foo.com", "zone2.foo.com", etc.
essentially, pre-compute and consolidate
the (successful) DNS suffix search zone results in a new zone.
yes, you change the zones a lot, but either add a last step
to your procedure for creating the updated search4me zone,
or use change notifications on a special nameserver...
--
-- zvr --
-- +---------------------------+ Alexios Zavras (-zvr-)
| H eytyxia den exei enoxes | [email protected]
+-----------------------zvr-+
_______________________________________________
Tech mailing list
[email protected]
http://lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
http://lopsa.org/
