DNS and WebServer

[April L]

I am running Exchange/DNS/IIS/Web server all on one box. I
am having no problems with exchange but I am unable to get
my web Server up. (should have been the easier of the 2) I
have opened all the ports necessary on my firewall I have
forwarded everything I need but I am unable to get this
going. I was using (no-ip.org) for DNS resolution with no
problems. So I know it works. I have to be setting up my
own DNS incorrectly. This is what I have in forward zone:

(same as parent folder) Start of Authority [54],
noc.xyzdomain.com.,
(same as parent folder) Name Server noc.xyzdomain.com.
(same as parent folder) Host (my static ip HERE)
(same as parent folder) Host 169.254.201.60
(same as parent folder) Host 192.168.1.10
(same as parent folder) Mail Exchanger [10]
xyzdomain.com.
noc Host 192.168.1.10

Reverse:

(same as parent folder) Start of Authority [8],
noc.xyzdomain.com.,
(same as parent folder) Name Server noc.xyzdomain.com.
(same as parent folder) Host (my static ip HERE)
192.168.1.10 Pointer noc.xyzdomain.com.


IDEAS???? I am so close yet so far away.. I need an
expert!!
Thanks!
~APRIL

 

[Ace Fekay [MVP]]

In

I am running Exchange/DNS/IIS/Web server all on one box. I
am having no problems with exchange but I am unable to get
my web Server up. (should have been the easier of the 2) I
have opened all the ports necessary on my firewall I have
forwarded everything I need but I am unable to get this
going. I was using (no-ip.org) for DNS resolution with no
problems. So I know it works. I have to be setting up my
own DNS incorrectly. This is what I have in forward zone:

(same as parent folder) Start of Authority [54],
noc.xyzdomain.com.,
(same as parent folder) Name Server noc.xyzdomain.com.
(same as parent folder) Host (my static ip HERE)
(same as parent folder) Host 169.254.201.60
(same as parent folder) Host 192.168.1.10
(same as parent folder) Mail Exchanger [10]
xyzdomain.com.
noc Host 192.168.1.10

Reverse:

(same as parent folder) Start of Authority [8],
noc.xyzdomain.com.,
(same as parent folder) Name Server noc.xyzdomain.com.
(same as parent folder) Host (my static ip HERE)
192.168.1.10 Pointer noc.xyzdomain.com.


IDEAS???? I am so close yet so far away.. I need an
expert!!
Thanks!
~APRIL

I don't see a "www' under your xyzdomain.com zone. Is that how you normally
connect to your website with:
www.xyzdomain.com ?

So assuming since you said it already worked prior to that, then your
previous provider probably had that record created. Otherwise, how can one
connect by using www.xyzdomain.com unless you only want users to connect by
http://xyzdomain.com for any specific reason?


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

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

 

[Kevin D. Goodknecht Sr. [MVP]]

In Ace Fekay [MVP] <PleaseSubstituteMyFirstName&[email protected]>
posted their concerns
Then Kevin made his reply below:

In

I am running Exchange/DNS/IIS/Web server all on one box. I
am having no problems with exchange but I am unable to get
my web Server up. (should have been the easier of the 2) I
have opened all the ports necessary on my firewall I have
forwarded everything I need but I am unable to get this
going. I was using (no-ip.org) for DNS resolution with no
problems. So I know it works. I have to be setting up my
own DNS incorrectly. This is what I have in forward zone:

(same as parent folder) Start of Authority [54],
noc.xyzdomain.com.,
(same as parent folder) Name Server noc.xyzdomain.com.
(same as parent folder) Host (my static ip HERE)
(same as parent folder) Host 169.254.201.60
(same as parent folder) Host 192.168.1.10
(same as parent folder) Mail Exchanger [10]
xyzdomain.com.
noc Host 192.168.1.10

Reverse:

(same as parent folder) Start of Authority [8],
noc.xyzdomain.com.,
(same as parent folder) Name Server noc.xyzdomain.com.
(same as parent folder) Host (my static ip HERE)
192.168.1.10 Pointer noc.xyzdomain.com.


IDEAS???? I am so close yet so far away.. I need an
expert!!
Thanks!
~APRIL

I don't see a "www' under your xyzdomain.com zone. Is that how you
normally connect to your website with:
www.xyzdomain.com ?

So assuming since you said it already worked prior to that, then your
previous provider probably had that record created. Otherwise, how
can one connect by using www.xyzdomain.com unless you only want users
to connect by http://xyzdomain.com for any specific reason?

I had intended on replying to this post but just to add, if he intends to
allow access by http://xyxdomain from the public side it is going to be
inconsistent due to the fact that he has two of three blank hosts using
non-routable private IP addresses.

 

[Jonathan de Boyne Pollard]

AL> I am unable to get my web Server up. [...]
AL> I was using (no-ip.org) for DNS resolution with no
AL> problems. So I know it works.

That it works now, or that it worked then ?

AL> I have to be setting up my own DNS incorrectly.

How have you determined that DNS service is in fact the
locus of your problem ? Don't tell us your guesses at
what the cause of the problem is and expect us to work
from those. If they were right, and you knew what the
problem was, you wouldn't be asking us for help in the
first place. Tell us the _symptoms_.

"I am unable to get my web server up." is a wholly
indaequate problem description.

<URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/problem-report-standard-litany.html>

For all we know, your problem (whatever it actually is)
could be entirely unrelated to DNS service. "I am unable
to get my web server up." could be caused by not having
a web server installed in the first place, for example,
or by a misconfiguration of the service manager.

 

[Ace Fekay [MVP]]

In

In Ace Fekay [MVP] <PleaseSubstituteMyFirstName&[email protected]>
posted their concerns
Then Kevin made his reply below:

In

I am running Exchange/DNS/IIS/Web server all on one box. I
am having no problems with exchange but I am unable to get
my web Server up. (should have been the easier of the 2) I
have opened all the ports necessary on my firewall I have
forwarded everything I need but I am unable to get this
going. I was using (no-ip.org) for DNS resolution with no
problems. So I know it works. I have to be setting up my
own DNS incorrectly. This is what I have in forward zone:

(same as parent folder) Start of Authority [54],
noc.xyzdomain.com.,
(same as parent folder) Name Server noc.xyzdomain.com.
(same as parent folder) Host (my static ip HERE)
(same as parent folder) Host 169.254.201.60
(same as parent folder) Host 192.168.1.10
(same as parent folder) Mail Exchanger [10]
xyzdomain.com.
noc Host 192.168.1.10

Reverse:

(same as parent folder) Start of Authority [8],
noc.xyzdomain.com.,
(same as parent folder) Name Server noc.xyzdomain.com.
(same as parent folder) Host (my static ip HERE)
192.168.1.10 Pointer noc.xyzdomain.com.


IDEAS???? I am so close yet so far away.. I need an
expert!!
Thanks!
~APRIL

I don't see a "www' under your xyzdomain.com zone. Is that how you
normally connect to your website with:
www.xyzdomain.com ?

So assuming since you said it already worked prior to that, then your
previous provider probably had that record created. Otherwise, how
can one connect by using www.xyzdomain.com unless you only want users
to connect by http://xyzdomain.com for any specific reason?

I had intended on replying to this post but just to add, if he
intends to allow access by http://xyxdomain from the public side it
is going to be inconsistent due to the fact that he has two of three
blank hosts using non-routable private IP addresses.

Oh yes, boy I missed that one. Bright as daylight. GOt the APIPA address
(the 169.254.x.x) which probably happened from a failed DHCP request, and
the 192.168.1.10 number. Can't mix public and private IP addressing on the
same server. He'll need two DNS servers if he wants to do this.

Taking that in consideration, and this server is holding both public IPs and
the internal private IPs, I'm surpirsed that mail is working consistently
since resolving the MX record will cause a Round Robin reply of one of three
records, the two above (169.254 and 192.168.1.10) and the actual external IP
that April didn't provide us.

If we can see the actual domain name, we can take a look at it and run a
couple of tests.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

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