Do I add a Zone?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello al

First of all, excuse the double posting, but I thought both the DNS
and Exchange newsgroup should have a look at this question

I've got a free DNS service (dyndns.org). This allows me to name
both my website (http://www.mydomain.dyndns.org) and my FTP
site (http://ftp.mydomain.dyndns.org). Along with this free service,
I've added a email forwarding component. This will allow us to have
email sent to (e-mail address removed) forwarded to our internal
Exchange server

My AD/DNS name is mydomain.prv (prv=private). Will I have to make
any notations in DNS (adding the dyndns zone) so both internal and
external clients will excess to both the website and FTPsite? Also,
what if any notations do I need to make for our email forwarding service

Any help will be greatly appreciated
 
Hodgepodge said:
Hello all

First of all, excuse the double posting, but I thought both the DNS
and Exchange newsgroup should have a look at this question.
Click to expand...

If you don't get any help you might want to re-state the specifics
of your question, then follow it with a clear statement of the steps
you have taken.

At this point your message bears an unfortunate resemblance to your
email alias. <GRIN>

Seriously, many of us have set up DNS internally and externally and
even mixed in some sort of dynamic public registration or email forwarding
but it isn't clear what you have done so far or what specific problems
you still have.
 
H> First of all, excuse the double posting, [...]

No. Don't multi-post. Cross-post (if appropriate).

H> My AD/DNS name is mydomain.prv (prv=private). Will I have
H> to make any notations in DNS (adding the dyndns zone) so
H> both internal and external clients will excess to both the
H> website and FTPsite?

Only you know. You've deliberately hidden the domain names from
us, and thus hidden from us the data that are required to answer
that question. You've thus prevented anyone from being able to
help you.

<URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/dont-obscure-your-dns-data.html>
 
----- Herb Martin wrote: -----


If you don't get any help you might want to re-state the specifics
of your question, then follow it with a clear statement of the steps
you have taken.

At this point your message bears an unfortunate resemblance to your
email alias. <GRIN>

Seriously, many of us have set up DNS internally and externally and
even mixed in some sort of dynamic public registration or email forwarding
but it isn't clear what you have done so far or what specific problems
you still have.

--
Herb Martin

First of all, thanks for the reply! But I don't understand why you can't make heads-or-tails of
my questions? It makes perfect sense to me....<grin> Secondly, let me see if I can clarify my
situation.

I'm trying to circumvent a possible problem. Or maybe it'll work the as it did before.

When the Enterprise was a Workgroup as opposed to a Active Directory domain, you'd
log into our FTPsite by using the free DNS service name ftp://ftp.mydomain.dyndns.org.
You'd use the same service, http://www.mydomain.dyndns.org to gain access to our
Website.

I was just wondering whether the change to AD domain (mydomain.prv) have any affect
on how you'd gain access to these services. In other words, as I mentioned in my initial
post: Will I have to make any notations in my AD domain about my free DNS service?

I don't know if I've clarified matters any, but I hope!

Thanks again!
 
In Hodgepodge <[email protected]> posted a question
Then Kevin replied below:
: ----- Herb Martin wrote: -----
:
:
: If you don't get any help you might want to re-state the
: specifics of your question, then follow it with a clear
: statement of the steps you have taken.
:
: At this point your message bears an unfortunate resemblance to
: your email alias. <GRIN>
:
: Seriously, many of us have set up DNS internally and externally
: and even mixed in some sort of dynamic public registration or
: email forwarding but it isn't clear what you have done so far or
: what specific problems you still have.
:
: --
: Herb Martin
:
: First of all, thanks for the reply! But I don't understand why you
: can't make heads-or-tails of my questions? It makes perfect sense to
: me....<grin> Secondly, let me see if I can clarify my situation.
:
: I'm trying to circumvent a possible problem. Or maybe it'll work the
: as it did before.
:
: When the Enterprise was a Workgroup as opposed to a Active Directory
: domain, you'd
: log into our FTPsite by using the free DNS service name
: ftp://ftp.mydomain.dyndns.org.
: You'd use the same service, http://www.mydomain.dyndns.org to gain
: access to our
: Website.
:
: I was just wondering whether the change to AD domain (mydomain.prv)
: have any affect
: on how you'd gain access to these services. In other words, as I
: mentioned in my initial
: post: Will I have to make any notations in my AD domain about my free
: DNS service?
:
: I don't know if I've clarified matters any, but I hope!
:
: Thanks again!

I understood perfectly, you need to add two zones:
ftp.mydomain.dyndns.org
www.mydomain.dyndns.org

Then in each of these zone put one blank host with the IP of your Website
and ftp site. Then you can access it internally without the name interfering
with other dyndns.org sites.
 
In
Kevin D. Goodknecht said:
In

I understood perfectly, you need to add two zones:
ftp.mydomain.dyndns.org
www.mydomain.dyndns.org

Then in each of these zone put one blank host with the IP of your
Website and ftp site. Then you can access it internally without the
name interfering with other dyndns.org sites.

--
Best regards,
Kevin D4 Dad Goodknecht Sr. [MVP]
Hope This Helps
============================
Click to expand...

Just to add, since running Exchange internally, make sure (if you haven't
already done so) to set your Recipient Policy to: @mydomain.dyndns.org so
it's authorative to receive mail on that domain. It doesn't matter what
private internal AD DNS name the Exchange server is under, just that the
Recipient policy dicatates what domain it;s authorative to receive mail
under.

Under DynDNS you'll also want to create a mail record, call it mail, then
create an MX record and point it to mail.mydomain.dyndns.org

If you've already done that part, disregard my explanation.


--
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
 
----- Kevin D. Goodknecht [MVP] wrote: -----
First of all, thanks for the reply! But I don't understand why you
: can't make heads-or-tails of my questions? It makes perfect sense to
: me....<grin> Secondly, let me see if I can clarify my situation.
:
: I'm trying to circumvent a possible problem. Or maybe it'll work the
: as it did before.
:
: When the Enterprise was a Workgroup as opposed to a
: Active Directory domain, you'd log into our FTPsite by
: using the free DNS service name ftp.mydomain.dyndns.org.
: You'd use the same service, : www.mydomain.dyndns.org
: to gain access to our Website.
:
: I was just wondering whether the change to AD domain (mydomain.prv)
: have any affect on how you'd gain access to these services. In other words,
: as I mentioned in my initial post: Will I have to make any notations in my
: AD domain about my free DNS service?
:
: I don't know if I've clarified matters any, but I hope!
:
: Thanks again!

I understood perfectly, you need to add two zones:
ftp.mydomain.dyndns.org
www.mydomain.dyndns.org

Then in each of these zone put one blank host with the IP of your Website
and ftp site. Then you can access it internally without the name interfering
with other dyndns.org sites.



Thanks a lot for the reply Kevin.

What I understand of DNS, your reply is what I thought.
I wasn't sure how it would be noted.

Thanks again!
 
----- Ace Fekay [MVP] wrote: ----
I understood perfectly, you need to add two zones
ftp.mydomain.dyndns.or
www.mydomain.dyndns.or
Then in each of these zone put one blank host with the IP of you
Click to expand...
Website and ftp site. Then you can access it internally without th
name interfering with other dyndns.org sites
-
Click to expand...
Best regards
Kevin D4 Dad Goodknecht Sr. [MVP
Hope This Help
===========================
Click to expand...

Just to add, since running Exchange internally, make sure (if you haven'
already done so) to set your Recipient Policy to: @mydomain.dyndns.org s
it's authorative to receive mail on that domain. It doesn't matter wha
private internal AD DNS name the Exchange server is under, just that th
Recipient policy dicatates what domain it;s authorative to receive mai
under

Under DynDNS you'll also want to create a mail record, call it mail, the
create an MX record and point it to mail.mydomain.dyndns.or

If you've already done that part, disregard my explanation


--
Regards
Ac

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, MV
Microsoft Windows MVP - Active Director
--
================================

Thanks Ace for your reply

Your reply was exactly what DynDns.org said. They're going to walk me throug
the whole process when we're ready

Thanks again
 
In
Hodgeposge said:
----- Ace Fekay [MVP] wrote: -----
your > Website and ftp site. Then you can access it internally
without the > name interfering with other dyndns.org sites.

Just to add, since running Exchange internally, make sure (if
you haven't already done so) to set your Recipient Policy to:
@mydomain.dyndns.org so it's authorative to receive mail on that
domain. It doesn't matter what private internal AD DNS name the
Exchange server is under, just that the Recipient policy
dicatates what domain it;s authorative to receive mail under.

Under DynDNS you'll also want to create a mail record, call it
mail, then create an MX record and point it to
mail.mydomain.dyndns.org

If you've already done that part, disregard my explanation.


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

Thanks Ace for your reply!

Your reply was exactly what DynDns.org said. They're going to walk me
through the whole process when we're ready.

Thanks again!
Click to expand...

Awesome!!
:-)

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