Re: On the control of the Internet.
On 6/13/2010 14:59, Joe Greco wrote:
How about the case where the master zone file has be amputated and the secondaries can no longer get updates?
Mea culpa. That was suppose to say "How about the case where the master zone file has beEN amputated and the secondaries can no longer get updates? My apologies. -- Somebody should have said: A democracy is two wolves and a lamb voting on what to have for dinner. Freedom under a constitutional republic is a well armed lamb contesting the vote. Requiescas in pace o email Ex turpi causa non oritur actio Eppure si rinfresca ICBM Targeting Information: http://tinyurl.com/4sqczs http://tinyurl.com/7tp8ml
On 6/13/2010 14:59, Joe Greco wrote:
How about the case where the master zone file has be amputated and the secondaries can no longer get updates?
Mea culpa.
That was suppose to say "How about the case where the master zone file has beEN amputated and the secondaries can no longer get updates?
My apologies.
Do you actually mean that the master zone file has been modified by the government? If so, how is that intertwined with secondaries no longer being able to get updates? Work with me, here, I'm trying to understand what you're saying. If the government has corrupted your master, and they actually want those changes pushed out, one would expect that: 1) your master is not public to begin with (just good design, that, ..) 2) they would definitely not damage it in a manner that broke the ability of the secondaries to update, because presumably the reason they changed your zone was to push their data out to the 'net under your domain name, and that wouldn't work without the secondaries. 3) if they just wanted your domain to go away, there are easier ways to make that happen. So from my point of view, your question still makes no sense, even as corrected. I may be missing your point. Otherwise, if your question is "How about the case where the master zone file SERVER has been rendered unreachable and the secondaries can no longer get updates," I think I answered that already, between the public and private e-mails we've exchanged. The fundamental answer there is just to engineer it to avoid that being a serious problem; this includes things like trying to maintain a static DNS environment (dynamic updates of things == somewhat bad, particularly where such updates are required for proper operation), setting your expire record accordingly, and/or maintaining a contingency plan for updating your secondaries through an out-of-band mechanism, such as floppy disk via FedEx, modem to private dial-in, or pretty much any other way one uses to get bits from A to B. ... JG -- Joe Greco - sol.net Network Services - Milwaukee, WI - http://www.sol.net "We call it the 'one bite at the apple' rule. Give me one chance [and] then I won't contact you again." - Direct Marketing Ass'n position on e-mail spam(CNN) With 24 million small businesses in the US alone, that's way too many apples.
On Sun, Jun 13, 2010 at 03:23:06PM -0500, Larry Sheldon wrote:
On 6/13/2010 14:59, Joe Greco wrote:
How about the case where the master zone file has be amputated and the secondaries can no longer get updates?
Mea culpa.
That was suppose to say "How about the case where the master zone file has beEN amputated and the secondaries can no longer get updates?
I'm really not sure what you're asking, and I don't know what "master zone file has been amputated" means, but if the master server goes unreachable, then, for each secondary, either: (a) it's not reachable from anywhere, in which case it doesn't really matter what information it has because nothing will be querying it, or (b) it is reachable from somewhere, in which case you log in to it from that somewhere, edit the configuration file, change "slave" to "master", and restart BIND. (Adjust as needed for whatever DNS server is in use, if it's not BIND.) -- Brett
On 6/13/2010 18:09, Brett Frankenberger wrote:
On Sun, Jun 13, 2010 at 03:23:06PM -0500, Larry Sheldon wrote:
On 6/13/2010 14:59, Joe Greco wrote:
How about the case where the master zone file has be amputated and the secondaries can no longer get updates?
Mea culpa.
That was suppose to say "How about the case where the master zone file has beEN amputated and the secondaries can no longer get updates?
I'm really not sure what you're asking, and I don't know what "master zone file has been amputated" means, but if the master server goes unreachable, then, for each secondary, either: (a) it's not reachable from anywhere, in which case it doesn't really matter what information it has because nothing will be querying it, or (b) it is reachable from somewhere, in which case you log in to it from that somewhere, edit the configuration file, change "slave" to "master", and restart BIND. (Adjust as needed for whatever DNS server is in use, if it's not BIND.)
I have been faulted for injecting "politics" into the discussion of BGP configurations for people that ought not...... There I go again. Have you actually read the article I posted at the top of this thread? -- Somebody should have said: A democracy is two wolves and a lamb voting on what to have for dinner. Freedom under a constitutional republic is a well armed lamb contesting the vote. Requiescas in pace o email Ex turpi causa non oritur actio Eppure si rinfresca ICBM Targeting Information: http://tinyurl.com/4sqczs http://tinyurl.com/7tp8ml
participants (3)
-
Brett Frankenberger -
Joe Greco -
Larry Sheldon