dhcp and nameservers

[Paul Donahue]

<Disclaimer>
you really don't want to bring up a server in DHCP mode. Although I have
done this a few times it's generally a bad idea. You really should have your
server on a Static IP
</Disclaimer>

<solution>
just setup your own name servers or use something like the public dns
http://soa.granitecanyon.com and have it point to your IP address. Your name
will resolve soon enough, even through your ISP's name servers!
</solution>

<cover ass from responsibility>
this is a bad idea as it probably violates your TOS with your ISP however
most sysadmins don't have enough time to scan through various domain names
to see if one is resolving to one of their IP's. If they do have time to do
this, they should be looking for a better job anyway. :)  I don't "think"
TCImet does this :)
</cover ass from responsibility>

-----Original Message-----
From: linux-user-admin@egr.msu.edu
[mailto:linux-user-admin@egr.msu.edu]On Behalf Of Marcel Kunath
Sent: Friday, July 07, 2000 2:27 PM
To: linux-user@egr.msu.edu
Subject: dhcp and nameservers


Hi,

the goal is to use your ISP to get an online connection through a DHCP cable
modem. You also want to host a server on your connection but not through the
ISPs nameservers.

I am confused on how to do this properly. Does the DHCP access depend on the
ISP nameserver? Does the correct resolving of the domain and the hosting of
mail and web server depend on the nameservers other than the ISP?

How can this work out???


 -- Marcel Kunath

_______________________________________________
linux-user mailing list
linux-user@egr.msu.edu
http://www.egr.msu.edu/mailman/listinfo/linux-user