Slave Configuration

Danny Mayer mayer at gis.net
Thu Nov 23 04:02:54 UTC 2000


		One other issue you should be aware of: BIND on NT creates the
  resolv.conf file on startup, on my version only if it doesn't already exist.
  This file lives in system32\Drivers\etc.

		Danny

At 11:00 AM 11/22/00 -0600, Jamie P. Bontrager wrote:
>
>Thanks for the input. I have everything configured as you listed...my zone
>files look exactly like that. We are in the process of rearranging servers
>and equipment so I'm thinking it has something to do with that.
>
>Thanks,
>Jamie P. Bontrager
>KCTC.net
>
>-----Original Message-----
>From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
>Behalf Of Colin Stefani
>Sent: Wednesday, November 22, 2000 9:39 AM
>To: 'Jamie P. Bontrager '; 'bind-users at isc.org '
>Subject: RE: Slave Configuration
>
>
>
>Sorry to hear you're leaving the Land of Unix :-)
>
>Anyway, I think you might have to do some reading to make this one work out
>for you in the end. One important detail missing in your note here is how is
>it not working? Can clients not query it? or is it not able to do zone
>x-fers from the primary?
>
>DNS servers really like to have an internet connection availible for doing
>root server look ups and reverse lookups. I would get that machine connected
>and see what happens. How is it able to contact the master server if it's
>not connected to the internet? If it cannot, that could cause problems also.
>
>Regardless, in terms of configuration, you will want to have that salve
>server's name/ip address appear is every zone files it's going to be a
>secondary for as an NS record, so for example in the heading of the zone
>file (e.g. a zone file called mydomain.com) would look like this, with
>ns2.mydomain.com being the slave and ns1 being master:
>
>@       SOA     ns1.mydomain.com. root.mydomain.com. (
>                2000101701
>                10800                   ; Refresh after 3 hours
>                3600                    ; Retry after 1 hour
>                604800                  ; Expire after 1 week
>                86400 )                 ; Minimum TTL of 1 day
>@       NS      ns1.mydomain.com.
>        NS      ns2.mydomain.com.
>        A       192.168.123.123
>        MX      5 mx1.mydomain.com.
>        MX      50 mx2mydomain.com.
>
>If the NEW secondary is not listed in the Master's zone file for the domain
>you are trying to x-fer, then it will not recieve updates from the master.
>
>Next, check both sides "named.conf" files (on the master and the new
>secondary). In the Master's .conf file, make sure there are no zoen x-fer
>restrictions set that only allow the current slaves to transfer zone files.
>In the slave's conf file check to make sure that the zones you are trying to
>transfer are listed similar to this:
>
>zone "mydomain.com" {
>        type slave;
>        file "mydomain.com";
>        masters { 192.169.123.121; };
>};
>
>Where the masters entry lists the master DNS server's ip address you are
>trying to pull zone files from. If this isn't listed, the secondary will
>assume it's not authoritative for that zone and won't accept an update or
>try to go get the new zone file when started.
>
>I don't know how bind on NT logs, but that would be the best place to start.
>I would check the event log/ text log it creates and see what errors have
>arisen. I imagine you'll find a bunch of info relating to your problem.

>
>
>hope it helps somewhat,
>
>colin.s
>
>-----Original Message-----
>From: Jamie P. Bontrager
>To: bind-users at isc.org
>Sent: 11/22/00 7:04 AM
>Subject: Slave Configuration
>
>
>Hi all,
>
>We are currently switching are whole operation over to NT from UNIX. And
>right now the task at hand is DNS. We are familiar with Bind for Unix so
>we
>decided to implement Bind for NT 8.2.3. Right now we have Bind on one of
>our
>new NT servers that's not live on the internet yet (which may be the
>problem). We are trying to test it as the secondary (i.e. slave) DNS but
>are
>having trouble achieving this. We are most certain that we have the
>slave
>dns configured correctly according to the samples provided. I really
>don't
>like to read much and so I'm in need of some more examples of how a
>working
>slave dns configuration for bindnt looks. If anyone would be so kind,
>whether it's your own or an in-depth example, you can email it to the
>address below. Sure would appreciate it. Any other resources would be
>helpful to.
>
>Thanks,
>Jamie P. Bontrager
>KCTC.net
>jamie at kctc.net
> 



More information about the bind-users mailing list