dns problem
Scott Howell
showell at lrxms.net
Sun Oct 13 10:43:04 EDT 2002
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
More information about the Speakup
mailing list