Re: Non authoritative domain on Windows Server 2003
- From: "Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx>
- Date: Tue, 31 Oct 2006 14:00:42 -0000
Hi
If I understand you correctly you want that your internal DNS server resolve your public domain to the private IPAddress, correct?
If yes all you have to do is to create an
Primary Zone, and create the records that point to the private internal Ip address of your Domain.
--
I hope that the information above helps you
Good Luck
Jorge Silva
MCSA
Systems Administrator
"Chino" <chino75@xxxxxxxxxxxxx> wrote in message news:ei7dak$2jp$1@xxxxxxxxxxxxxxxxxxxxxxx
Hi all.
I'm not confident with DNS in general, but I have to find a way to do this:
I'm in a LAN using a Windows Server 2003 as the primary DNS.
We have Mail and Web servers using public addresses, when someone check for www.ourdomain.it or mail.ourdomain.it from ouside the LAN, they get the servers' public addresses from our provider authoritative DNS.
That is ok.
When we check look for www.ourdomain or mail.ourdomain.it from inside the LAN, we also get the public addresses from our internal DNS.
That's not ok. We should get our servers' private IP addresses.
How can I configure our internal DNS to do the job?
Should I add ourdomain.it on the DNS as a stub one?
If I only add a host(A), I do not resolve the problem, as the server automatically add the ourdomain.locale suffix to the address.
Could someone point me at the right documentation, or tell how to have this working if it's simple?
thank you very much.
.
- Follow-Ups:
- Prev by Date: Re: DNS dynamic update pending in DHCP
- Next by Date: Re: UDP Not Getting Though
- Previous by thread: Re: DNS dynamic update pending in DHCP
- Next by thread: Re: Non authoritative domain on Windows Server 2003
- Index(es):
Relevant Pages
|
