>From a workstation in NET1 administra...@d9q87t01:~$ telnet 192.168.1.75 53 Trying 192.168.1.75... Connected to 192.168.1.75. Escape character is '^]'. Connection closed by foreign host.
Jose On Thu, 2010-02-18 at 18:23 +0100, Remko Lodder wrote: > On Feb 18, 2010, at 6:18 PM, Jose Torres wrote: > > > I am not sure if this is the way to set the DNS binding. > > > > I went to the DNS Server configuration page and set the Binding IP > > address field as "127.0.0.1, 192.1687.1.75" and clicked save. > > > > Then I restarted the service. > > > > If this is the way, then the DNS Server is listening on both addresses > > now. > > > > But Windows DNS still does not transfer/copy/retrieve successfully the > > pfSense DNS zone. > > > > Jose > > Can you connect to 192.168.1.75 on port 53 at all? (I am sure you wrote > a typo there). I didn't setup zonetransfers yet, so possibly you are right but > lets get the details right first :-) > > Remko > > > > > On Thu, 2010-02-18 at 18:02 +0100, Remko Lodder wrote: > >> On Feb 18, 2010, at 5:26 PM, Jose Torres wrote: > >> > >>> Lets try to clarify. > >>> > >>> Windows Workstations (Domain area.com) > >>> + > >>> + (Network 192.168.0.0/24 - NET1) > >>> + > >>> Windows 2000 DNS Server > >>> (Not BIND, Not TinyDNS, Windows DNS) > >>> + > >>> + (Network 192.168.0.0/24 - NET1) > >>> + > >>> pfSense DNS Server (TinyDNS package) (Binded to 127.0.0.1) > >>> + > >>> + (Network 192.168.1.0/24 - NET2) > >>> + > >>> Windows Workstations (sub.area.com) > >>> > >>> Already can ping machine.area.com from machine.sub.area.com > >>> Already can ping www.google.com (Internet) from machine.sub.area.com > >>> > >>> Need to resolve the IPs of network NET2 from NET1 > >>> Need to ping machine.sub.area.com from machine.area.com > >>> > >>> To do that I want to have the Windows DNS as slave/copy of the pfSense > >>> DNS. > >>> > >>> Jose > >> > >> You can never transfer zone's if you are listening on 127.0.0.1, neither > >> can you do resolving for your > >> clients if you only listen on the localhost.. (127.0.0.1). > >> > >>> > >>> On Thu, 2010-02-18 at 16:51 +0100, Remko Lodder wrote: > >>>> > >>>> On Feb 18, 2010, at 3:40 PM, Jose Torres wrote: > >>>> > >>>>> While searching the web I found two threads. > >>>>> > >>>>> One thread was in a pfSense bug tracker system > >>>>> http://redmine.pfsense.org/issues/show/119 > >>>>> > >>>>> And the other was on the pfSense Forum > >>>>> http://forum.pfsense.org/index.php/topic,6957.0.html > >>>>> > >>>>> > >>>>> The Bug tracker did not said to which version of pfSense or TinyDNS > >>>>> package version this bug applied. It includes an attachment, which is > >>>>> not clear if it is a patch for the bug and if it is a patch how to > >>>>> implement it. > >>>>> > >>>>> The forum thread just say to execute the afxrdns-conf but does not > >>>>> explain how to do it in pfSense. This program has some parameters that > >>>>> are specific for the system being run. And what else has to be done > >>>>> after executing this program, in detail specific for the pfSense system. > >>>>> > >>>>> By the way my pfSense version is 1.2.3-RELEASE and dns-server version > >>>>> 1.0.6.4 > >>>>> > >>>>> > >>>>> Please Help > >>>>> > >>>>> Jose > >>>>> > >>>>> > >>>> > >>>> > >>>> > >>>> Ofcourse when the machine is being tied to the localhost, it is never > >>>> reachable and cannot transfer anything at all. > >>>> > >>>> Your information is not clear enough imo to get you going. From where do > >>>> you want to transfer files? What files > >>>> are you trying to transfer? Under bind you need to specify the zone > >>>> > >>>> zone "blaat.com" { > >>>> allow-transfer { external_ip; }; > >>>> type slave; > >>>> file "slaves/blaat.com.zone"; > >>>> }; > >>>> > >>>> And things like that, you need to tell us a bit more about what you are > >>>> trying to do. From the redmine ticket it is something > >>>> that the submitter uses, it's not a patch, neither is it something on > >>>> how to implement it. It's something that works for the > >>>> submitter, but might not work for you. > >>>> > >>>> Hope this clarifies at least something... > >>>> > >>>> Cheers, > >>>> > >>>> Remko > >>>> > >>>> p.s. Yes you have written something about your "requirements" but I find > >>>> them a bit vague.. > >>>> > >>> > >>> > >>> --------------------------------------------------------------------- > >>> To unsubscribe, e-mail: [email protected] > >>> For additional commands, e-mail: [email protected] > >>> > >>> Commercial support available - https://portal.pfsense.org > >>> > >> > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > Commercial support available - https://portal.pfsense.org > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] Commercial support available - https://portal.pfsense.org
