DNS moving ISP

  • Thread starter Thread starter Jack Jones
  • Start date Start date
J

Jack Jones

Hey,
We are thinking about moving to another ISP to increase bandwidth,
the only concern I have is in relation to our internal DNS server, currently
it is set up with an internal IP address and looks to the ISP's DNS server
and we transfer info etc. If we move ISP will there be any implications with
DNS, i.e can I just change the DNS setting on my DNS servers' NIC and the
rest will fall into place?

We use Windows 2000 DNS/

Thanks
 
In
Jack Jones said:
Hey,
We are thinking about moving to another ISP to increase
bandwidth, the only concern I have is in relation to our internal DNS
server, currently it is set up with an internal IP address and looks
to the ISP's DNS server and we transfer info etc. If we move ISP will
there be any implications with DNS, i.e can I just change the DNS
setting on my DNS servers' NIC and the rest will fall into place?

We use Windows 2000 DNS/

Thanks
Click to expand...

Not sure what you are talking about here but if this is an AD domain all
NICs should be using the internal DNS including the DNS server itself. Then
in the DNS server properties you can optionally use your ISP's DNS as a
forwarder. Even in a non-AD network there is no real reason to use your
ISP's DNS, you should still use your local DNS at least for caching
purposes.
300202 - HOW TO Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202&FR=1
 
Kevin,
Currently I have all internal clients pointing to my internal DNS
server. The DNS server itself is pointing to my ISP's DNS server - all seems
to be working fine - how bad is this??

Thanks
 
If you are not using the active directory, this shouldn't be a problem but it's a recommended configuration. But if you have an Active Directory, this will be a
problem. This machine should point to itself only for DNS and all clients should point at this DNS server only as well. Then in the DNS server service you can
configure forwarders to your ISP or if you choose, you can use root hints which is the default. The prefered method would be to forward to your ISP in the DNS
server service properties. If the ISP changes, just change the forwarders list in the DNS server and everything will continue to work. If you don't use forwarders,
root hints will work no matter what ISP you use with no configuration changes.

Thank you,
Mike Johnston
Microsoft Network Support

--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
 
In
Jack Jones said:
Kevin,
Currently I have all internal clients pointing to my internal
DNS server. The DNS server itself is pointing to my ISP's DNS server
- all seems to be working fine - how bad is this??
Click to expand...
If the DNS server is a member of an Active Directory domain it would be
unable to register its address in the domain. If DNS is on a Domain
controller it is not good unless it is multihomed with multiple interfaces,
but unless dynamic registration is disabled it is certainly trying to
register in the ISP's DNS.

To answer this correctly I would have to know if DNS is running on a DC and
if it is multihomed.
 
OK,
The DNS server is part of AD and is NOT the DC or multihomed,. Strange,
I set this up about a year ago and don't /didn't have any problems - are
there any implications of changing this now? i.e adding the DNS server
setting on the internal DNS to itself and then adding a forward in its DNS
console?

Thanks
 
In
Jack Jones said:
OK,
The DNS server is part of AD and is NOT the DC or multihomed,.
Strange, I set this up about a year ago and don't /didn't have any
problems - are there any implications of changing this now? i.e
adding the DNS server setting on the internal DNS to itself and then
adding a forward in its DNS console?

Thanks
Click to expand...
If this is a Member of your AD domain then it should point to it own
address, if on the other hand it is a standalone server just hosting the
zone for the AD Domain then it would not matter because it would not need to
register its addresses in DNS or find the domain controller.
You see, by being a domain member when you logon using domain credentials it
will need to find the domain controller in DNS, if it is using the ISP's DNS
it won't find the domain controller in the ISP DNS server.

You can verify this by running netdiag /v from the machine
 
Kevin,
I ran netdiag and believe it or not the setup is as follows:

This Windows2000 DNS box is a memeber server of the AD.
The DNS entry for its one and only connected network card is the external
address of my ISP's DNS server
All internal clients have their DNS entry on their NIC set to the internal
address of my DNS server.
The DNS server is auththenticating no problem daily to the DC running
AD?????

Is this possible and if so what problem is this causing me?

Thanks for the help.
 
In
Jack Jones said:
Kevin,
I ran netdiag and believe it or not the setup is as follows:

This Windows2000 DNS box is a memeber server of the AD.
The DNS entry for its one and only connected network card is the
external address of my ISP's DNS server
All internal clients have their DNS entry on their NIC set to the
internal address of my DNS server.
The DNS server is auththenticating no problem daily to the DC running
AD?????

Is this possible and if so what problem is this causing me?
Click to expand...

I don't exactly know how it is doing it. what does the DNS test portion of
the output show?
To do just the DNS test run netdiag /test:dns /v
But the machine should only be pointing to its own address. Having it point
to the ISP is not going to help DNS in any way, it is only going to cause
errors and poor performance connecting to internal machines, if it can
access the internal machines. That is unless your ISP has a zone for your AD
domain or is resolving your AD domain.
 
Back
Top