You can still use your former ISP's DNS records while using the new ISP's
bandwidth. It does not matter who owns the DNS server. Everybody have access
to it once they are in the internet. Except when they are specifically
filtered.
The only drawn back is that, Your new ISP have to forward the
Any decent ISP will refuse DNS recursion from any IP address that is not
within its own address space. This is fundamental to DNS security.
You need to rewrite the destination IP address. Note that Cisco's NAT
is not suitable for this because of the DNS ALG. The easiest thing to
do may be
At 05:11 AM 2/18/02, Godswill HO wrote:
You can still use your former ISP's DNS records while using the new ISP's
bandwidth. It does not matter who owns the DNS server. Everybody have access
to it once they are in the internet. Except when they are specifically
filtered.
The only drawn back is
hhmmm.
as I understand the original question, each workstation in the network in
question is hard coded for DNS.
So, if for example, my machine is hard coded for DNS server 207.126.96.162
( my ISP DNS server ) and I change ISP's, and make no changes to my
workstation, then any DNS request
At 12:28 PM 2/18/02, Marc Thach Xuan Ky wrote:
Any decent ISP will refuse DNS recursion from any IP address that is not
within its own address space.
He wasn't asking about recursion. He was asking about the initial query
from the end host. Although I could believe you that a service provider
the simple way to test this would be to set your workstation with some other
ISP's DNS address, and see how things go. In one of my posts I provided the
real IP of an active DNS server. Someone want to give it a try? or post one
that you know about. I'll be happy to test.
I wish the guy who
:[EMAIL PROTECTED]]
Sent: Monday, February 18, 2002 13:16
To: [EMAIL PROTECTED]
Subject: Re: DNS Request Redirection [7:35703]
hhmmm.
as I understand the original question, each workstation in the network
in
question is hard coded for DNS.
So, if for example, my machine is hard coded for DNS
Yes, I can use that DNS server that you mentioned without any problem. I
have my PC set to use it right now. And I know of others that anyone can
use too, but I'm not going to give details in case they would not like this
info to get out. ;-)
Priscilla
At 03:24 PM 2/18/02, Chuck wrote:
the
thanks, Cil.
I guess we can lay this one to rest. the network in question probably needs
make no changes and life will be dandy.
Chuck
Priscilla Oppenheimer wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
Yes, I can use that DNS server that you mentioned without any problem. I
Thanks for everyone who responded.
I did some testing and here is what I found.
Our current ISP's DNS is not reachable from the outside world it seems that
we use an internal DNS server which then forwards the request to the
internal side of there firewall which forwards to there external DNS
not to add any heat underneath anyone behind, but I routinely use
UUNET/Mindspring/Earthlink/Qwest... (their caching of course)
to be honest with you, I have never run into an isp that wouldn't allow
lookups from external hosts... I mean...for authoratative servers, how
would you propagate
And to add one more point Filtering for queries just from root servers
wouldn't work either. It's not the root server that sends the query. The
root server responds to the requesting server with the address of the
authoritative server for a name. Then the requesting server asks the
]]
Sent: Monday, February 18, 2002 2:25 PM
To: [EMAIL PROTECTED]
Subject: Re: DNS Request Redirection [7:35703]
the simple way to test this would be to set your workstation with some other
ISP's DNS address, and see how things go. In one of my posts I provided the
real IP of an active DNS server
Oh, sorry, I misunderstood his comment about forwarding. Yes, the new ISP
has to send the packets to the old ISP because the users are using the old
ISP's DNS server. As you say, this should work unless the old ISP denies
requests coming from sources outside its IP address range. (And that may
Recursion is precisely what he was concerned about. As you have
alluded, there are two roles for a DNS server, cacheing (which requires
recursion), and authoritataive. An ISP does not need to publish the
addresses of a authoritative nameserver, those addresses are stored in
the distributed
]]
Sent: Monday, February 18, 2002 13:16
To: [EMAIL PROTECTED]
Subject: Re: DNS Request Redirection [7:35703]
hhmmm.
as I understand the original question, each workstation in the network
in
question is hard coded for DNS.
So, if for example, my machine is hard coded for DNS server
g server a spin, and let us know if it fails
certain queries.
Mark
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Monday, February 18, 2002 2:25 PM
To: [EMAIL PROTECTED]
Subject: Re: DNS Request Redirection [7:35703]
the simple way to test this would b
I have been re-reading the posts again and I have one question.
I believe what Chuck says is true about NAT outbound changes the source
address, not the destination address.
So
Would it be possible to change the destination address on the inbound side ?
For example.
Let say I have a web
I think what you are talking about is a static nat ( conduit, in Cisco
speak )
It's done all the time, for just the reason you mention. any device for
which you want / need a single internet face, use a static NAT.
Chuck
Michael Hair wrote in message
[EMAIL PROTECTED]">news:[EMAIL
consider that the DNS request packet has a destination address of the server
of your former ISP. what you are trying to accomplish, if I understand you
correctly, is to change that destination address. Policy routing can change
the next hop, but it cannot change the destination IP of the packet
20 matches
Mail list logo
