RE: [cobalt-users] IP Change

[<rpaiz@xxxxxxxxxxxxxx>]

> Thanks for the reply. Should I be setting the time to live
> value low just for the sites that are having the IP
> addresses changed, or can I get away with just changing the
> TTL for the name server itself?

The only sites that *need* the low TTL are those who are moving. But a
very short TTL (temporarily) will do you no harm except to drastically
increase the load on your nameserver. Odds are this will cause you no
sweat... just a slight bandwidth peak for a couple of days.

> When I say ask if I can just change the "name server" I might
> not be using the correct terminology. I am referring to the TTL
> setting I see when I go to "control panel - DNS parameters" and
> then clicking on the IP xxx.xxx.xxx.0/24 - I assume this is the
> "network" referred to when it says "select domain or network."
> There is a SOA configuration there as well as for the one I see
> just for domains in question themselves...  the ones that
> are were getting the new IPs.

Good thing you explained... I don't know, and I don't have a RaQ so I
can't go check. *If* changing this value changes the TTL for every
domain on the box (i.e. the entire nameserver) then no problem; as I
said, it'll increase your DNS traffic but no damage and no big deal. If,
by clicking on that link, you are changing the TTL for the *reverse IP*
DNS management (numbers -> names), then it will do you no good at all.

Remember, you can always find out. Do a dig on one domain (using your
NS, of course) and verify you have the normal TTL. Then make the change,
restart named, and do a dig again. If it changed, good... if not,
well... not good.

If I had to guess, I'd say that xxx.xxx.xxx.0/24 setting refers to the
reverse DNS and that you're going to have to go domain by domain.
Tedious and boring, but such is the life sometimes. I'm starting to do
the same thing myself...

--
Rodolfo J. Paiz
rpaiz@xxxxxxxxxxxxxx <mailto:rpaiz@xxxxxxxxxxxxxx>