| Author |
Message |
.:mmac:.
Guest
|
 Posted:
Wed Jan 12, 2005 11:46 pm Post subject:
DNS doesn't resolve local web page with same name as domain. |
|
|
In a single location I have two win2k forests and two domains that have
a mutual trust with each other. the LAN is on forest/domain2 and the
webserver email etc are on forest/domain1.
I am having disk space trouble with two machines that are DC's for
domain2 so I put in a third DC (win2k3 not yet AD ) to take the load while I
remove one for rebuilding and upgrading which I haven't done yet because
this happened:
Our web site has the same name as our domain (i.e.domain2.com). that
created a problem where I couldn't surf directly to domain2.com, I had to
use www.domain2.com. I get that and it's OK. (I know I need to start over
with this setup, but I volunteer and there isn't time in the near future)
The problem I just found is that if I set my DHCP clients to use a DNS
on Domain2 the web page , with the same name as the domain, is not found. If
I set them to use the DNS on domain1 the page is found fine.
NSlookup resolved to the correct IP using both DNS servers and I see no
differences int the entries.
Did I stumble onto a problem that I am going to have when I upgrade the
whole thing to win2k3 or is this because the domain is the same name and I
need to correct that? Or something else? |
|
| Back to top |
|
 |
Lanwench [MVP - Exchange]
Guest
|
| Posted:
Thu Jan 13, 2005 1:03 am Post subject:
Re: DNS doesn't resolve local web page with same name as dom |
|
|
..:mmac:. wrote:
| Quote: | In a single location I have two win2k forests and two domains
that have a mutual trust with each other. the LAN is on
forest/domain2 and the webserver email etc are on forest/domain1.
I am having disk space trouble with two machines that are DC's for
domain2 so I put in a third DC (win2k3 not yet AD ) to take the load
while I remove one for rebuilding and upgrading which I haven't done
yet because this happened:
Our web site has the same name as our domain (i.e.domain2.com).
that created a problem where I couldn't surf directly to domain2.com,
I had to use www.domain2.com. I get that and it's OK. (I know I need
to start over with this setup, but I volunteer and there isn't time
in the near future)
|
You don't actually have to change your internal domain name at all - what
you have is fairly common. And you can't change anything in W2k anyway, so
you'd have to do a total rebuild, and I don't see that it's worth it.
| Quote: | The problem I just found is that if I set my
DHCP clients to use a DNS
on Domain2 the web page , with the same name as the domain, is not
found. If I set them to use the DNS on domain1 the page is found fine.
NSlookup resolved to the correct IP using both DNS servers and I
see no differences int the entries.
Did I stumble onto a problem that I am going to have when I
upgrade the whole thing to win2k3 or is this because the domain is
the same name and I need to correct that? Or something else?
|
From a client, ping www.domain2.com and see that it's returning the correct
(public) IP address. If it isn't, check its DNS settings and also try
ipconfig /flushdns. If they ping www.domain2.com and get xxx.xxx.xxx.xxx
returned, they ought to be able to open www.domain2.com in their browser and
get to it.
In all the internal DNS servers, you need to create the www host in the
forward lookup zone and point it at the correct public IP address - so
double check this if you still have problems. |
|
| Back to top |
|
|
John Smith
Guest
|
| Posted:
Thu Jan 13, 2005 2:13 am Post subject:
Re: DNS doesn't resolve local web page with same name as dom |
|
|
i'm not sure i followed your story all the way through, but have you tried
adding a static dns entry for your website in domain2?
On Wed, 12 Jan 2005 09:46:06 -0800, .:mmac:. wrote:
| Quote: | In a single location I have two win2k forests and two domains that have
a mutual trust with each other. the LAN is on forest/domain2 and the
webserver email etc are on forest/domain1.
I am having disk space trouble with two machines that are DC's for
domain2 so I put in a third DC (win2k3 not yet AD ) to take the load while I
remove one for rebuilding and upgrading which I haven't done yet because
this happened:
Our web site has the same name as our domain (i.e.domain2.com). that
created a problem where I couldn't surf directly to domain2.com, I had to
use www.domain2.com. I get that and it's OK. (I know I need to start over
with this setup, but I volunteer and there isn't time in the near future)
The problem I just found is that if I set my DHCP clients to use a DNS
on Domain2 the web page , with the same name as the domain, is not found. If
I set them to use the DNS on domain1 the page is found fine.
NSlookup resolved to the correct IP using both DNS servers and I see no
differences int the entries.
Did I stumble onto a problem that I am going to have when I upgrade the
whole thing to win2k3 or is this because the domain is the same name and I
need to correct that? Or something else? |
|
|
| Back to top |
|
|
.:mmac:.
Guest
|
| Posted:
Thu Jan 13, 2005 7:24 am Post subject:
Re: DNS doesn't resolve local web page with same name as dom |
|
|
"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in message
news:O7zxOQO%23EHA.3616@TK2MSFTNGP11.phx.gbl...
| Quote: | .:mmac:. wrote:
In a single location I have two win2k forests and two domains
that have a mutual trust with each other. the LAN is on
forest/domain2 and the webserver email etc are on forest/domain1.
I am having disk space trouble with two machines that are DC's for
domain2 so I put in a third DC (win2k3 not yet AD ) to take the load
while I remove one for rebuilding and upgrading which I haven't done
yet because this happened:
Our web site has the same name as our domain (i.e.domain2.com).
that created a problem where I couldn't surf directly to domain2.com,
I had to use www.domain2.com. I get that and it's OK. (I know I need
to start over with this setup, but I volunteer and there isn't time
in the near future)
You don't actually have to change your internal domain name at all - what
you have is fairly common. And you can't change anything in W2k anyway, so
you'd have to do a total rebuild, and I don't see that it's worth it.
|
Except for the 40 machines I have two forests and two domains. With the same
users on each and a trust between them. It seems kinds pointless to leave it
like that.
| Quote: | The problem I just found is that if I set my
DHCP clients to use a DNS
on Domain2 the web page , with the same name as the domain, is not
found. If I set them to use the DNS on domain1 the page is found fine.
NSlookup resolved to the correct IP using both DNS servers and I
see no differences int the entries.
Did I stumble onto a problem that I am going to have when I
upgrade the whole thing to win2k3 or is this because the domain is
the same name and I need to correct that? Or something else?
From a client, ping www.domain2.com and see that it's returning the
correct
(public) IP address. If it isn't, check its DNS settings and also try
ipconfig /flushdns. If they ping www.domain2.com and get xxx.xxx.xxx.xxx
returned, they ought to be able to open www.domain2.com in their browser
and
get to it.
|
I agree with that but the IP resolves properly but the site doesn't show
even if I type in the IP myself. Since I use Host Headers that sounds like
it should happen that way.
I know that the site wont work without the www in front of it and I
understood that to be the way of things since the domain and web domain are
named the same thing. (I didn't know at the time they could be different) so
I keep leaning that direction.
| Quote: | In all the internal DNS servers, you need to create the www host in the
forward lookup zone and point it at the correct public IP address - so
double check this if you still have problems.
|
That is correct. But I use Host Headers so there are other web sites on that
IP address. Could that be connected? |
|
| Back to top |
|
|
.:mmac:.
Guest
|
| Posted:
Thu Jan 13, 2005 7:26 am Post subject:
Re: DNS doesn't resolve local web page with same name as dom |
|
|
In the DNS Forward zone, Yes.
I know it's confusing to describe, How could one DNS work while the other
doesn't and yet both are giving me the same NSlookup info. If has to be
something that I cant see with nslookup. Something in the Host Header part?
"John Smith" <jsmith@macroshaft.com> wrote in message
news:pan.2005.01.12.20.13.14.375180@macroshaft.com...
| Quote: | i'm not sure i followed your story all the way through, but have you tried
adding a static dns entry for your website in domain2?
On Wed, 12 Jan 2005 09:46:06 -0800, .:mmac:. wrote:
In a single location I have two win2k forests and two domains that
have
a mutual trust with each other. the LAN is on forest/domain2 and the
webserver email etc are on forest/domain1.
I am having disk space trouble with two machines that are DC's for
domain2 so I put in a third DC (win2k3 not yet AD ) to take the load
while I
remove one for rebuilding and upgrading which I haven't done yet because
this happened:
Our web site has the same name as our domain (i.e.domain2.com). that
created a problem where I couldn't surf directly to domain2.com, I had to
use www.domain2.com. I get that and it's OK. (I know I need to start over
with this setup, but I volunteer and there isn't time in the near future)
The problem I just found is that if I set my DHCP clients to use a
DNS
on Domain2 the web page , with the same name as the domain, is not found.
If
I set them to use the DNS on domain1 the page is found fine.
NSlookup resolved to the correct IP using both DNS servers and I see
no
differences int the entries.
Did I stumble onto a problem that I am going to have when I upgrade
the
whole thing to win2k3 or is this because the domain is the same name and
I
need to correct that? Or something else?
|
|
|
| Back to top |
|
|
Lanwench [MVP - Exchange]
Guest
|
| Posted:
Thu Jan 13, 2005 7:45 am Post subject:
Re: DNS doesn't resolve local web page with same name as dom |
|
|
..:mmac:. wrote:
| Quote: | "Lanwench [MVP - Exchange]"
lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in
message news:O7zxOQO%23EHA.3616@TK2MSFTNGP11.phx.gbl...
.:mmac:. wrote:
In a single location I have two win2k forests and two domains
that have a mutual trust with each other. the LAN is on
forest/domain2 and the webserver email etc are on forest/domain1.
I am having disk space trouble with two machines that are DC's
for domain2 so I put in a third DC (win2k3 not yet AD ) to take the
load while I remove one for rebuilding and upgrading which I
haven't done yet because this happened:
Our web site has the same name as our domain (i.e.domain2.com).
that created a problem where I couldn't surf directly to
domain2.com, I had to use www.domain2.com. I get that and it's OK.
(I know I need to start over with this setup, but I volunteer and
there isn't time in the near future)
You don't actually have to change your internal domain name at all -
what you have is fairly common. And you can't change anything in W2k
anyway, so you'd have to do a total rebuild, and I don't see that
it's worth it.
Except for the 40 machines I have two forests and two domains. With
the same users on each and a trust between them. It seems kinds
pointless to leave it like that.
|
Then you want a total rebuild to flatten your domain model into one domain?
That may make sense.
| Quote: |
The problem I just found is that if I set my
DHCP clients to use a DNS
on Domain2 the web page , with the same name as the domain, is not
found. If I set them to use the DNS on domain1 the page is found
fine. NSlookup resolved to the correct IP using both DNS
servers and I
see no differences int the entries.
Did I stumble onto a problem that I am going to have when I
upgrade the whole thing to win2k3 or is this because the domain is
the same name and I need to correct that? Or something else?
From a client, ping www.domain2.com and see that it's returning the
correct
(public) IP address. If it isn't, check its DNS settings and also try
ipconfig /flushdns. If they ping www.domain2.com and get
xxx.xxx.xxx.xxx returned, they ought to be able to open
www.domain2.com in their browser and
get to it.
I agree with that but the IP resolves properly but the site doesn't
show even if I type in the IP myself. Since I use Host Headers that
sounds like it should happen that way.
|
Then this doesn't sound like a DNS issue at all...
| Quote: | I know that the site wont work without the www in front of it and I
understood that to be the way of things since the domain and web
domain are named the same thing. (I didn't know at the time they
could be different) so I keep leaning that direction.
In all the internal DNS servers, you need to create the www host in
the forward lookup zone and point it at the correct public IP
address - so double check this if you still have problems.
That is correct. But I use Host Headers so there are other web sites
on that IP address. Could that be connected?
|
Maybe, but I wouldn't think so - that isn't my area of expertise, but that's
a webserver thing, not a DNS thing. These are externally hosted websites,
right? All you've told your workstations to do is to go to IP address "x"
when typing in URL "y". That's where the DNS stuff ends....as to the rest, I
can't tell you. If you ping www.domain2.com from a computer on the Internet,
does it return the same public IP, and can you access the website correctly? |
|
| Back to top |
|
|
.:mmac:.
Guest
|
| Posted:
Thu Jan 13, 2005 11:46 am Post subject:
Re: DNS doesn't resolve local web page with same name as dom |
|
|
"Lanwench [MVP - Exchange]"
<lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in message
news:OFdQFKR%23EHA.1452@TK2MSFTNGP11.phx.gbl...
| Quote: | .:mmac:. wrote:
"Lanwench [MVP - Exchange]"
lanwench@heybuddy.donotsendme.unsolicitedmail.atyahoo.com> wrote in
message news:O7zxOQO%23EHA.3616@TK2MSFTNGP11.phx.gbl...
.:mmac:. wrote:
In a single location I have two win2k forests and two domains
that have a mutual trust with each other. the LAN is on
forest/domain2 and the webserver email etc are on forest/domain1.
I am having disk space trouble with two machines that are DC's
for domain2 so I put in a third DC (win2k3 not yet AD ) to take the
load while I remove one for rebuilding and upgrading which I
haven't done yet because this happened:
Our web site has the same name as our domain (i.e.domain2.com).
that created a problem where I couldn't surf directly to
domain2.com, I had to use www.domain2.com. I get that and it's OK.
(I know I need to start over with this setup, but I volunteer and
there isn't time in the near future)
You don't actually have to change your internal domain name at all -
what you have is fairly common. And you can't change anything in W2k
anyway, so you'd have to do a total rebuild, and I don't see that
it's worth it.
Except for the 40 machines I have two forests and two domains. With
the same users on each and a trust between them. It seems kinds
pointless to leave it like that.
Then you want a total rebuild to flatten your domain model into one
domain?
That may make sense.
The problem I just found is that if I set my
DHCP clients to use a DNS
on Domain2 the web page , with the same name as the domain, is not
found. If I set them to use the DNS on domain1 the page is found
fine. NSlookup resolved to the correct IP using both DNS
servers and I
see no differences int the entries.
Did I stumble onto a problem that I am going to have when I
upgrade the whole thing to win2k3 or is this because the domain is
the same name and I need to correct that? Or something else?
From a client, ping www.domain2.com and see that it's returning the
correct
(public) IP address. If it isn't, check its DNS settings and also try
ipconfig /flushdns. If they ping www.domain2.com and get
xxx.xxx.xxx.xxx returned, they ought to be able to open
www.domain2.com in their browser and
get to it.
I agree with that but the IP resolves properly but the site doesn't
show even if I type in the IP myself. Since I use Host Headers that
sounds like it should happen that way.
Then this doesn't sound like a DNS issue at all...
I know that the site wont work without the www in front of it and I
understood that to be the way of things since the domain and web
domain are named the same thing. (I didn't know at the time they
could be different) so I keep leaning that direction.
In all the internal DNS servers, you need to create the www host in
the forward lookup zone and point it at the correct public IP
address - so double check this if you still have problems.
That is correct. But I use Host Headers so there are other web sites
on that IP address. Could that be connected?
Maybe, but I wouldn't think so - that isn't my area of expertise, but
that's
a webserver thing, not a DNS thing. These are externally hosted websites,
right? All you've told your workstations to do is to go to IP address "x"
when typing in URL "y". That's where the DNS stuff ends....as to the rest,
I
can't tell you. If you ping www.domain2.com from a computer on the
Internet,
does it return the same public IP, and can you access the website
correctly?
|
The websites are hosted on a machine on our Lan (actually by the same
machine that is running the current working DNS server) and they were
accessible to the internet during this ordeal. ONLY the the machines using
DHCP that renewed the lease had the problem because I changed the DNS to
this other machine. The ones I left alone, that had static DNS entries to
the old machine or that didn't renew the lease continued to work properly.
Thats why I thought it should be a DNS issue.
The router blocks ICMP traffic so I can't ping the website but the DNS
reports match and I have made no DNS changes for a long time. The only
thing that changed was:
1. Added a new server which was win2003 and had it join the domain.
2. ADPREP/forestprep the schema master in preparation to make this new
machine a DC (wait a minute... I ADPREPed the wrong domain!) But that
shouldn't matter yet I don't think.
3. Changed the order of the DNS servers in the DHCP server to make ip
x.x.x.253 first on the list (x.x.x.27 was the previous entry but was in the
other domain from the clients yet same IP subnet)
Changing the DHCP setting to put the x.x.x.27 server back on top solved the
issue.
Four notes:
1.x.x.x.253 server is part of the same AD domain that the website is named
after, i.e. domain2.com
2. the DNS server x.x.x.27 that works is not part of that domain. it is part
of domain1.com
3. No other web sites are affected except the one with the same name as our
AD domain.
4. Internet could always see the website.
This is tied to that DNS machine somehow. I feel it in my bones! |
|
| Back to top |
|
|
John Smith
Guest
|
| Posted:
Thu Jan 13, 2005 7:52 pm Post subject:
Re: DNS doesn't resolve local web page with same name as dom |
|
|
if this is a winnt/2k/2k3 server, install network monitor and look at the
packets to see if they reveal anything.
On Wed, 12 Jan 2005 09:46:06 -0800, .:mmac:. wrote:
| Quote: | In a single location I have two win2k forests and two domains that have
a mutual trust with each other. the LAN is on forest/domain2 and the
webserver email etc are on forest/domain1.
I am having disk space trouble with two machines that are DC's for
domain2 so I put in a third DC (win2k3 not yet AD ) to take the load while I
remove one for rebuilding and upgrading which I haven't done yet because
this happened:
Our web site has the same name as our domain (i.e.domain2.com). that
created a problem where I couldn't surf directly to domain2.com, I had to
use www.domain2.com. I get that and it's OK. (I know I need to start over
with this setup, but I volunteer and there isn't time in the near future)
The problem I just found is that if I set my DHCP clients to use a DNS
on Domain2 the web page , with the same name as the domain, is not found. If
I set them to use the DNS on domain1 the page is found fine.
NSlookup resolved to the correct IP using both DNS servers and I see no
differences int the entries.
Did I stumble onto a problem that I am going to have when I upgrade the
whole thing to win2k3 or is this because the domain is the same name and I
need to correct that? Or something else? |
|
|
| Back to top |
|
|
.:mmac:.
Guest
|
| Posted:
Thu Jan 13, 2005 11:09 pm Post subject:
Re: DNS doesn't resolve local web page with same name as dom |
|
|
that makes sense, I'll try that. I may have to post with the result, I'm not
certain I will understand all that I will see from network monitor.
"John Smith" <jsmith@macroshaft.com> wrote in message
news:pan.2005.01.13.13.52.30.721689@macroshaft.com...
| Quote: | if this is a winnt/2k/2k3 server, install network monitor and look at the
packets to see if they reveal anything.
On Wed, 12 Jan 2005 09:46:06 -0800, .:mmac:. wrote:
In a single location I have two win2k forests and two domains that
have
a mutual trust with each other. the LAN is on forest/domain2 and the
webserver email etc are on forest/domain1.
I am having disk space trouble with two machines that are DC's for
domain2 so I put in a third DC (win2k3 not yet AD ) to take the load
while I
remove one for rebuilding and upgrading which I haven't done yet because
this happened:
Our web site has the same name as our domain (i.e.domain2.com). that
created a problem where I couldn't surf directly to domain2.com, I had to
use www.domain2.com. I get that and it's OK. (I know I need to start over
with this setup, but I volunteer and there isn't time in the near future)
The problem I just found is that if I set my DHCP clients to use a
DNS
on Domain2 the web page , with the same name as the domain, is not found.
If
I set them to use the DNS on domain1 the page is found fine.
NSlookup resolved to the correct IP using both DNS servers and I see
no
differences int the entries.
Did I stumble onto a problem that I am going to have when I upgrade
the
whole thing to win2k3 or is this because the domain is the same name and
I
need to correct that? Or something else?
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in