Re: much to my surprise....
On 23/09/2011 01:08, Frank Shute wrote: I had to use them because my static IP all of a sudden became dynamic (crappy ISP). Now it seems to have gone back to static again. There are much better ISPs in the UK -- usually the smaller ones give you much better service. You can get a /28 fixed block as part of a standard package if you shop around. I certainly wouldn't consider running my own DNS server (having done it). It's more trouble than it's worth and is just one more vulnerability/thing to go wrong. You can just use hosts for a small network. Not my experience. Running my own DNS is simple and trouble free, plus it gives me much more scope to play with things like DNSSEC. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: much to my surprise.... [ now trending #OT ]
From: Matt Emmerton m...@gsicomp.on.ca snip but i've been doing this for a while, and until i was away for five days, everything had been going fine for over a month. oh:: one power-out. the UPS saved the server, but everything else needed to be reinitialized. A lesson that I learned many years ago - if you can afford a big UPS for your servers, you can afford a little one for your telco/network equipment. I'm using some PoE kit to power the router remotely down it's LAN cable, that in turn run's from the protected supply from the UPS. Said UPS also powers the main network switch, as well as my own LAN server (f'BSD based, to stay vaguely on toppic!) Plus two other PC's and a NAS device. It'll hold that lot up, for over 20 minutes when the lights go out (the longest unscheduled outage so far.) It's also configured to NOT come back, if it runs down and cuts out. I'll do that manually if needed. (Not so far.) I never did get the BSD port of APCUPSD to work correctly. All works well. Also, easy to do a router Hard restart, without going to the router itself. And if it does all die, it fails safe. Regards. Dave B. ___ 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
Re: much to my surprise.... [ now trending #OT ]
On Thu, Sep 22, 2011 at 10:48:09PM -0400, Matt Emmerton wrote: Date: Thu, 22 Sep 2011 22:48:09 -0400 From: Matt Emmerton m...@gsicomp.on.ca Subject: RE: much to my surprise [ now trending #OT ] To: freebsd-questions@freebsd.org X-Mailer: Microsoft Office Outlook 12.0 *Finally*, i saw that my telco router was displaying INT in red LED's. i didn't know they displayed in any other color but the default green, but after power-cycling, voila! back to green. and now, yes, i can ping freebsd.org. and i'm pretty sure other network things will work too. The Mark I eyeball is an amazing tool. well, cant be sure, but my router is q1000. [?] I recently had a HDSL link provided by my telco go down. I happened to be 2 hours away from the facility at the time. Tech support said the problem was the router because they couldn't get to it, and they just wouldn't believe me that it was up. (I could ping it from the inside via the secondary network connection.) So after I drove to the facility, I noticed that the HDSL modem (which is line-powered from some box on the street) had no lights. Ahah! 28 hours later (sigh) they found a blown circuit breaker somewhere. AH! one thin i have has problems with over the years is cars hitting power poles somewhere and that knocks me off. After last time i put everything thru my highend surge protecter. EVERYTHING was live. i had never [not once in ten years] had the Internet flow go south. mine has been green. i saw that all LED's were lit and never thought to see if the lights were all-green or not! live and learn. so, along with check routers/switches; maybe power cycle i have use named debug, use traceroute. snip but i've been doing this for a while, and until i was away for five days, everything had been going fine for over a month. oh:: one power-out. the UPS saved the server, but everything else needed to be reinitialized. A lesson that I learned many years ago - if you can afford a big UPS for your servers, you can afford a little one for your telco/network equipment. such as? brand, model? would it work to just plug my surge protecto into my larger UPS? ---yes, that wouldn't save me from as glitch in this telco router. but since the APC UPC has its own surge filter, i'm thinking, why not/? gary -- Matt Emmerton ___ 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 -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 8.51a release of Jottings: http://jottings.thought.org ___ 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
Re: much to my surprise....
On Fri, Sep 23, 2011 at 12:14 AM, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: Not my experience. Running my own DNS is simple and trouble free, plus it gives me much more scope to play with things like DNSSEC. I've done it before, but I don't anymore. Partly because it's very hard to provide proper levels of DNS redundancy if you're running your own DNS server. Not that the big players always get it right; I've seen ones that had four authoritative servers that were all on the same subnet. ;) ___ 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
Re: much to my surprise.... [ now trending #OT ]
On Fri, Sep 23, 2011 at 12:27:57PM +0100, Dave wrote:
Date: Fri, 23 Sep 2011 12:27:57 +0100
From: Dave d...@g8kbv.demon.co.uk
Subject: Re: much to my surprise [ now trending #OT ]
To: freebsd-questions@freebsd.org
X-mailer: Pegasus Mail for Windows (4.61)
From: Matt Emmerton m...@gsicomp.on.ca
snip
but i've been doing this for a while, and
until i was away for five days, everything had been going
fine for over a month. oh:: one power-out. the UPS saved
the server, but everything else needed to be reinitialized.
A lesson that I learned many years ago - if you can afford a big UPS
for your servers, you can afford a little one for your telco/network
equipment.
I'm using some PoE kit to power the router remotely down it's LAN cable,
that in turn run's from the protected supply from the UPS. Said UPS also
powers the main network switch, as well as my own LAN server (f'BSD
based, to stay vaguely on toppic!) Plus two other PC's and a NAS device.
It'll hold that lot up, for over 20 minutes when the lights go out (the
longest unscheduled outage so far.) It's also configured to NOT come
back, if it runs down and cuts out. I'll do that manually if needed.
(Not so far.) I never did get the BSD port of APCUPSD to work correctly.
All works well. Also, easy to do a router Hard restart, without going
to the router itself. And if it does all die, it fails safe.
Regards.
Dave B.
see, if i had help at =your= level of expertise, i'd be
fine. 4 days in the icu is still ,messing me up a bit, but
i grok most of what you're saying to matt.
Oh, and for those who suggested i hire somebody instead of
relying on volunteers:: while there is a seattle linux
group, gslug, i know 0.0 people who have a clue about BSD.
i've asked around--the senior techs at the telco have no
clue when i [or someone who can speak] mentioned 'unix'.
i've tried to find some students at the u/washington. zip.
linux, a few people mumble, 'yes, ive heard of that.' but
unix, or berkeley unix , or sun unix. {gawk: Orifice unix,
rather} Zero.
BTW, ive not had time nor savvy to get the APC UPS Port
installed. besides, right now, there in only one 2009 dell
2-cpu on the battery. it has saved state twice. but i
=still= had to get down and crawl around with flashlight in
teeth and power off stuff. -no, no 'poor gary'; that's just
the bare facts.
-g
___
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
--
Gary Kline kl...@thought.org http://www.thought.org Public Service Unix
Journey Toward the Dawn, E-Book: http://www.thought.org
The 8.51a release of Jottings: http://jottings.thought.org
___
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
Re: much to my surprise....
On 23/09/2011 19:19, David Brodbeck wrote: On Fri, Sep 23, 2011 at 12:14 AM, Matthew Seaman m.sea...@infracaninophile.co.uk wrote: Not my experience. Running my own DNS is simple and trouble free, plus it gives me much more scope to play with things like DNSSEC. I've done it before, but I don't anymore. Partly because it's very hard to provide proper levels of DNS redundancy if you're running your own DNS server. Not that the big players always get it right; I've seen ones that had four authoritative servers that were all on the same subnet. ;) Yeah. My ISP will 2ary my zones onto their much larger and diversely situated servers at no extra cost. That's pretty handy. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matt...@infracaninophile.co.uk Kent, CT11 9PW signature.asc Description: OpenPGP digital signature
Re: much to my surprise....
From owner-freebsd-questi...@freebsd.org Thu Sep 22 14:30:49 2011 Date: Thu, 22 Sep 2011 12:30:54 -0700 From: Gary Kline kl...@thought.org To: FreeBSD Mailing List freebsd-questions@freebsd.org Cc: Subject: much to my surprise guys, well, after a forced, unexpected, and emergency 5 days away, i got back to my desk and could not ping. while mail seemed to be working, and my *local* ping worked---I could ping around from my freebsd server to my other computers--i spent 3+ hours trying to ping various sites. Zero. i tried everything i could think of. NOTHING worked. i tried the -d -f -f to named and on and on and on. nothing. *Finally*, i saw that my telco router was displaying INT in red LED's. i didn't know they displayed in any other color but the default green, but after power-cycling, voila! back to green. and now, yes, i can ping freebsd.org. and i'm pretty sure other network things will work too. from any/all sysadmin types or others:: i would like tricks, tips, insights--whatever--about named and whatever else. i thought i had collected many. nope.i've got bind 9.8 installed and it was working fine until my recent 'vacation.' Other than checking one's routers (hub/switch), and other hardware (including server, computers, cables, etc) does anybody have a checklist of what to do to diagnose this? are there any other utilities i can try besides ping and named -d 3 -f -g? other network utilities with a debug flag? i'm running 7.3 on a dell 530. tia for any insights, You should _really_ consider hiring a professional to maintain your systems. Diagnosing _this_ problem should have taken no more than about 30 *seconds*. If you can't get somewhere 'by name', you try to get there 'by address'. If 'by address' works and 'by name' doesn't, *that* is the indication of a DNS problem. If you can't get there 'by address', it is *NOT* a DNS problem, and you start looking for a 'connectivity' problem. The *BASIC* tools for that start with 'traceroute'. Which would have *immediately* (well, within abut ten seconds :) indicated exactly _where_ the problem was. Those who don't understand these kind dof things are too dangerous to be trusted with the superuser password. Bluntly, not only do you not know the things you need to know to manage a (even 'personal') network, you DON'T KNOW _what_ you don't know, and until you *do* learn the basics, you'll save youself a *LOT* of hair- tearing if you hire someone to solve the problems for you. ___ 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
Re: much to my surprise....
On Thu, Sep 22, 2011 at 03:14:50PM -0500, Robert Bonomi wrote: From owner-freebsd-questi...@freebsd.org Thu Sep 22 14:30:49 2011 Date: Thu, 22 Sep 2011 12:30:54 -0700 From: Gary Kline kl...@thought.org To: FreeBSD Mailing List freebsd-questions@freebsd.org Cc: Subject: much to my surprise guys, well, after a forced, unexpected, and emergency 5 days away, i got back to my desk and could not ping. while mail seemed to be working, and my *local* ping worked---I could ping around from my freebsd server to my other computers--i spent 3+ hours trying to ping various sites. Zero. i tried everything i could think of. NOTHING worked. i tried the -d -f -f to named and on and on and on. nothing. *Finally*, i saw that my telco router was displaying INT in red LED's. i didn't know they displayed in any other color but the default green, but after power-cycling, voila! back to green. and now, yes, i can ping freebsd.org. and i'm pretty sure other network things will work too. from any/all sysadmin types or others:: i would like tricks, tips, insights--whatever--about named and whatever else. i thought i had collected many. nope.i've got bind 9.8 installed and it was working fine until my recent 'vacation.' Other than checking one's routers (hub/switch), and other hardware (including server, computers, cables, etc) does anybody have a checklist of what to do to diagnose this? are there any other utilities i can try besides ping and named -d 3 -f -g? other network utilities with a debug flag? i'm running 7.3 on a dell 530. tia for any insights, You should _really_ consider hiring a professional to maintain your systems. Diagnosing _this_ problem should have taken no more than about 30 *seconds*. If you can't get somewhere 'by name', you try to get there 'by address'. If 'by address' works and 'by name' doesn't, *that* is the indication of a DNS problem. If you can't get there 'by address', it is *NOT* a DNS problem, and you start looking for a 'connectivity' problem. The *BASIC* tools for that start with 'traceroute'. Which would have *immediately* (well, within abut ten seconds :) indicated exactly _where_ the problem was. Those who don't understand these kind dof things are too dangerous to be trusted with the superuser password. Bluntly, not only do you not know the things you need to know to manage a (even 'personal') network, you DON'T KNOW _what_ you don't know, and until you *do* learn the basics, you'll save youself a *LOT* of hair- tearing if you hire someone to solve the problems for you. While your information may be correct and useful, your self-righteous arrogant diatribe is not helpful or appropriate on this list. jerry ___ 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 ___ 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
Re: much to my surprise....
On Sep 22, 2011, at 3:14 PM, Robert Bonomi wrote: From owner-freebsd-questi...@freebsd.org Thu Sep 22 14:30:49 2011 Date: Thu, 22 Sep 2011 12:30:54 -0700 From: Gary Kline kl...@thought.org To: FreeBSD Mailing List freebsd-questions@freebsd.org Cc: Subject: much to my surprise guys, well, after a forced, unexpected, and emergency 5 days away, i got back to my desk and could not ping. while mail seemed to be working, and my *local* ping worked---I could ping around from my freebsd server to my other computers--i spent 3+ hours trying to ping various sites. Zero. i tried everything i could think of. NOTHING worked. i tried the -d -f -f to named and on and on and on. nothing. *Finally*, i saw that my telco router was displaying INT in red LED's. i didn't know they displayed in any other color but the default green, but after power-cycling, voila! back to green. and now, yes, i can ping freebsd.org. and i'm pretty sure other network things will work too. from any/all sysadmin types or others:: i would like tricks, tips, insights--whatever--about named and whatever else. i thought i had collected many. nope.i've got bind 9.8 installed and it was working fine until my recent 'vacation.' Other than checking one's routers (hub/switch), and other hardware (including server, computers, cables, etc) does anybody have a checklist of what to do to diagnose this? are there any other utilities i can try besides ping and named -d 3 -f -g? other network utilities with a debug flag? i'm running 7.3 on a dell 530. tia for any insights, You should _really_ consider hiring a professional to maintain your systems. Diagnosing _this_ problem should have taken no more than about 30 *seconds*. If you can't get somewhere 'by name', you try to get there 'by address'. If 'by address' works and 'by name' doesn't, *that* is the indication of a DNS problem. If you can't get there 'by address', it is *NOT* a DNS problem, and you start looking for a 'connectivity' problem. The *BASIC* tools for that start with 'traceroute'. Which would have *immediately* (well, within abut ten seconds :) indicated exactly _where_ the problem was. Those who don't understand these kind dof things are too dangerous to be trusted with the superuser password. Bluntly, not only do you not know the things you need to know to manage a (even 'personal') network, you DON'T KNOW _what_ you don't know, and until you *do* learn the basics, you'll save youself a *LOT* of hair- tearing if you hire someone to solve the problems for you. I whole-heartedly agree with Robert's points. I host in my apartment... but I have more than a decade's experience maintaining networks and systems and, while the occasional issue stumps me, I'm pretty good at getting to the root of issues in minutes vs hours. Yes, I was once a... for lack of a better term... moron on these things and I relied heavily on the tech who pushed me (gently) towards ƒBSD from RHL and I am gracious every day for that nudge. Experience is the best way to pick up the quick list of things to check on if there's a problem on your connectivity... but there's one thing I *must* stress: NEVER EVER EVER run your own DNS service. It's too much of a PITA. When I quit doing my own DNS my issues revolving around that ended. I use DynDNS to run my primary domain and all the others run through GoDaddy's free DNS manager. This is because I use the primary domain's hostname as my MX record on all the others. While GD's DNS is functional, it's also cumbersome, too cumbersome to update on a semi-regular basis. I highly suggest that you do the same. $20/year for DynDNS' full domain service is worth the price. My two bits (and a nibble). -- Ryan___ 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
Re: much to my surprise....
On Thu, Sep 22, 2011 at 04:28:50PM -0500, Ryan Coleman wrote: On Sep 22, 2011, at 3:14 PM, Robert Bonomi wrote: From owner-freebsd-questi...@freebsd.org Thu Sep 22 14:30:49 2011 Date: Thu, 22 Sep 2011 12:30:54 -0700 From: Gary Kline kl...@thought.org To: FreeBSD Mailing List freebsd-questions@freebsd.org Cc: Subject: much to my surprise guys, well, after a forced, unexpected, and emergency 5 days away, i got back to my desk and could not ping. while mail seemed to be working, and my *local* ping worked---I could ping around from my freebsd server to my other computers--i spent 3+ hours trying to ping various sites. Zero. i tried everything i could think of. NOTHING worked. i tried the -d -f -f to named and on and on and on. nothing. *Finally*, i saw that my telco router was displaying INT in red LED's. i didn't know they displayed in any other color but the default green, but after power-cycling, voila! back to green. and now, yes, i can ping freebsd.org. and i'm pretty sure other network things will work too. from any/all sysadmin types or others:: i would like tricks, tips, insights--whatever--about named and whatever else. i thought i had collected many. nope.i've got bind 9.8 installed and it was working fine until my recent 'vacation.' Other than checking one's routers (hub/switch), and other hardware (including server, computers, cables, etc) does anybody have a checklist of what to do to diagnose this? are there any other utilities i can try besides ping and named -d 3 -f -g? other network utilities with a debug flag? i'm running 7.3 on a dell 530. tia for any insights, You should _really_ consider hiring a professional to maintain your systems. Diagnosing _this_ problem should have taken no more than about 30 *seconds*. If you can't get somewhere 'by name', you try to get there 'by address'. If 'by address' works and 'by name' doesn't, *that* is the indication of a DNS problem. If you can't get there 'by address', it is *NOT* a DNS problem, and you start looking for a 'connectivity' problem. The *BASIC* tools for that start with 'traceroute'. Which would have *immediately* (well, within abut ten seconds :) indicated exactly _where_ the problem was. Those who don't understand these kind dof things are too dangerous to be trusted with the superuser password. Bluntly, not only do you not know the things you need to know to manage a (even 'personal') network, you DON'T KNOW _what_ you don't know, and until you *do* learn the basics, you'll save youself a *LOT* of hair- tearing if you hire someone to solve the problems for you. I whole-heartedly agree with Robert's points. I host in my apartment... but I have more than a decade's experience maintaining networks and systems and, while the occasional issue stumps me, I'm pretty good at getting to the root of issues in minutes vs hours. Yes, I was once a... for lack of a better term... moron on these things and I relied heavily on the tech who pushed me (gently) towards ?BSD from RHL and I am gracious every day for that nudge. Experience is the best way to pick up the quick list of things to check on if there's a problem on your connectivity... but there's one thing I *must* stress: NEVER EVER EVER run your own DNS service. It's too much of a PITA. When I quit doing my own DNS my issues revolving around that ended. I use DynDNS to run my primary domain and all the others run through GoDaddy's free DNS manager. This is because I use the primary domain's hostname as my MX record on all the others. While GD's DNS is functional, it's also cumbersome, too cumbersome to update on a semi-regular basis. I highly suggest that you do the same. $20/year for DynDNS' full domain service is worth the price. My two bits (and a nibble). -- Ryan___ It's $30/year for DynDNS where I am (UK). I had to use them because my static IP all of a sudden became dynamic (crappy ISP). Now it seems to have gone back to static again. I certainly wouldn't consider running my own DNS server (having done it). It's more trouble than it's worth and is just one more vulnerability/thing to go wrong. You can just use hosts for a small network. Regards, -- Frank Contact info: http://www.shute.org.uk/misc/contact.html pgpl6pQtrTLm3.pgp Description: PGP signature
Re: much to my surprise....
On Thu, Sep 22, 2011 at 04:28:50PM -0500, Ryan Coleman wrote: Date: Thu, 22 Sep 2011 16:28:50 -0500 From: Ryan Coleman edi...@d3photography.com Subject: Re: much to my surprise To: Robert Bonomi bon...@mail.r-bonomi.com Cc: freebsd-questions@freebsd.org, kl...@thought.org X-Mailer: Apple Mail (2.1244.3) On Sep 22, 2011, at 3:14 PM, Robert Bonomi wrote: From owner-freebsd-questi...@freebsd.org Thu Sep 22 14:30:49 2011 Date: Thu, 22 Sep 2011 12:30:54 -0700 From: Gary Kline kl...@thought.org To: FreeBSD Mailing List freebsd-questions@freebsd.org Cc: Subject: much to my surprise guys, well, after a forced, unexpected, and emergency 5 days away, i got back to my desk and could not ping. while mail seemed to be working, and my *local* ping worked---I could ping around from my freebsd server to my other computers--i spent 3+ hours trying to ping various sites. Zero. i tried everything i could think of. NOTHING worked. i tried the -d -f -f to named and on and on and on. nothing. *Finally*, i saw that my telco router was displaying INT in red LED's. i didn't know they displayed in any other color but the default green, but after power-cycling, voila! back to green. and now, yes, i can ping freebsd.org. and i'm pretty sure other network things will work too. from any/all sysadmin types or others:: i would like tricks, tips, insights--whatever--about named and whatever else. i thought i had collected many. nope.i've got bind 9.8 installed and it was working fine until my recent 'vacation.' Other than checking one's routers (hub/switch), and other hardware (including server, computers, cables, etc) does anybody have a checklist of what to do to diagnose this? are there any other utilities i can try besides ping and named -d 3 -f -g? other network utilities with a debug flag? i'm running 7.3 on a dell 530. tia for any insights, You should _really_ consider hiring a professional to maintain your systems. Diagnosing _this_ problem should have taken no more than about 30 *seconds*. If you can't get somewhere 'by name', you try to get there 'by address'. If 'by address' works and 'by name' doesn't, *that* is the indication of a DNS problem. If you can't get there 'by address', it is *NOT* a DNS problem, and you start looking for a 'connectivity' problem. points all well taken, robert, thanks. i was ready to fire off a few shots of my colt bisley 454, then took two deep breaths and soldiered on. [note that at least one other fellow has suggested that i just hire somebody to maintain my connectivity.] but i've been doing this for a while, and until i was away for five days, everything had been going fine for over a month. oh:: one power-out. the UPS saved the server, but everything else needed to be reinitialized. The *BASIC* tools for that start with 'traceroute'. Which would have *immediately* (well, within abut ten seconds :) indicated exactly _where_ the problem was. would traceroute have told me to check the modem/router? Those who don't understand these kind dof things are too dangerous to be trusted with the superuser password. Bluntly, not only do you not know the things you need to know to manage a (even 'personal') network, you DON'T KNOW _what_ you don't know, and until you *do* learn the basics, you'll save youself a *LOT* of hair- tearing if you hire someone to solve the problems for you. I whole-heartedly agree with Robert's points. I host in my apartment... but I have more than a decade's experience maintaining networks and systems and, while the occasional issue stumps me, I'm pretty good at getting to the root of issues in minutes vs hours. would you believe: i'm slow at typing, ? Yes, I was once a... for lack of a better term... moron on these things and I relied heavily on the tech who pushed me (gently) towards ?BSD from RHL and I am gracious every day for that nudge. i've used REAL UNIX [[$1100] for SVR4; and before than VAT, a 286 version of SVR2; then chose FreeBSD with 2.0.5. things started out as a dialup BBS and evolved since july '86 system administration is something i do reluctantly. adding system calls to the tera kernel plus other kernel work on the the hardware version of a 128-stream CPU seemed infinitely easier than this Experience is the best way to pick up the quick list of things to check on if there's a problem on your connectivity... but there's one thing I *must* stress: NEVER EVER EVER run your own DNS service. It's too much of a PITA. When I quit doing my own DNS my issues revolving around that ended. i dont want to sound like a goodie two-shoes, but i've been running a web site for a builder
Re: much to my surprise....
--As of September 22, 2011 6:31:19 PM -0700, Gary Kline is alleged to have said: i'm to the point where letting somebody else handle the dns-and-outward side sounds better by the day. i'v got more question if you care to answer them. i've been using gkg.net for a few years--8 or 9 anyway. but if switching to dyndns saves a lot of my flubs, hey. --As for the rest, it is mine. Just as an alternative vote: I've been using ZoneEdit for years. It's free if you are just running a couple of small sites. (Although I haven't tried their dynamic DNS features. I just pay the ISP for a static.) Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ 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
Re: much to my surprise....
On Thu, Sep 22, 2011 at 09:43:00PM -0400, Daniel Staal wrote: Date: Thu, 22 Sep 2011 21:43:00 -0400 From: Daniel Staal dst...@usa.net Subject: Re: much to my surprise To: Gary Kline kl...@thought.org, freebsd-questions@freebsd.org X-Mailer: Mulberry/4.0.8 (Mac OS X) --As of September 22, 2011 6:31:19 PM -0700, Gary Kline is alleged to have said: i'm to the point where letting somebody else handle the dns-and-outward side sounds better by the day. i'v got more question if you care to answer them. i've been using gkg.net for a few years--8 or 9 anyway. but if switching to dyndns saves a lot of my flubs, hey. --As for the rest, it is mine. Just as an alternative vote: I've been using ZoneEdit for years. It's free if you are just running a couple of small sites. (Although I haven't tried their dynamic DNS features. I just pay the ISP for a static.) i've got 5 static IP's and several / many virtual domains. that's one reason i've hesitated. i'd guess maybe 3-6 megs of stuff. mostly text. www.thought.org is home; another directory hosts jottings.thought.org; another is transfinite.thougght.org; and philosophy.thought.org. i want to add a bbs or forum like phpbb3, IIRC. If i find some reasonable hosting place, how will be be able to mess with that. last time, i remember getting that going pretty tough. i'd like to have forums available on at least two of my virtual or subdomain websites. having it HERE, no problem ... hm. there was recent discussion about mysql and openoffice and all that stuff. i was having trouble with mysql . that's a whole nother thread. Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- -- Gary Kline kl...@thought.org http://www.thought.org Public Service Unix Journey Toward the Dawn, E-Book: http://www.thought.org The 8.51a release of Jottings: http://jottings.thought.org ___ 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
RE: much to my surprise.... [ now trending #OT ]
*Finally*, i saw that my telco router was displaying INT in red LED's. i didn't know they displayed in any other color but the default green, but after power-cycling, voila! back to green. and now, yes, i can ping freebsd.org. and i'm pretty sure other network things will work too. The Mark I eyeball is an amazing tool. I recently had a HDSL link provided by my telco go down. I happened to be 2 hours away from the facility at the time. Tech support said the problem was the router because they couldn't get to it, and they just wouldn't believe me that it was up. (I could ping it from the inside via the secondary network connection.) So after I drove to the facility, I noticed that the HDSL modem (which is line-powered from some box on the street) had no lights. Ahah! 28 hours later (sigh) they found a blown circuit breaker somewhere. snip but i've been doing this for a while, and until i was away for five days, everything had been going fine for over a month. oh:: one power-out. the UPS saved the server, but everything else needed to be reinitialized. A lesson that I learned many years ago - if you can afford a big UPS for your servers, you can afford a little one for your telco/network equipment. -- Matt Emmerton ___ 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
