03-25-2006 was pulled for some reason (not DNS related though). Upgrade to http://pfsense.com/~sullrich/RELENG_1_SNAPSHOT_03-26-2006/ and try again. Also keep in mind that you have to set some special routes for your ISPs DNS-Servers when using multiwan or policy based routing so the DNS requests go out through the correct interface (see http://forum.pfsense.org/index.php?topic=756.msg5114#msg5114 for details).
Holger > -----Original Message----- > From: Stéphane Karges [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 28, 2006 10:09 AM > To: [email protected] > Subject: Re: [pfSense Support] Re: DNS problem with Beta2 > > > Hi All, > > Thanks Emanuel, it's exactly my problem, I thinks it's a bug. > The problem is > I have 40 macintosh and if it need to add dns manually, it's > a problem for > me. > > I use pfsense in dhcp mod, it see the dns server but when all mac are > connecting via dhcp on pfsense, they have ip, gateway .. But > not the DNS. > I have update to RELENG_1_SNAPSHOT_03-25-2006 because I have a little > problem with the load balancing in BETA2 and I can't get DNS > from pfsense. > > Regards, > > Stephane Karges > France > > On 28/03/06 7:01, "Emanuel A. Gonzalez" > <[EMAIL PROTECTED]> wrote: > > > Well, in fact, I got the same issue here, using > > RELENG_1_SNAPSHOT_03-25-2006, fresh install. > > > > I was using "DNS forward" option, DHCP with staticARP, any > of the internal > > clients got its address from pfsense DHCP server, and as > DNS the same > > pfsense box. > > > > I'm setting the DNS servers manually in pfsense, but they are up and > > responding. As stated Stepahe, I can resolve from the > pfsense console, but > > not from the internal clients. In fact my internal clients > can resolve > > through the pfsense box about 10 minutes after they got its > lease from > > pfsense, but after that, its impossible. > > > > I tried flushing cache from the clients, renewing the > leases (which works > > for a while), disabling Traffic Shapping, enabling/disabling the DNS > > Forward, rebooting pfsense, etc. But the only permanent > solution I got, was > > to disable the DNS forward, and assign the external DNS > servers to my > > internal clients via DHCP, to allow them to resolve. > > > > > > > > > > Emanuel Gonzalez > > Guatemala > > > > > > > > > > > > -----Mensaje original----- > > De: Scott Ullrich [mailto:[EMAIL PROTECTED] > > Enviado el: Lunes, 27 de Marzo de 2006 07:26 p.m. > > Para: [email protected] > > Asunto: [pfSense Support] Re: DNS problem with Beta2 > > > > I'm not really sure that I am following you. What do you mean by > > this? What dns server is the client using? Are you overriding the > > dns server? A lot more details are required for us to even begin > > troubleshooting. > > > > On 3/27/06, Stéphane Karges <[EMAIL PROTECTED]> wrote: > >> Hi All, > >> > >> I have a little problem with the DNS, the computer connect > to the DHCP > >> server loose the DNS. The DNS is seen by pfsense but not > by the computer. > >> > >> Any one can help me? > >> > >> Regards, > >> > >> > >> > --------------------------------------------------------------------- > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > >> > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > ____________ Virus checked by G DATA AntiVirusKit --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
