Hi Greg, Yes! This is always a good idea for the sake of standardization and ease of understanding for potential future administrators who come along after. Of course, this is not so critical on a residential implementation, but... ----- Original Message ----- From: "Gregory Nowak" <greg@xxxxxxxxxxxxxxxxxx> To: <speakup at braille.uwo.ca> Sent: Sunday, October 13, 2002 9:43 AM Subject: Re: dns problem > Yeah, if your isp or whoever you registered your domain with, knows your ns1 machine by one name, and you decide to give your ns1 another name without telling them, you're going to have problems. Either contact your isp and whoever you registered your domain with, and give them the new name for ns1, or make your new server have your old server's name. > > I never saw the advantage of naming your dns servers as ns1.domain.com, but I think I do now (smile). > > Greg > > > On Sun, Oct 13, 2002 at 10:43:04AM -0400, Scott Howell wrote: > > Folks, > > > > I ran into a dns problem and hope maybe someone can help me out. > > > > I currently have a box named lrxms it shows up as far as I know as > > lrxms.lrxms.net and it has two interfaces of 66.92.147.165 and > > 192.168.1.1. > > Now I recently configured a new machine that will be a firewall box and > > run a few services instead of lrxms running everything including the > > firewall. > > > > I first shutdown the lrxms machine and remove it from the network. I > > plugged in the new box which is named zoose; yeah on a greek mythology > > kick. I only edited the zone file to show the Cname of zoose, but made > > no other changes. The external ip and internal ip stayed the same from > > when lrxms was performing the dns service. > > > > Now the first problem I ran into is I had to grab the db.cache file from > > the old box cause on the new Debian box, zoose it was empty. Ok, so now > > when I attempted to perform lookups I get server not found errors. I > > could do a lookup on my own domain, but nothing else. > > I then put the old machine back online and all is fixed. So, I'd > > appreciate any help as to where to look for problems. I wonder if I need > > to tell the folks I registered my dns servers with about the change or > > my ISP who does reverse for me. I only told either about ns1.lrxms.net > > because I had planned to change the name of the machine in any case. > > Ay I finally got the firewall working I think, but this dns problem has > > me running in circles. Its was bad enough I had to litterally use the > > same cables from my old machine when bringing the new one online. I > > think the switch keeps that segment info in its little brain and you all > > but have to unplug the damned thing I guess to reset it. > > > > tia > > > > Scott > > > > > > _______________________________________________ > > Speakup mailing list > > Speakup at braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup
