Re: Help
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Fri, 1 Feb 2008 13:30:22 -0600
"Mack" <estatebarnes@xxxxxxxxx> wrote in message
news:8ab9962e-fb6b-445d-9e34-193bbda1a1ae@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I am having one problem with the DNS server and I'm sure there's a
simple solution. The sites that I'm hosting on the server it works
great with, but I have sites that are on a server outside of this
network and when I point the site in DNS to their IP it doesn't work.
I will explain below in an example.
Say I have a forward lookup zone for mydomain.com, I have a "Host A"
and pointing to private IP on the server 192.168.1.xx and it works
find inside the network and outside the network. So when I'm at home I
can type in the web address and it converts it to the public IP of the
server and when I'm in the network it just points it to 192.168.1.xx.
DNS Clients cannot point to "different" DNS servers (at the same time)
effectively but MUST point to ONLY the DNS Server(s) which resolve
ALL of the addresses they will every need and resolve them to addresses
(internal or external) which they can use.
When you MOVE a client from one network to another and need to
change the DNS server(s) used then you must ensure that EVERY DNS
server the clients (now) use can do these same resolutions (or the
resolutions that are NOW appropriate for the moved client.)
But the problem occurs when I point a "Host A" for the same thing and
point it to an outside server where the site is hosted with the public
IP eq 67.XX.XX.XX and it won't work, I do a nslookup and it times out
(Note I'm doing this outside the network at home) but on the server
itself (Inside the network) I do a nslookup and it point to
67.XX.XX.XX accurately (Note when I'm at home doing the above test, I
have also tried setting up my internet to connect to the server as its
DNS). So in other words everything works for sites hosted inside the
network, but if the siteis hosted outside the network and I need to
put in a public IP for (Backup Server) the DNS does not work. I know
there has to be a step I'm missing and if someone can help that would
be great. If you have any suggestions please let me know, I will
continue to try and figure something out.
When a DNS Server (in either case) doesn't "know" some of the correct
answers then the DNS SERVER must be fixed to find those answers with
one or more of the following methods:
1) Forward the requests the DNS server cannot answer to another
DNS server which can perform the resolution
2) Add the required Zone(s) to the DNS Server directly
If you use method #1 this means that the Forwarder must now follow
this rule too (except that anything resolved by the previous DNS server
doesn't also need to be available to the forwarder.)
That is really it -- it is not clear where your particular problem is
happening
(or precisely what that problem really is) from your description, but IF
you follow the above simple rules FAITHFULLY then you MUST solve
the problem or find that it is not possible to do so (and know why.)
--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com (phone on web site)
If you use LinkedIn then tell me where you know me from when linking:
http://www.linkedin.com/in/herbmartin
.
- References:
- Help
- From: Mack
- Help
- Prev by Date: Re: Monitor
- Next by Date: Re: DNS Restart to Access Internet
- Previous by thread: Help
- Next by thread: Re: [Domain name] is not accessible.
- Index(es):
Relevant Pages
|
