PROVIDER ISP - DNS - FORWARDING ?

[Maarten]

I am a hosting provider. I've got DNS installed on a windows 2000 server.
Each domain extension has its own Primary Zone eq:

NL - Zone

----- Test

----------WWW

-----Example

----------WWW



Com - Zone

----- Test

----------WWW

-----Example

----------WWW

etc.

This is also the structure microsoft advises for a secondary DNS server.
This because there are only a few DNS Zone Replications to be synchronized.

When i try to connect to internet, all clients/servers connect to the Local
Dns Server. De local Dns Server should forward the DNS request when it's not
possible to resolve de dns request locally. But when i try to resolve
NotMyDomain.NL it doesnt forward it anymore because the zone NL exist
locally.

Does anyone have a solution or do i have to make a different zone for each
of the domains i am hosting (approximitly 1000??)

 

[Ace Fekay [MVP]]

In

I am a hosting provider. I've got DNS installed on a windows 2000
server. Each domain extension has its own Primary Zone eq:

NL - Zone

----- Test

----------WWW

-----Example

----------WWW



Com - Zone

----- Test

----------WWW

-----Example

----------WWW

etc.

This is also the structure microsoft advises for a secondary DNS
server. This because there are only a few DNS Zone Replications to be
synchronized.

When i try to connect to internet, all clients/servers connect to the
Local Dns Server. De local Dns Server should forward the DNS request
when it's not possible to resolve de dns request locally. But when i
try to resolve NotMyDomain.NL it doesnt forward it anymore because
the zone NL exist locally.

Does anyone have a solution or do i have to make a different zone for
each of the domains i am hosting (approximitly 1000??)

You would have to make a different zone for each, such as test.nl,
example.nl, etc. What you did is effectively controlled ALL domains under
the "nl" TLD. Same with the 'com" and any other you created.

I don't believe that Microsoft would ever recommend such as method as you
did. This is not the norm unless you are trying to control access, such as
the results you are experiencing. On a secondary, you would just create the
test.nl zone, and give it the IP address of the DNS server that hosts the
Master zone.

You can use DNSCMD to possibly script the 1000 zones you have to change them
(found in the WIndows 2000 Support Tools on the CDROM).


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

 

[Jonathan de Boyne Pollard]

M> Does anyone have a solution or do i have to make a
M> different zone for each of the domains i am hosting
M> (approximitly 1000??)

You shouldn't really be using your public content DNS server for proxy DNS
service. So the proper solution is to set up a separate proxy DNS server
and use that for proxy DNS service. Then you can leave your content DNS
server exactly as it currently is, since then it won't matter that it has
extraneous information in its database.

<URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/dns-monolithic-server-as-content.html>