5/28/2010 - Dupe post on Slashdot. 6/15/2010 - Trupe post on Slashdot. 6/15/2010 - AskSlashdot question about whether dupe+1 = trupe or redupe. Links to original post. 6/15/2010 - Slashdot is slashdotted, creating a singular paradox. 5/24/2010 - The end of the world as we know it.
I am fairly certain this does not use any "backdoor" or "special" access numbers in order to function...
If you have access to multiple lines (not including your cell phone), try this: Call your cell phone from one of the lines (be it another cell phone, your desk phone, etc.) As soon as the call starts ringing, place it on hold, and call your cell phone *again* from another line (be it another line on your PBX, another cell phone, etc.) If your cell phone has voice mail service, this second call should connect directly to the voice mail and play your greeting. (While the first call will continue to ring your phone.)
I'm pretty certain this is how the service works. It places one outbound call to the destination cell phone to "tie up" the line, places a second call which *should* immediately go to voice mail, and then drops the first call. Since most mobile phones do not ring immediately after the number is dialed, it is theoretically possible to pull this off if everything is timed correctly, and a little bit of luck plays in your favor. (My experience has been that GSM phones take several seconds to start ringing, and ringback does not start until the handset begins to ring, whereas CDMA will produce ringback immediately to the caller, but the actual handset may take several seconds to start ringing.)
I tried this service against several different phones/providers, sometimes it would cause the phone to ring briefly, and other times it would not.
I also called our PBX at the office with it, and basically saw a call come in on Line 1, followed by another call on Line 2 about half a second later. Which would seem to back up my theory.
is that from the quote, it seems like their scare tactics worked against her... of course, being 12 maybe she doesn't realize the big picture (so I'll give her that much)... still, disturbing.
Seriously, though... eNIC (part of VeriSign) has seriously screwed up one of my DNS server's glue records under one of our.CC domain names! We had to renumber our network (our ISP finally got their own IP space) and I sent the request in through their web control panel. Yes, they did add the new IP address glue record, but they kept the old one! So now our DNS server's glue record points to two IPs -- one which works and one which doesn't. (And we do host a lot of sites, so I'm sure users are starting to feel the lag.)
I've been trying to resolve this situation for TWO MONTHS now, and no one at eNIC seems to have a clue. Ignored most of my mail until I sent a somewhat-nasty one to them and threatened to change registrars, and they claim to have made the fix. (However, ns1.globaldns.com and others have yet to show that up, and it's been almost a week.)
I'll be SO glad when management finally approves the switch to OpenSRS (RSN!) so we can get away from VeriSign... I'm beginning to prefer to deal with GeoTrust for SSL instead (none of that "fax us your business license" garbage... and it's a 10-minute deal.)
My ISP (located in Chattanooga, TN) has an OC-level link to UUNET in Atlanta, and about the same time everyone else mentioned, I started having problems. I could surf most of the net, but did have a few problems.
For one, my personal server is co-located at the office, which uses US LEC (which is multi-homed) for connectivity. I couldn't reach my server from my ISDN connection, but I could SSH to another shell server and then back to mine without a problem. Traceroute died somewhere in Atlanta.
I never was able to get back in, but I got my cablemodem today and it seems to be working fine. Weird part is, I'm linked to a gateway halfway across our state and it's linked to Kansas City through qwest... but it works.
Well, we've had alot of nasty storms this evening (I'm in southeast Tennessee.) I thought that whooshing sound was a tornado outside, although there has been no damage so far...
So I guess what I heard was our founding fathers turning over in their graves at very high speed.
You may want to look into ISDN. Where I'm at, there's no decent broadband. DSL isn't available (well, I had someone tell me the stuff was in, but FastAccess site says its not, and their reps are too lazy to check with the local CO), cable is one-way (not taking new customers) and they are pushing the two-way back more and more... last I heard it's Sep 1st before that's in. Satellite has too much latency (I do Slashdot with Mozilla, and mail/irc over an SSH connection to my co-located box.)
So, I'm using ISDN. It's 128Kbit, not the fastest, but it beats dialup majorly. And here in Tennessee it's about $40/mo. for the ISDN line (mine's $45, cause I get call waiting, forwarding, and all that jazz) plus your ISP charges (mine is $35/mo. for 400 hours.) There is one ISP that offers unlimited ISDN but they seem to have alot of upload problems, and a static IP costs you an extra $15/mo. with them!:/
The ISDN line comes with two channels and phone numbers, so you can be online at 64K and talk on the phone, or do multilink and run 128K using both channels. I have had very few problems with my ISDN, other than the fact it's ended up disconnected by Bell because they mess up our bills..but that's been straightened out now.
I've heard alot of other places, ISDN costs a lot more.. and that alot of places (even here in the US?) bill per minute or hour. I was told down in Huntsville, Alabama (a few hours from here) they get hours per month and then its a charge per hour after that... not that way here in Tennessee. So if you're in Tennessee, it might be a way to go (especially if you don't have any type of broadband available... ISDN is supposed to be avilable everywhere, its basically a regular line in digital mode of sorts.) If you're outside the state, check with your telco, it might be more expensive..
This is something I have been thinking for a while, and is somewhat on-topic for this article, so here I am posting it.
When I started out with computers, it was an Apple IIE with DOS 3.3 or ProDOS (depending on how you booted the machine.) It had 128K of RAM (I said K -- not megs!) A single 5.25" floppy, etc. I then moved up to DOS a few years later (yes, this was a long time ago) and was running DOS 3.3 at that time. I learned DOS, and was one who you'd find tweaking his CONFIG.SYS or fossil drivers for his modem.
Then along came Win3.1, which I tried but didn't really care for. I also tried Linux about that time, liked Linux MUCH better, and that's what I have stuck with since.
That being said, I can give a viewpoint from "the other side of the fence." Usually, the case is Linux users trying to convert Microsoft users to Linux. We all know the viewpoints on that. But, I seriously have had several Windows users try to convert me from Linux over to Windows. Let me share my viewpoint here:
First off, to me Windows is harder to use than Linux. In Linux, I know exactly where I am going, how to get there, and what will happen once I am there. Under Windows, I feel like I am having to wade through links on web pages (that's the best term I can think of right now) to find what I need. It takes me 10 times longer to get a job done on a Windows box than on Linux. Mind you, Windows has a much prettier interface, but Linux is simpler. Sometimes simpler IS better.
But, I'm not just talking about UI here. I am the network admin for an ISP, and I handle both the public network plus our private internal LAN. Our internal LAN appears to be an NT network, although it is served from a Samba server. I've setup a DHCP server, allowing me to give different systems different parameters. It all works beautifuly, except sometimes a few of the Windows machines won't see Samba. (Yet my Linux workstation will.) Another interesting case is that one of our computers has a printer entry in Windows that points to the printer on my system (through Samba.) That is setup as the default printer AND captures the LPT port. Word still prints to the system's local printer, as do DOS applications -- even though the system has been set (and shows) mine over the network as the default! Same system also locks up when you try using its local driver as the default. Changing the default gateway on our DHCP server for that machine, then doing a release and renew seemed to corrupt a few files and the system could no longer get online.
In other words, a Linux user with people trying to convert me to Microsoft, I share the same thing a lot of Microsofters say about Linux: I'm not impressed.
On my workstation, I do a LOT of work, at any given time I'll have a web browser open (either several copies of one, or if I am using Mozilla it's the tabbed interface), along with some terminal windows (Eterm) with SSH to various systems on the network, an MP3 player (got to have music), plus all of KDE's stuff, plus Gnumeric and possibly a few other apps. It handles just fine, and I achieve uptimes of several months (usually killed by extended power outages that the UPS can't handle.) My workstation has *never* crashed in the past year. It does what I need it to, and it does it well. I've tried the same on a Windows box, and it starts to lag once I get my 6-8 apps running. Alot of times it crashes even.
So, as I said, as a Linux user who people are trying to convert to Microsoft: Microsoft doesn't impress me.
Another side note: A friend of mine was a die-hard Windows fan, who seemed to write me off when I said it was unstable. Funny part was, after he started working with a G4 running Mac OS 9 alongside the Windows box, he started complaining profusely (more so than I do) about the stability (or lack thereof) of the Windows box...
I think alot of people just don't realize how bad it is until they've used something better.
Hopefully this doesn't get modded down through the toilet. This is not meant as flamebait, but rather just as me sharing my personal experience. This is what I have encountered over the past several years. When a system's told to use "Printer A" as a default all over the place, and instead it uses "Printer B" -- something's not right. I do not have alot of the problems other users on the network have. The only real difference is that they run Windows and I run Linux. And it's not just with Linux, Mac seems to be more stable even.
All of our production machines run either Linux or BSD, so it's only the workstations that suffer, but still.
And again, this is not flamebait. I am simply sharing my personal experience and my views from seeing both OSes. Alot of people say that Linux does not impress them at all on the desktop -- and I am saying I've seen/tried both and Linux impresses me a LOT more than Microsoft does right now.
Just happen to notice that apparently the same thing was posted over at news.com here.
Didn't see a picture of the new one like they had over at Time -- but then when I clicked the "what to expect" link they told me they appreciated my patience while they worked on making the media stream work with my browser. (Mozilla 0.9.5 on Linux.)
Yes, audio signals travel just fine through the CAT5 cable. At the office, our phone lines and phone system reside in my office. The telco was supposed to move the POTS lines to the server room, so I ran a CAT5 drop between there and my office to bring those lines to the phone system until we moved it. That's been 5 or 6 months ago, and I now use that cable to feed audio from a computer playing MP3s to our phone system for hold music. Works like a charm!
While I don't work in a cubicle, I do have my own office. So it's sort of like a cubicle, just bigger and better. Here is what I have found:
First, as others have mentioned, lighting can work wonders. The overhead lights (florescent) are about the worst thing you can use in an office environment with computers. On the other hand, too little light can be just as bad. I had a floor lamp (one of the ones that opens up toward the ceiling) that had a bulb go out, so I temporarily used a small (and very dim) desk lamp. It was about as bad as having too much light. The floor lamp is much better.
Also, here's a few other tips (some have been mentioned previously) that work for me:
Keep background noise and distractions to an absolute minimum. This will do wonders in improving your train of thought.
If you have the luxury of a DOOR for your office (or cubicle) then CLOSE IT. If you do not have a door, install one.:)
Find some good classical music to listen to as you work. If you have an Internet connection at the office, check out my favorite. (If you don't, check out the local radio stations.)
Most phone systems have a DND (Do Not Disturb) button on the individual phones. It's there for a reason -- use it. If you don't have a phone in your office, be thankful.
On a similar note, if your phone system has direct dialing from outside (either via DNIS or an automated transfer) only give your extension number to close friends/family that you don't mind interrupting your coding. (Make everyone else go through the operator.) If you DND your phone, they will usually get your voice mail if they dial you direct, but still, if you phone doesn't have DND, this is your second line of defense.
Don't keep your E-Mail client open while you work on other things. I have found that doing so creates a temptation to go read your new mail whenever it comes in.
Minimize any other distractions that you may come across. Encourage people to send E-Mail or leave voice mail when they need something, instead of bothering you personally. Every time you stop and help someone, you have to spend time getting back into the swing of things. (I know this may sound a bit mean, but you do have a job you have to get done, right?)
Depending on your network and/or what type of access you have to things, you may be able to install VNC on your machine and then work remotely from home if things get too nasty.
Customize the color configuration of your software. I do as one other person has mentioned here - black backgrounds with white (or gray) text. Most of the time I even turn off the syntax highlighting of my favorite editor when coding.
Anything else that might make you more comfortable and able to be more productive...
Remember this -- you aren't there to look pretty, you are there to do your job. If you need to make modifications to your environment in order to improve your job performance, then it's worth it. I personally wear jeans, a sports shirt, and tennis shoes to work every day. It's a lot easier to work in that than it is to work in dressy clothes.
Also, a lot of what works and doesn't work will depend on the person and possibly the company you are in. Each person has their own needs and what environment works for me may not work for others. YMMV.
Oh, and if your phone system uses standard phones (in other words, no proprietary multiline garbage, your call hold/transfer/conference uses flash hook, and you can use standard Wal-Mart phones on it) then you most likely don't have a DND button. Nortel's Meridian system can have add-on cards to support standard phones, as can many others. Just buy a project box, mount a SPST switch in it, connect one leg of the switch to one leg of a 600 ohm resistor, the other leg of the switch to one side of the phone line, and the remaining leg of the resistor to the other side of the line. When you flip the switch, it puts a 600 ohm load across the line, which is like taking the phone off hook. Instant busy signal.:) (Just make sure it is a standard phone compatible system -- else things can get a bit hairy when you start plugging things in like that.)
Well, not necessarily. You should be able to edit your root zone file (the one that BIND uses as the "." zone) and do something like this:
A.GTLD.BIZ. A 209.173.53.162
B.GTLD.BIZ. A 209.173.57.162
C.GTLD.BIZ. A 209.173.60.65
That way, whenever BIND finds that those are the nameservers for.us - and then goes to resolve those - even though you don't accept ICANN's.biz, you still have glue records for those servers. Of course, that will interfere with any "a.gtld.biz" etc. records that whatever.biz you use has. If that's an issue (and I doubt it is) you can probably do a number like this in the same file:
US. NS A.USDNS.FUZZY.
US. NS B.USDNS.FUZZY.
US. NS C.USDNS.FUZZY.
US. NS D.USDNS.FUZZY.
A.USDNS.FUZZY. A 209.173.53.162
B.USDNS.FUZZY. A 209.173.57.162
C.USDNS.FUZZY. A 209.173.60.65
At that point, you'd interfere with any other existing USDNS.FUZZY out there, but I don't know of any.fuzzy registrars.:) And for most people, the first idea won't be a problem anyway.
As far as I know, those two methods should work.:)
Slashdot Mirror
I encrypt my hard drive, put it in a safe, encrypt the safe as well, bury it in the yard, and finally encrypt the yard for good measure.
No, it's a fool and his money...
And don't call me Shirley!
Don't call me Shirley.
...and haven't since 98. How is this relevant to me?
And nothing of value was lost.
5/28/2010 - Dupe post on Slashdot.
6/15/2010 - Trupe post on Slashdot.
6/15/2010 - AskSlashdot question about whether dupe+1 = trupe or redupe. Links to original post.
6/15/2010 - Slashdot is slashdotted, creating a singular paradox.
5/24/2010 - The end of the world as we know it.
And I feel fine.
... grand closing!
I am fairly certain this does not use any "backdoor" or "special" access numbers in order to function...
If you have access to multiple lines (not including your cell phone), try this: Call your cell phone from one of the lines (be it another cell phone, your desk phone, etc.) As soon as the call starts ringing, place it on hold, and call your cell phone *again* from another line (be it another line on your PBX, another cell phone, etc.) If your cell phone has voice mail service, this second call should connect directly to the voice mail and play your greeting. (While the first call will continue to ring your phone.)
I'm pretty certain this is how the service works. It places one outbound call to the destination cell phone to "tie up" the line, places a second call which *should* immediately go to voice mail, and then drops the first call. Since most mobile phones do not ring immediately after the number is dialed, it is theoretically possible to pull this off if everything is timed correctly, and a little bit of luck plays in your favor. (My experience has been that GSM phones take several seconds to start ringing, and ringback does not start until the handset begins to ring, whereas CDMA will produce ringback immediately to the caller, but the actual handset may take several seconds to start ringing.)
I tried this service against several different phones/providers, sometimes it would cause the phone to ring briefly, and other times it would not.
I also called our PBX at the office with it, and basically saw a call come in on Line 1, followed by another call on Line 2 about half a second later. Which would seem to back up my theory.
Second Post!
yadda yadda biji bubu
umm... Microsoft IIS?
*dons asbestos armor, makes sneak, hide, and secure server checks, hoping that there's no check penalties on asbestos armor*
What kind of establishment is Slashdot, anyway? They seem to have a persistent track record of linking to stories on sites that are down.
is that from the quote, it seems like their scare tactics worked against her... of course, being 12 maybe she doesn't realize the big picture (so I'll give her that much) ... still, disturbing.
fp?
Seriously, though ... eNIC (part of VeriSign) has seriously screwed up one of my DNS server's glue records under one of our .CC domain names! We had to renumber our network (our ISP finally got their own IP space) and I sent the request in through their web control panel. Yes, they did add the new IP address glue record, but they kept the old one! So now our DNS server's glue record points to two IPs -- one which works and one which doesn't. (And we do host a lot of sites, so I'm sure users are starting to feel the lag.)
I've been trying to resolve this situation for TWO MONTHS now, and no one at eNIC seems to have a clue. Ignored most of my mail until I sent a somewhat-nasty one to them and threatened to change registrars, and they claim to have made the fix. (However, ns1.globaldns.com and others have yet to show that up, and it's been almost a week.)
I'll be SO glad when management finally approves the switch to OpenSRS (RSN!) so we can get away from VeriSign... I'm beginning to prefer to deal with GeoTrust for SSL instead (none of that "fax us your business license" garbage ... and it's a 10-minute deal.)
My ISP (located in Chattanooga, TN) has an OC-level link to UUNET in Atlanta, and about the same time everyone else mentioned, I started having problems. I could surf most of the net, but did have a few problems.
... but it works.
For one, my personal server is co-located at the office, which uses US LEC (which is multi-homed) for connectivity. I couldn't reach my server from my ISDN connection, but I could SSH to another shell server and then back to mine without a problem. Traceroute died somewhere in Atlanta.
I never was able to get back in, but I got my cablemodem today and it seems to be working fine. Weird part is, I'm linked to a gateway halfway across our state and it's linked to Kansas City through qwest
So I guess what I heard was our founding fathers turning over in their graves at very high speed.
You may want to look into ISDN. Where I'm at, there's no decent broadband. DSL isn't available (well, I had someone tell me the stuff was in, but FastAccess site says its not, and their reps are too lazy to check with the local CO), cable is one-way (not taking new customers) and they are pushing the two-way back more and more ... last I heard it's Sep 1st before that's in. Satellite has too much latency (I do Slashdot with Mozilla, and mail/irc over an SSH connection to my co-located box.)
:/
... not that way here in Tennessee. So if you're in Tennessee, it might be a way to go (especially if you don't have any type of broadband available ... ISDN is supposed to be avilable everywhere, its basically a regular line in digital mode of sorts.) If you're outside the state, check with your telco, it might be more expensive..
So, I'm using ISDN. It's 128Kbit, not the fastest, but it beats dialup majorly. And here in Tennessee it's about $40/mo. for the ISDN line (mine's $45, cause I get call waiting, forwarding, and all that jazz) plus your ISP charges (mine is $35/mo. for 400 hours.) There is one ISP that offers unlimited ISDN but they seem to have alot of upload problems, and a static IP costs you an extra $15/mo. with them!
The ISDN line comes with two channels and phone numbers, so you can be online at 64K and talk on the phone, or do multilink and run 128K using both channels. I have had very few problems with my ISDN, other than the fact it's ended up disconnected by Bell because they mess up our bills..but that's been straightened out now.
I've heard alot of other places, ISDN costs a lot more.. and that alot of places (even here in the US?) bill per minute or hour. I was told down in Huntsville, Alabama (a few hours from here) they get hours per month and then its a charge per hour after that
This is something I have been thinking for a while, and is somewhat on-topic for this article, so here I am posting it.
When I started out with computers, it was an Apple IIE with DOS 3.3 or ProDOS (depending on how you booted the machine.) It had 128K of RAM (I said K -- not megs!) A single 5.25" floppy, etc. I then moved up to DOS a few years later (yes, this was a long time ago) and was running DOS 3.3 at that time. I learned DOS, and was one who you'd find tweaking his CONFIG.SYS or fossil drivers for his modem.
Then along came Win3.1, which I tried but didn't really care for. I also tried Linux about that time, liked Linux MUCH better, and that's what I have stuck with since.
That being said, I can give a viewpoint from "the other side of the fence." Usually, the case is Linux users trying to convert Microsoft users to Linux. We all know the viewpoints on that. But, I seriously have had several Windows users try to convert me from Linux over to Windows. Let me share my viewpoint here:
First off, to me Windows is harder to use than Linux. In Linux, I know exactly where I am going, how to get there, and what will happen once I am there. Under Windows, I feel like I am having to wade through links on web pages (that's the best term I can think of right now) to find what I need. It takes me 10 times longer to get a job done on a Windows box than on Linux. Mind you, Windows has a much prettier interface, but Linux is simpler. Sometimes simpler IS better.
But, I'm not just talking about UI here. I am the network admin for an ISP, and I handle both the public network plus our private internal LAN. Our internal LAN appears to be an NT network, although it is served from a Samba server. I've setup a DHCP server, allowing me to give different systems different parameters. It all works beautifuly, except sometimes a few of the Windows machines won't see Samba. (Yet my Linux workstation will.) Another interesting case is that one of our computers has a printer entry in Windows that points to the printer on my system (through Samba.) That is setup as the default printer AND captures the LPT port. Word still prints to the system's local printer, as do DOS applications -- even though the system has been set (and shows) mine over the network as the default! Same system also locks up when you try using its local driver as the default. Changing the default gateway on our DHCP server for that machine, then doing a release and renew seemed to corrupt a few files and the system could no longer get online.
In other words, a Linux user with people trying to convert me to Microsoft, I share the same thing a lot of Microsofters say about Linux: I'm not impressed.
On my workstation, I do a LOT of work, at any given time I'll have a web browser open (either several copies of one, or if I am using Mozilla it's the tabbed interface), along with some terminal windows (Eterm) with SSH to various systems on the network, an MP3 player (got to have music), plus all of KDE's stuff, plus Gnumeric and possibly a few other apps. It handles just fine, and I achieve uptimes of several months (usually killed by extended power outages that the UPS can't handle.) My workstation has *never* crashed in the past year. It does what I need it to, and it does it well. I've tried the same on a Windows box, and it starts to lag once I get my 6-8 apps running. Alot of times it crashes even.
So, as I said, as a Linux user who people are trying to convert to Microsoft: Microsoft doesn't impress me.
Another side note: A friend of mine was a die-hard Windows fan, who seemed to write me off when I said it was unstable. Funny part was, after he started working with a G4 running Mac OS 9 alongside the Windows box, he started complaining profusely (more so than I do) about the stability (or lack thereof) of the Windows box...
I think alot of people just don't realize how bad it is until they've used something better.
Hopefully this doesn't get modded down through the toilet. This is not meant as flamebait, but rather just as me sharing my personal experience. This is what I have encountered over the past several years. When a system's told to use "Printer A" as a default all over the place, and instead it uses "Printer B" -- something's not right. I do not have alot of the problems other users on the network have. The only real difference is that they run Windows and I run Linux. And it's not just with Linux, Mac seems to be more stable even.
All of our production machines run either Linux or BSD, so it's only the workstations that suffer, but still.
And again, this is not flamebait. I am simply sharing my personal experience and my views from seeing both OSes. Alot of people say that Linux does not impress them at all on the desktop -- and I am saying I've seen/tried both and Linux impresses me a LOT more than Microsoft does right now.
Didn't see a picture of the new one like they had over at Time -- but then when I clicked the "what to expect" link they told me they appreciated my patience while they worked on making the media stream work with my browser. (Mozilla 0.9.5 on Linux.)
Yes, audio signals travel just fine through the CAT5 cable. At the office, our phone lines and phone system reside in my office. The telco was supposed to move the POTS lines to the server room, so I ran a CAT5 drop between there and my office to bring those lines to the phone system until we moved it. That's been 5 or 6 months ago, and I now use that cable to feed audio from a computer playing MP3s to our phone system for hold music. Works like a charm!
First, as others have mentioned, lighting can work wonders. The overhead lights (florescent) are about the worst thing you can use in an office environment with computers. On the other hand, too little light can be just as bad. I had a floor lamp (one of the ones that opens up toward the ceiling) that had a bulb go out, so I temporarily used a small (and very dim) desk lamp. It was about as bad as having too much light. The floor lamp is much better.
Also, here's a few other tips (some have been mentioned previously) that work for me:
Remember this -- you aren't there to look pretty, you are there to do your job. If you need to make modifications to your environment in order to improve your job performance, then it's worth it. I personally wear jeans, a sports shirt, and tennis shoes to work every day. It's a lot easier to work in that than it is to work in dressy clothes.Also, a lot of what works and doesn't work will depend on the person and possibly the company you are in. Each person has their own needs and what environment works for me may not work for others. YMMV.
Oh, and if your phone system uses standard phones (in other words, no proprietary multiline garbage, your call hold/transfer/conference uses flash hook, and you can use standard Wal-Mart phones on it) then you most likely don't have a DND button. Nortel's Meridian system can have add-on cards to support standard phones, as can many others. Just buy a project box, mount a SPST switch in it, connect one leg of the switch to one leg of a 600 ohm resistor, the other leg of the switch to one side of the phone line, and the remaining leg of the resistor to the other side of the line. When you flip the switch, it puts a 600 ohm load across the line, which is like taking the phone off hook. Instant busy signal. :) (Just make sure it is a standard phone compatible system -- else things can get a bit hairy when you start plugging things in like that.)
Well, not necessarily. You should be able to edit your root zone file (the one that BIND uses as the "." zone) and do something like this:
.us - and then goes to resolve those - even though you don't accept ICANN's .biz, you still have glue records for those servers. Of course, that will interfere with any "a.gtld.biz" etc. records that whatever .biz you use has. If that's an issue (and I doubt it is) you can probably do a number like this in the same file:
.fuzzy registrars. :) And for most people, the first idea won't be a problem anyway.
:)
A.GTLD.BIZ. A 209.173.53.162
B.GTLD.BIZ. A 209.173.57.162
C.GTLD.BIZ. A 209.173.60.65
That way, whenever BIND finds that those are the nameservers for
US. NS A.USDNS.FUZZY.
US. NS B.USDNS.FUZZY.
US. NS C.USDNS.FUZZY.
US. NS D.USDNS.FUZZY.
A.USDNS.FUZZY. A 209.173.53.162
B.USDNS.FUZZY. A 209.173.57.162
C.USDNS.FUZZY. A 209.173.60.65
At that point, you'd interfere with any other existing USDNS.FUZZY out there, but I don't know of any
As far as I know, those two methods should work.