David Rankin wrote: > > Praedor; > > I'm not sure I understand, but...... > > I think the issue here is getting your domain name host, edomains if I recall, > to update the IP associated with your domain name when you get a new IP > address assigned. It doesn't matter if you update your local DNS on your box > with the new dhcp IP when it changes because the rest of the world will still > be resolving your domain to whatever IP the domain name register was > forwarding your domain to when it was last updated. I would check with > edomains (or whoever your host is) to see if you can change your IP forwarding > and MX record by script. If so, your in business. The only downside is there > may be a bit of lag time between the changes made and decimination of that > info through the primary DNS system. >
David, As stated earlier, I do not use tinydns (or whatever is is called) but in my effort to purvey some assistance to Praedor, I have suggested that he simply run his own name server. With this method, he could keep his ip info current in both the master zone and reverse lookup zone. He could as well keep the MX resource record up to date. Do you see a problem with this approach? -- J. Craig Woods UNIX/NT Network/System Administration -Art is the illusion of spontaneity-
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
