DNS issue

[dst0202]

recently we upgraded to an active directory domain from a
workgroup. after changing I was recieving DNS errors>
afterward I contacted my ISP and they reassigned new DNS
primary and alternative. After changing the numbers I am
unable to view certain webpages. I can successfully ping
one of the DNS numbers and tacert works. The alternative
number does not ping or tracert. When I try to ping the
IP numbers that our domain resides on ping works but
tracert times out after leaving the garteway. The primary
DNS on the Active Directory is the IP of the server then
listed oare the other DNS numbers that were given to me
from our ISP. Our ISP claims that it is not an issue with
them.??
Any suggestions and/or comments are appreciated.

 

[Kevin D. Goodknecht [MVP]]

In

recently we upgraded to an active directory domain from a
workgroup. after changing I was recieving DNS errors>
afterward I contacted my ISP and they reassigned new DNS
primary and alternative. After changing the numbers I am
unable to view certain webpages. I can successfully ping
one of the DNS numbers and tacert works. The alternative
number does not ping or tracert. When I try to ping the
IP numbers that our domain resides on ping works but
tracert times out after leaving the garteway. The primary
DNS on the Active Directory is the IP of the server then
listed oare the other DNS numbers that were given to me
from our ISP. Our ISP claims that it is not an issue with
them.??
Any suggestions and/or comments are appreciated.

The issue is that your ISP advised you to put their DNS servers in your NIC
setup. Remove them from the NIC then put them in DNS as forwarders. You must
only use your local DNS on all AD domain members, even if you only have one
local. Just guessing you did not delete the root "." forward lookup zone in
your DNS so your local DNS won't resolve internet names. If you delete the
"." zone then you can use your ISP's DNS as forwarders.
Read this, 300202 - HOW TO: Configure DNS for Internet Access in Windows
2000
http://support.microsoft.com/?id=300202&FR=1

 

[Michael Johnston [MSFT]]

The AD server should ONLY point to itself for DNS. Do not point the server to your ISP for DNS in the TCP/IP settings. In the
DNS MMC, configured forwarders on the DNS service to the ISP. That will solve both problems.

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.

 

[dst]

-----Original Message-----
The AD server should ONLY point to itself for DNS. Do

not point the server to your ISP for DNS in the TCP/IP
settings. In the

DNS MMC, configured forwarders on the DNS service to the

ISP. That will solve both problems.

Thank you,
Mike Johnston
Microsoft Network Support

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.



.
when I remove the TCP/IP settings will there be a break

in the communication link? Is this something that should
be done outside normal work hours?

 

[Kevin D. Goodknecht [MVP]]

In

not point the server to your ISP for DNS in the TCP/IP
settings. In the
ISP. That will solve both problems.
confers no rights. Use of included script samples are
subject to the
responses to this message are best directed to the
newsgroup/thread from
in the communication link? Is this something that should
be done outside normal work hours?

You can Change DNS servers on the fly. Just point it to itself.

 

[dst]

-----Original Message-----
In

You can Change DNS servers on the fly. Just point it to itself.




.
So let me get this straight. TCP/IP settings, DNS should

only have the IP of the actual server. DNS forwarders
should list the ISP numbers. ALl this can be done during
work hours? Thanks, I am new to DNS.

 

[Kevin D. Goodknecht [MVP]]

In

only have the IP of the actual server. DNS forwarders
should list the ISP numbers. ALl this can be done during
work hours? Thanks, I am new to DNS.

Yes, it can. About the only thing that will cause the NIC to disconnect is
changing the configuration of the NIC itself, such as drivers and link type.
Point it to the IP of the local DNS server, even if it is the IP of the same
NIC on the server with DNS installed.