Date: Fri, 22 Oct 2010 23:01:59 -0400 From: Tim Dunphy <bluethundr@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: download cvsup? Message-ID: <AANLkTin7YE_Lcxbv8eveg2GHodF4wmVmrCRTBLRPK5MX@mail.gmail.com> In-Reply-To: <i9mcs1$peo$1@dough.gmane.org> References: <AANLkTimXPh2CrF8W1Xp0UaaQ8U=bnkq-CPY01k%2Bu_GML@mail.gmail.com> <i9gn4g$mnn$1@dough.gmane.org> <AANLkTi=zXuYMtOWeetLoDKY6-quHqSyWxjNmGjJz6T0i@mail.gmail.com> <i9j86o$ijr$1@dough.gmane.org> <AANLkTinhWrYf0Ffdx1Pyi%2BYUt7tU9JfmvOu9Q50zPb8q@mail.gmail.com> <da6a408e-26af-475f-90e8-289550c300b7@email.android.com> <i9mcs1$peo$1@dough.gmane.org>
next in thread | previous in thread | raw e-mail | index | archive | help
guys,
thanks for the input. busy couple of days sorry for not following up soone=
r.
at any rate, I tried many suggestions.
Here is the current state of things:
This is a working resolv.conf on the rest of the network which are
CentOS machines:
[root@LBSD2:/usr/home/bluethundr]#cat /etc/resolv.conf
domain summitnjhome.com
nameserver 192.168.1.44
nameserver 71.250.0.12
nameserver 4.2.2.2
I rsync'ed this file to the bsd server from a CentOS machine and this
is what happens when you try to resolve internally, then externally
(also tried editing it manually of course):
[root@LBSD2:/usr/home/bluethundr]#host bsd2
bsd2.summitnjhome.com has address 192.168.1.44
[root@LBSD2:/usr/home/bluethundr]#host sum1
sum1.summitnjhome.com is an alias for lCent01.summitnjhome.com.
lCent01.summitnjhome.com has address 192.168.1.42
[root@LBSD2:/usr/home/bluethundr]#ping yahoo.com
ping: cannot resolve yahoo.com: Host name lookup failure
this is how my named.conf looks:
options {
// Relative to the chroot directory, if any
directory "/etc/namedb";
pid-file "/var/run/named/pid";
dump-file "/var/dump/named_dump.db";
statistics-file "/var/stats/named.stats";
Also i notice it's
[root@LBSD2:/usr/home/bluethundr]#ping yahoo.com
ping: cannot resolve yahoo.com: Host name lookup failure
with forwarders commented out
and
[root@LBSD2:/usr/home/bluethundr]#ping yahoo.com
PING yahoo.com (72.30.2.43): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to host
with forwarders enabled:
forwarders {
71.250.0.12; 4.2.2.2;
};
or even just
forwarders {
192.168.1.1;
};
enabled.. I'm still quite puzzled.. I'm hoping that this problem won't
require me to backup my most important configurations (DNS, LDAP,
Apache) and reinstall.. cuz that's uhmmm.. cheating! ;) not to mention
a pain in the firggin' arse... guh
// If named is being used only as a local resolver, this is a safe default.
// For named to be accessible to the network, comment this option, specify
// the proper IP address, or delete this option.
#listen-on { 127.0.0.1; };
listen-on { 127.0.0.1; 192.168.1.44; };
allow-recursion {127.0.0.1; 192.168.1.0/24;};
On Wed, Oct 20, 2010 at 5:38 AM, Michael Powell <nightrecon@hotmail.com> wr=
ote:
> Dick Hoogendijk wrote:
>
>> Are the forwarders in your named.conf file OK?
>
> That was the next thing I was about to suggest. His FIOS router should be
> running DNS itself by default, with it pointing to Verizon's name servers=
.
> So he could try using 192.168.1.1 in his named.conf forwarders directive.
> This would just recurse out to Verizon's name servers and should get a ba=
sic
> external resolution going, provided he has not altered the default router
> setup.
>
> Example from mine: (don't just cut and paste but adjust as required)
>
> options {
> =A0 =A0 =A0 =A0directory =A0 =A0 =A0 "/etc/namedb";
> =A0 =A0 =A0 =A0pid-file =A0 =A0 =A0 =A0"/var/run/named/pid";
> =A0 =A0 =A0 =A0dump-file =A0 =A0 =A0 "/var/dump/named_dump.db";
> =A0 =A0 =A0 =A0statistics-file "/var/stats/named.stats";
>
> =A0 =A0 =A0 =A0listen-on =A0 =A0 =A0 { 127.0.0.1; 192.168.10.1; };
>
> =A0 =A0 =A0 =A0allow-recursion {127.0.0.1; 192.168.10.0/24;};
>
> // If you've got a DNS server around at your upstream provider, enter
> // its IP address here, and enable the line below. =A0This will make you
> // benefit from its cache, thus reduce overall DNS traffic in the Interne=
t.
>
> =A0 =A0 =A0 =A0forwarders {
> =A0 =A0 =A0 =A0 208.67.222.222; 208.67.220.220; 192.168.1.1;
> =A0 =A0 =A0 =A0};
>
>
> // =A0 =A0 =A0query-source address * port 53;
> };
>
> -------/ Below are snipped out zone file directives for my local stuff =
=A0/---
>
> The first two IP addresses in my forwarders clause are for OpenDNS. You
> could delete them so as to only have 192.168.1.1 and your FreeBSD's DNS
> server will then forward requests to your FIOS router which will then
> request from Verizon. Use of the listen-on and allow-recursion is not
> necessary, but if you decide to utilize make sure they reflect values whi=
ch
> apply to your situation. Do rndc reload or reboot to take effect.
>
> I think he has some other issues pending as well, but one thing at a time=
.
> :-)
>
> -Mike
>
>
>
> _______________________________________________
> freebsd-questions@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o=
rg"
>
--=20
Here's my RSA Public key:
gpg --keyserver pgp.mit.edu --recv-keys 5A4873A9
Share and enjoy!!
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTin7YE_Lcxbv8eveg2GHodF4wmVmrCRTBLRPK5MX>