How do my server 2003 (DNS) know the Internet?

I am playing with DNS on server 2003. The machine is multihomed only to gain
access to another network which do not require internet access. We already
have Internet access through a DSL router and will be using it as it is by
making it the Default Gateway for the clients.

So I have two NICS. One for Network A and the other for network B. Network B
needs to be managed through the Server 2003 Machine. This server will also
be a DC in the near future. Currently I have made this one as a DHCP and a
DNS Server. The clients get their IP configuration automatically from this
machine through DHCP.

On setting up DNS I have not specified any Nameserver to look for to resolve
Internet names. But the clients have no problem getting in to websites.

Now the question.

Please can someone give me a hint on why my clients and I (This Server 2003
machine) are able to resolve internet names..

Here is part of my netsh diag gui output in case

- Network Adapters PASSED
- [00000001] Intel(R) PRO/1000 MT Dual Port Network Connection
(PASSED)
DHCPEnabled = FALSE
DNSEnabledForWINSResolution = FALSE
DNSHostName = ptcr-dc1
DomainDNSRegistrationEnabled = FALSE
FullDNSRegistrationEnabled = TRUE
Index = 1
InterfaceIndex = 65539
+ IPAddress = 128.1.5.10 (PASSED)
Pinging 128.1.5.10 with 32 bytes of data:
Reply from 128.1.5.10: bytes=32 time<1ms TTL=0
Reply from 128.1.5.10: bytes=32 time<1ms TTL=0
Reply from 128.1.5.10: bytes=32 time<1ms TTL=0
Reply from 128.1.5.10: bytes=32 time<1ms TTL=0
Ping statistics for 128.1.5.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
IPConnectionMetric = 1
IPEnabled = TRUE
IPFilterSecurityEnabled = FALSE
IPSecPermitIPProtocols = 0
IPSecPermitTCPPorts = 0
IPSecPermitUDPPorts = 0
IPSubnet = 255.255.0.0
IPXEnabled = FALSE
MACAddress = 00:0D:60:EC:89:20
ServiceName = E1000
SettingID = {6ED33CBD-1748-440C-835B-BEC20A961309}
TcpipNetbiosOptions = 0
WINSEnableLMHostsLookup = TRUE
- [00000002] Intel(R) PRO/1000 MT Dual Port Network Connection
(PASSED)
Caption = [00000002] Intel(R) PRO/1000 MT Dual Port Network
Connection
DatabasePath = %SystemRoot%\System32\drivers\etc
+ DefaultIPGateway = 156.40.10.1(Same Subnet) (PASSED)
Pinging 156.40.10.1 with 32 bytes of data:
Reply from 156.40.10.1: bytes=32 time=1ms TTL=1
Reply from 156.40.10.1: bytes=32 time<1ms TTL=0
Reply from 156.40.10.1: bytes=32 time<1ms TTL=0
Reply from 156.40.10.1: bytes=32 time=1ms TTL=1
Ping statistics for 156.40.10.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
Description = Intel(R) PRO/1000 MT Dual Port Network Connection #2
DHCPEnabled = FALSE
DNSEnabledForWINSResolution = FALSE
DNSHostName = ptcr-dc1
+ DNSServerSearchOrder = 156.40.10.10 (PASSED)
Pinging 156.40.10.10 with 32 bytes of data:
Reply from 156.40.10.10: bytes=32 time<1ms TTL=0
Reply from 156.40.10.10: bytes=32 time<1ms TTL=0
Reply from 156.40.10.10: bytes=32 time<1ms TTL=0
Reply from 156.40.10.10: bytes=32 time<1ms TTL=0
Ping statistics for 156.40.10.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
DomainDNSRegistrationEnabled = FALSE
FullDNSRegistrationEnabled = TRUE
GatewayCostMetric = 2
Index = 2
InterfaceIndex = 65540
+ IPAddress = 156.40.10.10 (PASSED)
Pinging 156.40.10.10 with 32 bytes of data:
Reply from 156.40.10.10: bytes=32 time<1ms TTL=0
Reply from 156.40.10.10: bytes=32 time<1ms TTL=0
Reply from 156.40.10.10: bytes=32 time<1ms TTL=0
Reply from 156.40.10.10: bytes=32 time<1ms TTL=0
Ping statistics for 156.40.10.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
IPConnectionMetric = 1
IPEnabled = TRUE
IPFilterSecurityEnabled = FALSE
IPSecPermitIPProtocols = 0
IPSecPermitTCPPorts = 0
IPSecPermitUDPPorts = 0
IPSubnet = 255.255.0.0
IPXEnabled = FALSE
MACAddress = 00:0D:60:EC:89:21
ServiceName = E1000
SettingID = {C6F084AE-E8D8-4345-85DF-D86958E5F651}
TcpipNetbiosOptions = 0
WINSEnableLMHostsLookup = TRUE
- [00000003] RAS Async Adapter
Caption = [00000003] RAS Async Adapter
Description = RAS Async Adapter
DHCPEnabled = FALSE
Index = 3
IPEnabled = FALSE
IPXEnabled = FALSE
ServiceName = AsyncMac
SettingID = {8D6FECAE-71B2-4FC4-86EA-E2D9A940F516}
- [00000004] WAN Miniport (L2TP)
Caption = [00000004] WAN Miniport (L2TP)
Description = WAN Miniport (L2TP)
DHCPEnabled = FALSE
Index = 4
IPEnabled = FALSE
IPXEnabled = FALSE
ServiceName = Rasl2tp
SettingID = {4F0143DE-8740-430D-A2C4-400A0B8BE873}
- [00000005] WAN Miniport (PPTP)
Caption = [00000005] WAN Miniport (PPTP)
Description = WAN Miniport (PPTP)
DHCPEnabled = FALSE
Index = 5
IPEnabled = FALSE
IPXEnabled = FALSE
MACAddress = 50:50:54:50:30:30
ServiceName = PptpMiniport
SettingID = {67FA88FB-19D1-4258-9619-8C99B77F7497}
- [00000006] WAN Miniport (PPPOE)
Caption = [00000006] WAN Miniport (PPPOE)
Description = WAN Miniport (PPPOE)
DHCPEnabled = FALSE
Index = 6
IPEnabled = FALSE
IPXEnabled = FALSE
MACAddress = 33:50:6F:45:30:30
ServiceName = RasPppoe
SettingID = {613A4098-792D-4B6C-BC32-B1887E49265B}
- [00000007] Direct Parallel
Caption = [00000007] Direct Parallel
Description = Direct Parallel
DHCPEnabled = FALSE
Index = 7
IPEnabled = FALSE
IPXEnabled = FALSE
ServiceName = Raspti
SettingID = {06BCA804-4101-4AC7-9964-25C72319B8F5}
- [00000008] WAN Miniport (IP)
Caption = [00000008] WAN Miniport (IP)
Description = WAN Miniport (IP)
DHCPEnabled = FALSE
Index = 8
IPEnabled = FALSE
IPXEnabled = FALSE
ServiceName = NdisWan
SettingID = {8599C953-A7B4-4AEE-975B-AB61C4412891}
- DNS Servers PASSED
- [00000002] Intel(R) PRO/1000 MT Dual Port Network Connection
(PASSED)
- DNSServerSearchOrder = 156.40.10.10 (PASSED)
Pinging 156.40.10.10 with 32 bytes of data:
Reply from 156.40.10.10: bytes=32 time<1ms TTL=0
Reply from 156.40.10.10: bytes=32 time<1ms TTL=0
Reply from 156.40.10.10: bytes=32 time<1ms TTL=0
Reply from 156.40.10.10: bytes=32 time<1ms TTL=0
Ping statistics for 156.40.10.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
- Default Gateways PASSED
- [00000002] Intel(R) PRO/1000 MT Dual Port Network Connection
(PASSED)
- DefaultIPGateway = 156.40.10.1(Same Subnet) (PASSED)
Pinging 156.40.10.1 with 32 bytes of data:
Reply from 156.40.10.1: bytes=32 time=1ms TTL=1
Reply from 156.40.10.1: bytes=32 time<1ms TTL=0
Reply from 156.40.10.1: bytes=32 time<1ms TTL=0
Reply from 156.40.10.1: bytes=32 time<1ms TTL=0
Ping statistics for 156.40.10.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 1ms, Average = 0ms
DHCP Servers
- IP Address PASSED
- [00000001] Intel(R) PRO/1000 MT Dual Port Network Connection
(PASSED)
- IPAddress = 128.1.5.10 (PASSED)
Pinging 128.1.5.10 with 32 bytes of data:
Reply from 128.1.5.10: bytes=32 time<1ms TTL=0
Reply from 128.1.5.10: bytes=32 time<1ms TTL=0
Reply from 128.1.5.10: bytes=32 time<1ms TTL=0
Reply from 128.1.5.10: bytes=32 time<1ms TTL=0
Ping statistics for 128.1.5.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
- [00000002] Intel(R) PRO/1000 MT Dual Port Network Connection
(PASSED)
- IPAddress = 156.40.10.10 (PASSED)
Pinging 156.40.10.10 with 32 bytes of data:
Reply from 156.40.10.10: bytes=32 time<1ms TTL=0
Reply from 156.40.10.10: bytes=32 time<1ms TTL=0
Reply from 156.40.10.10: bytes=32 time<1ms TTL=0
Reply from 156.40.10.10: bytes=32 time<1ms TTL=0
Ping statistics for 156.40.10.10:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss)
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
+ Network Clients
+ Microsoft Terminal Services
Description = RDPNP
Manufacturer = Microsoft Corporation
Name = Microsoft Terminal Services
Status = Unknown
- Microsoft Windows Network
Caption = Workstation
Description = Creates and maintains client network connections to
remote servers. If this service is stopped, these connections will be
unavailable. If this service is disabled, any services that explicitly
depend on it will fail to start.
Manufacturer = Microsoft Corporation
Name = Microsoft Windows Network
Status = OK
+ Web Client Network
Caption = WebClient
Description = Enables Windows-based programs to create, access, and
modify Internet-based files. If this service is stopped, these functions
will not be available. If this service is disabled, any services that
explicitly depend on it will fail to start.
Manufacturer = Microsoft Corporation
Name = Web Client Network
Status = Unknown

By default your server will be configured to use Root Hints. That's a
list of servers on the internet responsible for ".".

If your DNS server gets a request for a name it's not authoritative for
(doesn't have a forward or reverse lookup zone for) it will first ask
the root servers if they can help. This is the first step in an
Iterative query which ends with your server talking to the DNS servers
which know everything about the requested name.

The entire conversation goes something like this:

1. Client asks your server for "microsoft.com"
2. Your server asks one of the Root Hints servers (a to m.root-servers.net)
3. Root Hints server replies with "try asking .com servers" (a to
m.gtld-servers.net)
4. Your server asks .com servers
5. .com servers reply with "try asking ns1 to ns5.msft.net" (name
servers for microsoft.com)
6. Your server asks any of ns1 to ns5.msft.net
7. ns1-5 respond with an answer
8. Your server caches (remembers) the answer for the value of the TTL (1
hour in the case of this example)

The Root Servers can be seen on your server under Server Properties,
Root Hints.

HTH

Chris

Thanks Chris!
That helps for a start

"Muj" <> wrote in message
news:%...
> Thanks Chris!
> That helps for a start
>
>

I also suggest that you do not make this server a domain controller due to
the multihoming. Multhomed DCs are extremely problematic due to the DNS
registrations AD requires. If you do actually wish to make it a DC, I can
offer you a (complex) step by step to configure it properly to keep it
functional within AD parameters and DNS registration. However, I usually do
not recommend the multiple changes in the registry that are required to make
this work, and simply recommend to make it single homed and get an
inexpensice LinkSys or other named brand router to handle internet access
for the network, disable DHCP on this router, and setup DHCP on the server.

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Please reply back to the newsgroup or forum to benefit from collaboration
among responding engineers, and to help others benefit from your resolution.

Ace Fekay, MCT, MCSE, MCSA 2003 & 2000, MCSA Messaging
Microsoft Certified Trainer

http://twitter.com/acefekay

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

"Muj" <> wrote in message
news:%...
> Thanks for the suggestion
> The Multihomed function is not for Internet access. Its another network.
> For
> internet access we are using another ADSL Router supplied by our ADSL
> Provider.
>
> Attachment shows (dont know how to save my route print output) how my
> routing is configured. I am running DHCP and and DNS on this server which
> has an ip of 156.40.10.10 for that network. The only purpose of having the
> 128.1.5.0 network is just to have remote access to that network for
> maintenance purposes. The 128.1.5.0 network does not require internet
> access
> or to be objects of the AD. The DHCP Scope is for the 156.40.10.0 network.
> The 128.1.5.0 network has preconfigured IP addresses and we dont have to
> play with their existing IP settings.
>
> Ace, do you still think that there will be problems if we configure AD on
> this machine.
>
> TIA
>

Based on the route print, it appears there are two gateways, besides the two
interfaces. Any multihomed machine must only have one gateway. Two will
definitely cause problems. You can search through the Networking newsgroups,
or Google to see how many folks post with problems that we find are caused
by two gates.

As for the DC and multihoming, maybe I wasn't explicit. I implied internet
access based on two NICs, but having two NICs on a DC, whether one is for
the internet side, or to offer NAT, or whether to connect two internal
networks, is not recommended. You can search the term 'multihomed domain
controller' to see what I mean. It is due to a number of reasons, mainly DNS
registration of both NICs, whereas you do not want that. If a client or
another DC queries for this DC, and gets the IP of the NIC that it has no
route to, how is it going to commuicate to it? It also puts the DC into
multiple AD Sites. It also causes multiple identical NetBIOS name
registration (bad). This even includes one NIC with RRAS installed as a VPN
server, because RRAS creates additional interfaces for itself.

I'll tell you what. I'm posting my blog on multihomed DCs to give you a
greater understanding of what happens with a DC in such a scenario. It also
explains a step by step to configure a multihomed DC. I mean you can do it,
but I wouldn't. Too many changes I think to alter a DC's default
functionality, where you can simply use your network's infrastructure to
route to all network segments.

Let me know what you thing and which direction you will go.

================================================== ================================================== ==
================================================== ================================================== ==
Multihomed DCs, DNS, RRAS servers.
By Ace Fekay, MCSE, MCT
First published: January, 2003, revised accordingly
==============================================

Multihomed DCs WILL cause numerous issues. It's highly recommended to single
home all DCs and use a non-DC for the multihoming purposes. If it is the
internet gateway, it is recommended to purchase an inexpensive, or cable/DLS
router, or even better, a Cisco or similar firewall to perform the task,
which if it is compromised by an internet attacker remotely, can further
compromise the rest of the internal network.

Also if attempting to use ICS on a DC, this further complicates matters with
DC functionality, and cannot be fixed with the following steps outlined in
this article.

To explain why will require a little background on AD and DNS:

First, just to get this out of the way, if you have your ISP's DNS addresses
in your IP configuration (DCs and clients), they need to be REMOVED. If the
ISP's DNS is in there, this will cause additional problems. I usually see
errors (GPOs not working, can't find the domain, RPC issues, etc), when the
ISP's DNS servers are listed on a client, DCs and/or member servers, or with
multihomed DCs. If you have an ISP's (or some other outside DNS server or
even using your router as a DNS server) DNS addresses in your IP
configuration (all DCs, member servers and clients), they need to be REMOVED
and ONLY use the internal DNS server(s). This can be very problematic.

Basically, AD requires DNS. DNS stores AD's resource and service locations
in the form of SRV records, hence how everything that is part of the domain
will find resources in the domain. If the ISP's DNS is configured in the any
of the internal AD member machines' IP properties, (including all client
machines and DCs), the machines will be asking the ISP's DNS 'where is the
domain controller for my domain?", whenever it needs to perform a function,
(such as a logon request, replication request, querying and applying GPOs,
etc). Unfortunately, the ISP's DNS does not have that info and they reply
with an "I dunno know", and things just fail. Unfortunately, the ISP's (or
your router as a DNS server) DNS doesn't have information or records about
your internal private AD domain, and they shouldn't have that sort of
information.

Also, AD registers certain records in DNS in the form of SRV records that
signify AD's resource and service locations. When there are multiple NICs,
each NIC registers. IF a client, or another DC queries DNS for this DC, it
may get the wrong record. One factor controlling this is Round Robin. If a
DC or client on another subnet that the DC is not configured on queries for
it, Round Robin will kick in offering one or the other. If the wrong one
gets offered, it may not have a route to it. On the other hand, Subnetmask
Priortization will ensure a querying client will get an IP that corresponds
to the subnet it's on, which will work. To insure everything works, stick
with one NIC.

Since this DC is multi-homed, it requires additional configuration to
prevent the public interface addresses from being registered in DNS. This
creates a problem for internal clients locating AD to authenticate and find
other services and resources such as the Global Catalog, file sharing and
the SYSVOL DFS share and can cause GPO errors with Userenv 1000 events to be
logged, authenticating to shares and printers, logging on takes forever,
among numerous other issues.

But if you like, there are some registry changes to eliminate the
registration of the external NIC or simply use the internal networking
routing to allow access. Here's the whole list of manual steps to follow.

Another problem is the DC now becomes part of two Sites. This is another
issue that can be problematic.

But believe me, it's much easier to just get a separate NAT device or
multihome a non-DC then having to alter the DC. If the both NICs are
internal, I would suggest to pick a subnet, team the NICs and allow your
internal routers handle the traffic between subnets - Good luck!

1. Insure that all the NICS only point to your internal DNS server(s) only
and none others, such as your ISP’s DNS servers’ IP addresses.

2. In Network & Dialup properties, Advanced Menu item, Advanced Settings,
move the internal NIC (the network that AD is on) to the top of the binding
order (top of the list).

3. Disable the ability for the outer NIC to register. The procedure, as
mentioned, involves identifying the outer NIC’s GUID number. This link will
show you how:
246804 - How to Enable-Disable Windows 2000 Dynamic DNS Registrations (per
NIC too):
http://support.microsoft.com/?id=246804

4. Disable NetBIOS on the outside NIC. That is performed by choosing to
disable NetBIOS in IP Properties, Advanced, and you will find that under the
“WINS” tab. You may want to look at step #3 in the article to show you how
to disable NetBIOS on the RRAS interfaces if this is a RRAS server.
296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
[Registry Entry]:
http://support.microsoft.com/?id=296379

Note: A standard Windows service, called the “Browser service”, provides the
list of machines, workgroup and domain names that you see in “My Network
Places” (or the legacy term “Network Neighborhood”). The Browser service
relies on the NetBIOS service. One major requirement of NetBIOS service is a
machine can only have one name to one IP address. It’s sort of a
fingerprint. You can’t have two brothers named Darrell. A multihomed machine
will cause duplicate name errors on itself because Windows sees itself with
the same name in the Browse List (My Network Places), but with different
IPs. You can only have one, hence the error generated.

5. Disable the “File and Print Service” and disable the “MS Client Service”
on the outer NIC. That is done in NIC properties by unchecking the
respective service under the general properties page. If you need these
services on the outside NIC (which is unlikely), which allow other machines
to connect to your machine for accessing resource on your machine (shared
folders, printers, etc.), then you will probably need to keep them enabled.

6. Uncheck “Register this connection” under IP properties, Advanced
settings, “DNS” tab.

7. Delete the outer NIC IP address, disable Netlogon registration, and
manually create the required records

a. In DNS under the zone name, (your DNS domain name), delete the outer
NIC’s IP references for the “LdapIpAddress”. If this is a GC, you will need
to delete the GC IP record as well (the “GcIpAddress”). To do that, in the
DNS console, under the zone name, you will see the _msdcs folder.

Under that, you will see the _gc folder. To the right, you will see the IP
address referencing the GC address. That is called the GcIpAddress. Delete
the IP addresses referencing the outer NIC.
i. To stop these two records from registering that information,
use the steps provided in the links below:
Private Network Interfaces on a Domain Controller Are Registered in DNS
http://support.microsoft.com/?id=295328

ii. The one section of the article that disables these records is
done with this registry entry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Netlogon\Parameters
(Create this Multi-String Value under it):
Registry value: DnsAvoidRegisterRecords
Data type: REG_MULTI_SZ
Values: LdapIpAddress
GcIpAddress

iii. Here is more information on these and other Netlogon Service records:
Restrict the DNS SRV resource records updated by the Netlogon service
[including GC]:
http://www.microsoft.com/technet/tre...o_rr_in_ad.asp

b. Then you will need to manually create these two records in DNS with
the IP addresses that you need for the DC. To create the LdapIpAddress,
create a new host under the domain, but leave the “hostname” field blank,
and provide the internal IP of the DC, which results in a record that looks
like:
(same as parent) A 192.168.5.200 (192.168.5.200 is used for illustrative
purposes)

i. You need to also manually create the GcIpAddress as well, if
this is a GC. That would be under the _msdcs._gc SRV record under the zone.
It is created in the same fashion as the LdapIpAddress mentioned above.

8. In the DNS console, right click the server name, choose properties, then
under the “Interfaces” tab, force it only to listen to the internal NIC’s IP
address, and not the IP address of the outer NIC.

9. Since this is also a DNS server, the IPs from all NICs will register,
even if you tell it not to in the NIC properties. See this to show you how
to stop that behavior (this procedure is for Windows 2000, but will also
work for Windows 2003):
275554 - The Host's A Record Is Registered in DNS After You Choose Not to
Register the Connection's Address:
http://support.microsoft.com/?id=275554

10. If you haven't done so, configure a forwarder. You can use 4.2.2.2 if
not sure which DNS to forward to until you've got the DNS address of your
ISP.
How to set a forwarder? Good question. Depending on your operating
system,choose one of the following articles:

300202 - HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/?id=300202

323380 - HOW TO: Configure DNS for Internet Access in Windows Server 2003
(How to configure a forwarder):
http://support.microsoft.com/d/id?=323380

Active Directory communication fails on multihomed domain controllers
http://support.microsoft.com/kb/272294


<==*** Some additional reading ***==>
More links to read up and understand what is going on:

292822 - Name Resolution and Connectivity Issues on Windows 2000 Domain
Controller with Routing and Remote Access and DNS Insta {DNS and RRAS and
unwanted IPs registering]:
http://support.microsoft.com/?id=292822

Active Directory communication fails on multihomed domain controllers
http://support.microsoft.com/kb/272294

246804 - How to enable or disable DNS updates in Windows 2000 and in Windows
Server 2003
http://support.microsoft.com/?id=246804

295328 - Private Network Interfaces on a Domain Controller Are Registered in
DNS [also shows DnsAvoidRegisterRecords LdapIpAddress to avoid reg
sameasparent private IP]:
http://support.microsoft.com/?id=295328

306602 - How to Optimize the Location of a DC or GC That Resides Outside of
a Client's Site [Includes info LdapIpAddress and GcIpAddress information and
the SRV mnemonic values]:
http://support.microsoft.com/?id=306602

825036 - Best practices for DNS client settings in Windows 2000 Server and
in Windows Server 2003 (including how-to configure a forwarder):
http://support.microsoft.com/default...b;en-us;825036

291382 - Frequently asked questions about Windows 2000 DNS and Windows
Server 2003 DNS
http://support.microsoft.com/?id=291382

296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
[Registry Entry]:
http://support.microsoft.com/?id=296379

Rid Pool Errors and other multihomed DC errors, and how to configure a
multihomed DC, Ace Fekay, 24 Feb 2006
http://www.ureader.com/message/3244572.aspx

257623 257623 Domain Controller's Domain Name System Suffix Does Not Match
Domain Name
http://support.microsoft.com/?id=257623
================================================== ================================================== ==
================================================== ================================================== ==
Ace

Thats plenty of reading I must go through. Will go throroguh as time
permits.

Currently I'm working on a test setup. For production it sounds like I shall
get another router leaving this one alone as a DC

Thanks

"Muj" <> wrote in message
news:emQG%...
> Thats plenty of reading I must go through. Will go throroguh as time
> permits.
>
> Currently I'm working on a test setup. For production it sounds like I
> shall
> get another router leaving this one alone as a DC
>
> Thanks

Unfortunately it is plenty of reading. I was trying to illustrate a good
reason not to multihome it, based on all the changes that need to be made.

Glad to hear you leaving it alone as a DC. Good choice with the least
administrative overhead.

:-)

Ace