I have the following setup, and it is working fine in my SOHO:
Workstations--->Ethernet--->ISDN router--->INTERNET
The ISDN router does NAT. It gets one IP address via DHCP when
it calls my ISP. It is NOT a DNS; that is done by my ISP.
Now I'm thinking of adding a video server to the Ethernet above.
There are various kinds of these, but the ones I'm most
interested in seem to require that either a static IP address be
set for the server or a static name (URL). I like the protection of being behind a router doing NAT. When the video server is added, the whole setup should probably go to being "always on" versus "sometimes on" as it is now. My questions:
1> If my ISP will put an entry in their DNS, would that take care
of it? ("sometimes on ")
2> If I replace the ISDN router with a combination router +
DNS server + firewall, and then configure my own DNS,
would that be another approach which should work?
(Still "sometimes on")
3> Would it be easire/better to move to a static IP setup
completely? ("Always on".) What would be the tradeoffs?
Workstations--->Ethernet--->ISDN router--->INTERNET
The ISDN router does NAT. It gets one IP address via DHCP when
it calls my ISP. It is NOT a DNS; that is done by my ISP.
Now I'm thinking of adding a video server to the Ethernet above.
There are various kinds of these, but the ones I'm most
interested in seem to require that either a static IP address be
set for the server or a static name (URL). I like the protection of being behind a router doing NAT. When the video server is added, the whole setup should probably go to being "always on" versus "sometimes on" as it is now. My questions:
1> If my ISP will put an entry in their DNS, would that take care
of it? ("sometimes on ")
2> If I replace the ISDN router with a combination router +
DNS server + firewall, and then configure my own DNS,
would that be another approach which should work?
(Still "sometimes on")
3> Would it be easire/better to move to a static IP setup
completely? ("Always on".) What would be the tradeoffs?