Tim Dunphy wrote:
hey listers!! sorry for all the trouble.. just as an FYI it turned out
to NOT be a DNS issue at all!!!
it was a routing issue...
this command apparently did the trick...
[r...@lbsd2:/usr/home/bluethundr]#/etc/rc.d/routing restart
add net default: gateway 192.168.1.1
thanks for the suggestion! but the other machines on this network do
not use the FreeBSD machine as a router. They merely reference it as
their first choice of DNS servers. So as of now networking is good to
go for all machines.
best!!
On Thu, Oct 28, 2010 at 2:32 AM, Michael Powell
hey listers!! sorry for all the trouble.. just as an FYI it turned out
to NOT be a DNS issue at all!!!
it was a routing issue...
this command apparently did the trick...
[r...@lbsd2:/usr/home/bluethundr]#/etc/rc.d/routing restart
add net default: gateway 192.168.1.1
guys,
thanks for the input. busy couple of days sorry for not following up sooner.
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:
[r...@lbsd2:/usr/home/bluethundr]#cat
Are the forwarders in your named.conf file OK?
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
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 is the current state of affairs:
[r...@lbsd2:/usr/home/bluethundr]#host bsd2
bsd2 has address 199.101.28.20
Host bsd2 not found: 3(NXDOMAIN)
[r...@lbsd2:/usr/home/bluethundr]#ping yahoo.com
PING yahoo.com (69.147.125.65): 56 data bytes
ping: sendto: No route to host
ping: sendto: No route to
Thanks guys! But to give more background the host in question IS
networking, at this point I can ssh into and out of it.. I just can't
resolve externally.
[r...@lbsd2:/usr/ports]#ifconfig
bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500
Tim Dunphy wrote:
Thanks guys! But to give more background the host in question IS
networking, at this point I can ssh into and out of it.. I just can't
resolve externally.
[r...@lbsd2:/usr/ports]#ifconfig
bge0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST metric 0 mtu 1500
hello,
I accidentally deleted my ports tree thinking that cvsup was already
installed. it wasn't. :(
I seem to be having a little trouble resolving external hosts tho my
trusty named server on this host is working fine to resolve the local
network. I need to reinstall my ports with sysinstall
Tim Dunphy wrote:
hello,
I accidentally deleted my ports tree thinking that cvsup was already
installed. it wasn't. :(
csup is cvsup rewritten with C and exists in the base system. You no longer
need to install cvsup, just use csup.
I seem to be having a little trouble resolving
On Sun, 17 Oct 2010 23:44:42 -0400
Tim Dunphy bluethu...@gmail.com wrote:
I accidentally deleted my ports tree thinking that cvsup was already
installed. it wasn't. :(
csup is part of the system, no need to use cvsup from the ports any longer.
I seem to be having a little trouble resolving
12 matches
Mail list logo
