DNS Prob.

[Mahmoud]

Hi All, I was having Domain controller that holding the DNS Server ( DNS
Server IP is 62.140.72.40) of my Domain, and I Have a leased line ( the DNS
Server IP of my ISP is 62.140.76.16), all Clients ( are win2000 Pro.) were
have the following settings in the DNS Section of the TCP/IP properties

Preferred DNS Server : 62.140.72.40
Alternate DNS Server : 62.140.76.16

Everything was working fine, I just reformatted my Server and installed the
new one, I set the same settings but the internet now doesn't work when I
set the 62.140.76.16 to be the Preferred DNS ( which is the DNS Server of
the ISP or Internet DNS ) and make the Active directory DNS 62.140.72.40 be
the alternate one Internet working just for some minutes then " the page
cannot be found due to a DNS problem"
Now, I removed the Alternete DNS and make the Internet DNS (ISP DNS) only on
the preferred DNS, Internet is working fine but the clients cannot change
thier passwords.
What can I do ?

 

[Jonathan de Boyne Pollard]

M> Preferred DNS Server : 62.140.72.40
M> Alternate DNS Server : 62.140.76.16

<URL:http://homepages.tesco.net./~J.deBo...nt-all-proxies-must-provide-same-service.html>

 

[Larry Brasher]

Hello All,

Active Directory with DNS on the same server.

TCP/IP settings

1.)Right click "My network places" and select properties.
2.)For the LAN connection right click and select properties.
3.)On the properties page double click TCP/IP
4.)At the bottom of the protocols page select Preferred DNS Server option
and enter the IP address for the server itself.
5.)Click the advanced button. In the advanced setting make sure the
"Register this connection's address in DNS" selection is checked at the
bottom of the display.

DNS settings

1.)Open up the DNS console.
2.)Once opened, right click on the server in the right hand pane and select
properties.
3.)Once the properties page is up, select the "Forwarders" tab.
4.)Check the "Enable forwarders" selection at the top.
5.)Add the IP address of the DNS in which to forward requests. If this is
the only DNS , add the IP address for the ISP's DNS. (note- In the TCP/IP
settings, we selected the choice for DNS to point to itself. If name
resolution cannot be resolved then a request is made to the forwarders. If
resolution cannot be made via the internal DNS and there are no forwarders
listed, then no resolution will be made at all.)
6.)Click OK.
7.)Expand the "Forward Lookup Zones"
8.)If there is a folder with a dot "." listed then delete it. (note- This
indicates to the server that it is the root server, which means do not go
beyond this server for name resolution.)
9.)Right click the domain folder and select properties. Make sure that
"Allow dynamic updates is selected."

Close out the DNS console.

Open up a command prompt and type the following:

1.)At the prompt type ipconfig /flushdns and wait for the services to
flush.
2.)ipconfig /registerdns wait for the services to regiser.
3.)net stop netlogon
4.)net start netlogon

If you receive an error during this process go to control panel, admin.
tools, services. Make sure the DHCP client service is started, even if
they are not using DHCP they still need the service started. Once all of
this is done. Open the DNS console again. Expand the forward lookup zones,
then expand the domain folder. You should see the underscore folders below:

_msdcs
_sites
_tcp
_udp

If you see these, then all is right with the world.


Shane Brasher
MCSE (2000,NT),MCSA, A+
Microsoft Platforms Support
Windows NT/2000 Networking

 

[Jonathan de Boyne Pollard]

LB> Hello All,

There are two problems with the article that you are copying and pasting into
several threads in this newsgroup, with the signature of a Microsoft support
person.

The first problem is that the article gives explicit instructions to enable
forwarding, and then states that if there's no forwardee then "no resolution
will be made at all". That's not true. If root hints are present, query
resolution is enabled (i.e. the egregiously misnamed "do not use recursion"
option is disabled), and the appropriate IP connectivity is present, query
resolution will occur.

The fact that employing forwarding is not required has been thrashed out at
length in this forum several times. It doesn't help for articles with the
stamp of Microsoft upon them to create confusion by implying that it is.

The second is that the article is very badly written. For example:

LB> If name resolution cannot be resolved then a
LB> request is made to the forwarders.

should read

LB*> If the answer is not already in the local DNS
LB*> database or cache, then the request is forwarded
LB*> by this DNS server to the listed DNS server(s).

(which is more akin to what the Microsoft DNS server documentation itself
states, and which doesn't embody the nonsense concept of "name resolution
being resolved");

LB> Make sure that "Allow dynamic updates is selected."

should read

LB> Make sure that "Allow dynamic updates" is selected.

; and

LB> 5.)Add the IP address of the DNS in which to forward
LB> requests. If this is the only DNS , add the IP
LB> address for the ISP's DNS.

should (at the very least, and setting aside for now the implication of the
very existence of this step that using forwarding is mandatory) read

LB*> 5.) Add the IP address of the DNS server to which
LB*> requests are to be forwarded. If you have no such
LB*> DNS server of your own, add the IP address of the
LB*> DNS server that is provided to you by your ISP
LB*> for such use.

Who wrote this article ? Was it Microsoft ? Was it proof-read ? Why did
whoever wrote it not consult the Microsoft DNS server product documentation ?