Re: ISC considering a change to the BIND open source license

"The MPL license requires that anyone redistributing the code who has changed it must publish their changes ." Sounds like the MPL has the "(please?) share your changes with the other users of the software so that all may benefit" (directive?) Good, the MPL has that in common with the GPL. O

Re: ISC considering a change to the BIND open source license

(Sorry if this ends up on the list twice, did not send to "bind-users" the first time.) Is there any reason not to use a GPL license, which requires that changes be shared back with the user community? Keith ___ Please visit https://lists.isc.org/mailma

Re: Named will not start when $ORIGIN is present, other errors also, bind 9.7.3-p3

Aha. Thank you Mark, and rob0, that should remedy it. Appreciate your quick response(s.) ==Keith ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org htt

Named will not start when $ORIGIN is present, other errors also, bind 9.7.3-p3

Hello, Attempting to set up a small dns server purely for testing purposes, using a non-existent domain name. I have run into problems with my very simple setup, have tried changing multiple tokens in the config files, no success, but have found a few items: - The zone file loads, and BIND sta

Explanation of a resolver.c error message

Could anyone offer an explanation for what condition(s) trigger this error in older, out of date versions of BIND, specifically, BIND 9.5.1b1 ? resolver.c:5617: REQUIREquery) != ((void *)0)) && (((const isc__magic_t *)(query))->magic == ((('Q') << 24 | ('!') << 16 | ('!') << 8 | ('!')) fai

How to prevent slaves from contacting master for name resolution?

Our redundant DNS configuration is one master and three slaves, spread across two colo facilities. master and slave1 are in colo_ALPHA. slave2 and slave3 are in colo_BETA. During an extended maintenance window, the master DNS was offline. Slave2 was trying to contact the master, and lookups faile

Can bind log the IP of clients requesting lookups to a domain?

Version - bind 9.5.1 on CentOS 5.x. Is there a way to log either the IP of clients requesting lookups of a particular domain? In other words, I'd like to know the IP of clients trying to resolve app01.foocompany.net (for example.) There is probably a logging option but I'm not sure what it might

Finding and culling unused entries from zone files

I'm looking for a method to cull out unused DNS entries from zone files. Eventually, entries we add to zone files entries fall into disuse. Usually the customers never report when this happens, so the zone files grow and grow and grow with "cruft." Can any of you share recommendations? I'm runni