Re: Internet and intranet domain name - problem with dns!
- From: "Andrea" <vtube@xxxxxxxxx>
- Date: 11 Dec 2006 03:38:36 -0800
Phillip Windell ha scritto:
Then you are screwed. That has to be corrected,..it needs to be a fixed
IP#. As far as your clients are concerned your internal AD DNS is
"authoritative" for the domian name (not the ISP), and your AD/DNS cannot
deal with the dynamic IP# from the ISP.
If that can't be made static,..then you have to do "No. 1".
This kind of trouble is why a person has to reseach everything before the AD
Domain is created. And you also have to research all the ramifications of
getting an ISP that uses dynamic IP#s before you give them any $$$.
Phil's Rules:
1. AD Domains are not the same thing as Public Domains,...have nothing to do
with each other,... exist for entirely different reasons,...and should never
be the same name.
2. Never except dynamic IPs from an ISP for a commecial network. Dynamic
IP#s are for Home Users.
Thanks Philip!
We have a fixed IP for the web server, not for the POP3 server.
Andrea
.
- References:
- Prev by Date: Re: Can't get L2TP VPN working with NAT...PPTP works fine
- Next by Date: Re: Can't get L2TP VPN working with NAT...PPTP works fine
- Previous by thread: Re: Internet and intranet domain name - problem with dns!
- Next by thread: Ping localhst displays huge times
- Index(es):
Relevant Pages
|
Loading