How to be a master server for all the incoming requests barring a few ?

Kevin Darcy kcd at daimlerchrysler.com
Mon Aug 26 20:43:17 UTC 2002


sanapala at yahoo.com wrote:

> Hello all,
> I need your help in configuring named to be a master server for all
> the requests barring a few requests.
> We have a linux machine on which webserver and named are running. All
> the clients in our environment are in two states: "Authorized" and
> "Unauthorized".
> Initially all the clients are put in "Unauthorized" state and linux
> machine on which named and webserver are running is configured as DNS.
> Whenever user tries to launch a browser with any request, our
> DNS/webserver resolves the request to its own IP and displays a logon
> dialog to enforce the user to enter user name, password and domian
> name. Logon dialog is displayed using the webserver running on our
> linux DNS. Once the user is authenticated, at that point he gets new
> set of DHCP attributes and client machine is put into "Authorized"
> state which will have new real DNS.
> The following named.conf worked fine until the new requirement come
> in:
> options {
> directory "/var/named";
> forward first;
> forwarders {
> 192.168.66.243;
> };
> };
> zone "." {
> type master;
> file "zone/root.hints";
> };
> zone "localhost" {
> type master;
> file "zone/localhost";
> };
> zone "0.0.127.in-addr.arpa" {
> type master;
> file "zone/127.0.0";
> };
> /*********Endof named.conf *******/
> root.hints:
>
> @ IN SOA urt-appliance4.mvpx.com. hostmaster.mvpx.com. (
> 2001062702      ; Serial number
> 86400           ; Refresh 1 day
> 7200            ; Retry   2 hours
> 3600000         ; Expire 41.67 days
> 172800 )        ; Minimum TTL 2 days
>
> .. 3600000 IN NS      urt-appliance4.mvpx.com.
> * IN A 192.168.66.243
> /*********Endof root.hints *******/
>
> Now the problem is since the linux DNS/webserver resolves all the
> requests to its own IP, even the requests for server1.mvpx.com are
> also being resolved to its own IP. But the request for
> something.mvpx.com should be resolved by other real DNS which I
> specify.
> Sure there must be a way to configure named so that all the incoming
> requests to be resolved to its own IP except some requests to be
> resolved by another DNS.
> Any help is much appreciated.

Delegate mvpx.com from your root zone. Delegation overrides wildcarding.
Don't forget the glue records.

By the way, it's very confusing for you to call that root *master* file
"root.hints". A root "hints" file is something quite different....


- Kevin




More information about the bind-users mailing list