Configure Internet Primary DNS

[Ian]

We have an IIS 5 web server and an Exchange 2000 server on
the private network befind a firewall. The 2 servers are
made visible on Internet by port forwarding and adding
some DNS reords including MX records in ISP's DNS server.

The ISP said that we can host the primary DNS server in
order for us to manage our DNS records, and ISP will host
the secondary. A local DNS server is set up on the
internal network. How to modify it to be an our own
Internet Primary DNS server? So we can add records like
ftp.mydomain.com, www.mydomain.com, mail.mydomain.com, or
whatever we need. Thanks.

 

[Guest]

make in the forward lookup zone a new zone and make it standard primary, for the name of the lookup zone type:
yourdomain.yourextention,
create the file,
in the properties select in Zone Transfers and select 'only the following servers' and enter the ip from your IPS dns servers
I think that's about it, of course you have to open port 53 (don't think there are any other) on your firewall to your dns server to allow dns reqsuests.

Wim.

 

[Ian]

Thank you very much for your help.

So I can just use my public IP address as the Primary DNS
server IP address. Is there anything else to do with my
DSL ISP? Can I use the same public IP address as the
Secondary DNS server IP address or can I leave it blank?
Thanks.

-----Original Message-----
make in the forward lookup zone a new zone and make it

standard primary, for the name of the lookup zone type:

yourdomain.yourextention,
create the file,
in the properties select in Zone Transfers and

select 'only the following servers' and enter the ip from
your IPS dns servers

I think that's about it, of course you have to open port

53 (don't think there are any other) on your firewall to
your dns server to allow dns reqsuests.

 

[Ace Fekay [MVP]]

In

Thank you very much for your help.

So I can just use my public IP address as the Primary DNS
server IP address. Is there anything else to do with my
DSL ISP? Can I use the same public IP address as the
Secondary DNS server IP address or can I leave it blank?
Thanks.

No, do not use your public IP internally. That will invite errors.

If you want to host your own zone, and you're running AD (evident by Ex 2k),
then you will need two separate DNS servers. One to host AD internally, and
one to host your public records. But you only point your internal machines
to the "internal" DNS server or you will have numerous errors. Do not point
to the external DNS. Your external server must NOT contain any private IPs
or private internal records.

Configure forwarding on your "internal" DNS to the ISP, not to the
"external" DNS. See http://support.microsoft.com/?id=300202 on how to do
that.

Now, depending...and if you are hosting your own webserver and ftp server...

1. If you're domain name for AD is the same as your external domain name,
(called Split Horizon or a Split Zone), manually create the www and ftp
records on the internal DNS and give it the private IPs.

2. If the names are different, the manually create the "external" name on
your "internal" DNS. Then manually create the www and ftp records and give
it the internal private IPs.

3. If not hosting internally, and the name is the same, then create the www
and ftp manually and give it the external IPs.

4. For mail, this is not necessary since you are using MAPI clients
(assuming so).



--
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