network admin, ip addresses for webserver

[Wade Smart]

--
Registered Linux User: #480675
Registered Linux Machine: #408606
Linux since June 2005


On Mon, Oct 27, 2014 at 3:46 PM, Niles Rogoff <nilesrogoff at gmail.com> wrote:
> Not mine, it depends on the router. It's most likely much easier to program
> a masquerading NAT system without a resolver than it is to create one that
> does allow hostnames. Most routers are limited to 1-2M of flash space
> anyways, for both OS and configuration.
>
> On Mon, Oct 27, 2014 at 4:40 PM, Colin Law <clanlaw at gmail.com> wrote:
>>
>> On 27 October 2014 20:35, Thufir <hawat.thufir at gmail.com> wrote:
>> > Why is important for a server to use static ip address instead of DHCP?
>> > If it's behind a router, why not use that router's outward facing IP
>> > address, and then the router will *route* to that hostname?
>>
>> Many (most?) routers require an IP address to be specified when
>> setting up port forwarding, so the server needs a fixed ip address.
>> Can your router take a host name instead?
>>
>> Colin
>>
>>
>> >
>> > Just in general.
>> >
>> >
>> > thanks,
>> >
>> > Thufir

If the server isnt turned off and the router isnt turned off, both are on
battery backup, you port forward all port 80 and 8080 traffic to a dhcp
address, it wont really matter about the server on dhcp but its going to
very rarely change.  Its just as easy to assign a static to your server
on your Lan and port forward from the Wan.

Wade