Bind 9.2.3 and wildcard entries
Michael Varre
bind9 at kishmish.com
Tue Jul 20 20:29:45 UTC 2004
> -----Original Message-----
> From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
> Behalf Of Christopher T. Beers
> Sent: Tuesday, July 20, 2004 4:12 PM
> To: bind-users at isc.org
> Subject: Bind 9.2.3 and wildcard entries
>
> We are trying to create a quarantine network at Syracuse University. To
> support this, we are looking to configure DNS so that almost all entries
> point to a particular IP address (which has a website to help our troubled
> students).
>
> Anyhow we do this like this in Bind 9.2.1 on our current system:
>
> -----------
> ; this is the default record
> * IN A 128.230.18.61
> ; these hosts are then specifically permitted
> cms.syr.edu. IN A IP ADDRESS
> other.entries.that.we.really.want.to.resolve.correctly
>
> -----------
>
> In 9.2.3 this does not work. Any chance this has something to do with ISC
> disabling Verisign SiteFinder services in the code? If so, are there any
> option that I can put in the named.conf or a patch to allow this to happen
> on our quarantine network?
I'm running 9.2.3 and using wildcard support with no problem so I don't
believe the functionality has been taken out of bind 9.x.x
How isn't it working? Just saying it cant resolve? Any log entries?
p.s. GO SU!
>
> Also looks like bug id 1448 ([bug] Handle empty wildcards labels.) could
> have broken the functionality we need. Appreciate the help (and I am not
> subscribed to the list so please copy me on replies).
>
> Regards,
>
> --
> Christopher T. Beers
> UNIX Systems Engineer - Syracuse University
> 250 Machinery Hall Syracuse, NY 13244
> (315) 443-4103 Office (315) 443-1621 Fax
>
More information about the bind-users
mailing list