DNS HELP?!
just1...@yahoo.ca
mydomain.com
mydomain.local uses Active Directory DNS where as mydomain.com is hosted
with our ISP.
Now, the website for mydomain.com is hosted on a server within
mydomain.local but from any PC/Server within that domain I can't access
www.mydomain.com.
Make sense? Any ideas?
mote
<just1...@yahoo.ca> wrote in message
news:OPBw$IWgEH...@tk2msftngp13.phx.gbl...
Zoltan Fekete
Your problem has nothing to do with your DNS, as your external and internal
domain names are different, and your external DNS records are hosted by
your ISP.
Best regards,
--
Zoltan Fekete <zol...@neobee.net>
Microsoft Certified Professional
YU Spin d.o.o. Novi Sad - http://www.yuspin.co.yu
NetSee Network Utility - http://yuspin.metrohive.net/netsee
Sharad Naik
on public IP, within his LAN.
He should add zone www.hisdomain.com , blank record pointing the private
address of the web server.
Sharad
"Zoltan Fekete" <zol...@neobee.net> wrote in message
news:w1t51jciou2x$.12fwazp7t6106.dlg@40tude.net...
Roger Abell
provide the webs intrenal address.
Whether, getting the public IP from the ISP hosted DNS
zone for mydomain.com, and they browsing to this from
inside, through the proxy and/or firewall to the network
outside and get routed back in as any other external client
does, whether this works or not depends on the brand and
way the proxy and/or firewall is configured (apparently
some brands just cannot be simple configured to allow).
--
Roger Abell
Microsoft MVP (Windows Server System: Security)
MCSE (W2k3,W2k,Nt4) MCDBA
"Sharad Naik" <shara...@nospam-vsnl.net> wrote in message
news:%23%23LH7hd...@TK2MSFTNGP09.phx.gbl...
Jonathan de Boyne Pollard
SN> access the web site on public IP, within his LAN.
I was just about to point out that he had said that his web-site was
hosted by an external hosting company, so that wouldn't apply, when I
realised that I had mis-read his post the first time around. (-:
That's the other possibility, yes.
Jonathan de Boyne Pollard
Only if, contrary to what you state, you are in fact using
"mydomain.com." with Active Directory, either in addition to or instead
of "mydomain.local.".
Ace Fekay [MVP]
Sharad Naik <shara...@nospam-vsnl.net> made a post then I commented below
> If he has firewall / NAT set up he will not be able to access the web
> site on public IP, within his LAN.
> He should add zone www.hisdomain.com , blank record pointing the
> private address of the web server.
>
> Sharad
This was multiposted (rather than cross-posted) and Kevin replied in the
win2000.dns group with the same exact answer.
--
Regards,
Ace
Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.
This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services
Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
--
=================================
just1...@yahoo.ca
> In news:%23%23LH7hd...@TK2MSFTNGP09.phx.gbl,
> Sharad Naik <shara...@nospam-vsnl.net> made a post then I commented below
>
>>If he has firewall / NAT set up he will not be able to access the web
>>site on public IP, within his LAN.
>>He should add zone www.hisdomain.com , blank record pointing the
>>private address of the web server.
>>
>>Sharad
>
>
> This was multiposted (rather than cross-posted) and Kevin replied in the
> win2000.dns group with the same exact answer.
>
So, for each website hosted on the internal servers I should have a zone
for that site and a blank record pointing to the private IP of the server?
Does Windows DNS support wildcards too? Like *.domain.com ?
Ace Fekay [MVP]
just1...@yahoo.ca <just1...@yahoo.ca> made a post then I commented below
>
> So, for each website hosted on the internal servers I should have a
> zone for that site and a blank record pointing to the private IP of
> the server?
>
> Does Windows DNS support wildcards too? Like *.domain.com ?
Yes it does support wildcards, but you can get in trouble using them. I
suggest not to.
But that's the idea. How many zones do you have?
ca.yahoo@just1coder
Could you explain why internal DNS is required too?
I thought that since it was hosted externally, it would be ok?!
Apparently not.
Ace Fekay [MVP]
ca.yahoo@just1coder <ca.yahoo@just1coder> made a post then I commented below
If you are hosting a webserver internally to the outside world, then the
external DNS is pointing to the WAN IP of your NAT/Router. The router in a
NAT scenario such as this is port remapping por 80 to the internal private
IP. That is how the external users get to it.
For internal users, if it resolves to the outside WAN IP, NAT cannot, cannot
port remap an internal request to the outside interface and back in again to
the internal resource. Hence, why you have to manually create the record
internally using the private IP address.
Just a limitation of NAT, no matter who makes the device...
Hope that helps.
ca.yahoo@just1coder
Ace Fekay [MVP]
ca.yahoo@just1coder <ca.yahoo@just1coder> made a post then I commented below
> Yes, that makes perfect sense. Thanks Ace.
My pleasure!
Ashish Ranjan Tiwary
1. The local DNS
2. The ISP's DNS.
The DNS in your Active Directory is authoritative for your local name
lookups, but your .com domain - even though hosted internally, gets its
IP/DNS from the ISP.
That is why your local machines are unable to look it up.
The best way is to configure a forwarder on your .local DNS so that any
addresses in the .com domain are looked up via the ISP. There is an article
to configure the same on the support website, and the address is:
How To Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202
There is a description to configure the forwarders towards the bottom middle.
Hope it helps out.
:)