DNS server use live through ISP

  • Thread starter Thread starter Ron
  • Start date Start date
R

Ron

OK this maybe a noobie question but I am trying to
run my Domain controller live on the Internet through DSL
on an ISP I get an IP adress through DHCP from them so I
am having DNS issues. I would like all of my other
computers and server to log onto the domain and use it as
a DNS server, including my web and email server. I have
purchased a Domain Name but I can not get a DNS server to
point anyone on the internet to my Domain. I am trying to
setup my own but not sure whatI am missing.
 
Since you have a DHCP address from your ISP, see www.dyndns.org and set up
an account there and set up yourdomain.dnsalias.com or something similar.
Download one of the update service apps from there, install it on your
server so it updates your account and yourdomain.dnsalias.com has your
current address.

You need a router (ideally a firewall) that does NAT. In there, open up
ports 25 (for inbound mail) and port 80 (for http, but I'd recommend using
SSL and port 443 instead) in your firewall and forward them to the
appropriate private IP address of your mail/web server.

Have whomever hosts your DNS set up an MX record for your domain that points
to yourdomain.dnsalias.com (MX records don't refer to IP addresses
directly).

For your web server, you can use either http://yourdomain.dnsalias.com or
https:// if using SSL as recommended.

For your internal DNS, make sure that all servers and workstations specify
the internal AD-integrated DNS server's IP address in their network
settings. The AD-integrated DNS server should be set up with forwarders to
your ISP's DNS servers for external resolution. See
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202 for more
info.

Does this help?
 
Yes it does help some.We have another setup with a small
firewall router. We where trying to come up with a way to
do it while getting my adresses directly from my ISP but
I can see the problem unless I can get my ISP to add me
to there DNS server. When I do an NSlookup on my IP
adress it comes back to Ctel because its in there Domain.
Not sure if I can do it without the Firewall router.
-----Original Message-----
Since you have a DHCP address from your ISP, see
www.dyndns.org and set up
an account there and set up yourdomain.dnsalias.com or something similar.
Download one of the update service apps from there, install it on your
server so it updates your account and
yourdomain.dnsalias.com has your
current address.

You need a router (ideally a firewall) that does NAT. In there, open up
ports 25 (for inbound mail) and port 80 (for http, but I'd recommend using
SSL and port 443 instead) in your firewall and forward them to the
appropriate private IP address of your mail/web server.

Have whomever hosts your DNS set up an MX record for your domain that points
to yourdomain.dnsalias.com (MX records don't refer to IP addresses
directly).

For your web server, you can use either
http://yourdomain.dnsalias.com or
 
In
Yes it does help some.We have another setup with a small
firewall router. We where trying to come up with a way to
do it while getting my adresses directly from my ISP but
I can see the problem unless I can get my ISP to add me
to there DNS server. When I do an NSlookup on my IP
adress it comes back to Ctel because its in there Domain.
Not sure if I can do it without the Firewall router.

That's because they own the IP address, not you. Normally in most cases if
you have a static IP, they can delegate the reverse range to your DNS, that
is if it is properly registered as a nameserver. However, if DHCP, which
apparently your line is, they won't do that, but they may create an entry in
their nameservers for your domain name.

DOing it with DHCP is difficult and you may not achieve the results you are
looking for. DynDNS as Lanwench mentioned, is a good service, but when it
comes to mail, DNS and other applications/services that require static
addressing, you may come across inconsistencies...


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In Ace Fekay [MVP] <PleaseSubstituteMyActualFirstName&[email protected]>
posted a question
Then Kevin replied below:
In (e-mail address removed)


That's because they own the IP address, not you. Normally in most
cases if you have a static IP, they can delegate the reverse range to
your DNS, that is if it is properly registered as a nameserver.
However, if DHCP, which apparently your line is, they won't do that,
but they may create an entry in their nameservers for your domain
name.

DOing it with DHCP is difficult and you may not achieve the results
you are looking for. DynDNS as Lanwench mentioned, is a good service,
but when it comes to mail, DNS and other applications/services that
require static addressing, you may come across inconsistencies...

To add, since you have a dynamic IP address, you are not going to be able to
have a reverse lookup on your IP that points to your mail server hostname. I
suggest the you set your ISP's Mail server as a Smart host for your mail
server to relay outgoing messages through.
Depending on your ISP's mail server setup you may need to have your mail
server authenticate to their mail server using your account details, or it
may accept mail based solely on it coming from their IP address.
 
Ace said:
In (e-mail address removed)


That's because they own the IP address, not you. Normally in most
cases if you have a static IP, they can delegate the reverse range to
your DNS, that is if it is properly registered as a nameserver.
However, if DHCP, which apparently your line is, they won't do that,
but they may create an entry in their nameservers for your domain
name.

DOing it with DHCP is difficult and you may not achieve the results
you are looking for. DynDNS as Lanwench mentioned, is a good service,
but when it comes to mail, DNS and other applications/services that
require static addressing, you may come across inconsistencies...

I haven't had problems with plain ole SMTP delivery using dynamic dns
services, myself. I wouldn't recommend it in a large organization, but for
small/home offices, it seems to work fine. I wouldn't do too much else with
dynamic DNS...
 
In Lanwench [MVP - Exchange]
I haven't had problems with plain ole SMTP delivery using dynamic dns
services, myself. I wouldn't recommend it in a large organization,
but for small/home offices, it seems to work fine. I wouldn't do too
much else with dynamic DNS...

Hi Lanwench,

I understand. I used to use it once years ago too, but it has some minor
downfalls, such as when my IP changed, some servers had the old record
cached and would cause delays recieving mail. Just rather use a static
address !


Cheers!
:-)

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Ace Fekay [MVP] wrote:
Hi Lanwench,

I understand. I used to use it once years ago too, but it has some
minor downfalls, such as when my IP changed, some servers had the old
record cached and would cause delays recieving mail. Just rather use
a static address !

Me too - I also like paying $35/mo for my cable modem as opposed to a lot
more for a business class DSL account ;-)
 
In Lanwench [MVP - Exchange]
Ace Fekay [MVP] wrote:


Me too - I also like paying $35/mo for my cable modem as opposed to a
lot more for a business class DSL account ;-)

Yea, same here. That's why I dumped my T1 for a cable account! :-)

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top