Well....., it depends:
If his host (edomains) is using IP forwarding to direct people to his domain,
and, Praedor has to tell edomains what IP to forward his domain to, then yeh, I
think there is a problem. My setup is similar (but with a fixed IP). I have a domain
and my host provides IP forwarding and sets the MX record on information I supply to
the host to direct the world to my server. I run BIND 8 as a caching only DNS on my
side so I'm not propogating my domain/IP out to the master DNS servers. That's what
my host does. If Praedor has to provide his host with this same information, then I
don't understand how his local DNS will be able to change the IP forwarding
relationship that was initially set up with edomains.
I'm still learning though, so If I'm really missing something here, please feel
free to flame me. I guess if Praedor simply registered his domain and is not relying
on anyone else to provide IP forwarding and MX record updates, then a "full blown"
DNS run locally should do the trick. (That just means port 53 is hanging open
permanently)
"J. Craig Woods" wrote:
> 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
--
David C. Rankin, J.D., P.E.
RANKIN * BERTIN, PLLC
1329 N. University, Suite D4
Nacogdoches, Texas 75961
(936) 715-9333
(936) 715-9339 fax
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
