BIND / NT problem

joseph lang tcnojl1 at earthlink.net
Mon Jul 31 12:12:46 UTC 2000


Anthony Cross wrote:
> 
> I have been running the Windows NT port on BIND v4.9.5 from software.com
> (http://www.software.com) for some time as an alternative to our ISP's
> usually 'touchy' DNS servers for our Mailer-Daemon. Network is
> WindowsNT4SP6a with MS DNS disabled and all works well, without too much
> drama, but I am forever having to remove BIND entries from the Windows NT
> Event Log, such as
> 
> ns_forw: sendto([198.41.0.4].53): error code = 0
> ns_forw: sendto([203.8.183.1].53): error code = 0
> ns_forw: sendto([128.9.64.26].53): error code = 0
> Err/TO getting serial# for "spiritmodems.com.au"
> Err/TO getting serial# for "0.168.192.in-addr.arpa"
> (xfer for spiritmodems.com.au failed) (child = 168) - rescheduling!
> (xfer for 0.168.192.in-addr.arpa failed) (child = 180) - rescheduling!
> 
> The connection from the WinNT machine is via RAS/DUN to our ISP (not the SOA
> holder for spiritmodems.com.au) and all mail transfers and lookups performed
> by the Mailer-Daemon work perfectly.
> 
> _______________________________________________________________
> FILES
> ----------------------------------------------------------------------------
> -----------------------------------
> --db.127.0.0 file--
> @        IN SOA    0.168.192.in-addr.arpa. hostmaster.spiritmodems.com.au. (
>             951213   ; serial number
>             43200    ; refresh every 12 hours
>             7200     ; retry after 2 hours
>             1209600  ; expire after 2 weeks
>             172800)  ; default ttl is 2 days
> ;
>          IN NS    cobra.spiritmodems.com.au.
> ==========================================================
> --named.boot file--
> directory      D:\\bind
> primary 0.0.127.IN-ADDR.ARPA db.127.0.0
> secondary spiritmodems.com.au 203.2.192.124 db.zoneinfo
> secondary 0.168.192.in-addr.arpa 203.2.192.124 db.inaddr
> cache . db.cache
> 
> Entries in the file were created by the BIND set-up. Installation was as a
> "Caching Only Server", that is not authoritative for any zone.
> 
> Anthony Cross
> Administration Manager
> Spirit Technology
> www.spiritmodems.com.au
> (a division of Mike Boorne Electronics Pty Limited)
> 'The Spirit Modem people...'
> 
> - - -
I see two problems:

you are secondary to 203.2.192.124 for spiritmodems.com.au
but 203.2.192.124 is not athoritative for that zone.

do you really mean for 203.2.192.124 to be primary for 
the 192.168.0 reverse zone? (also not athoritative)

joe lang



More information about the bind-users mailing list