Re: Subnet problem.

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance




"abckid" <abckid@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:969F2FF4-3F21-4C66-B079-67BD3864152E@xxxxxxxxxxxxxxxx
Hello,

Thanks for reply.

I do understand that it should be changed to any private ip range. But
there
are many changes that would be required by them. Also they are using the
same
subnet for some of their branches which are connected to them !

Still none of that should matter much since practically all "connections" to
them
will be by NAME. DNS or NetBIOS.

A few machines such as printers and routers will need to be updated on the
machines that use these, but if they use DHCP this will be relatively easy
and
if they do not use DHCP this is a good time to START.

Thanks again.

abc.

"Herb Martin" wrote:


"abckid" <abckid@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B5C058DF-4A0D-42F4-B8D5-9D59D031B3E2@xxxxxxxxxxxxxxxx
Hi,

Thanks for reply.

I cannot change the existing IP range used by them. But its possible to
select a different domain name.

You can certainly change it if it is a publicly assigned range they do
not
own and they are connected to the Internet.

You not can but should -- and if you mean "you" personally cannot
change it then the Network Admin can do so and should

Thanks again for the guidance.

abc.

"Herb Martin" wrote:


"abckid" <abckid@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:498307B0-0367-4204-93DF-8FD0AA264F04@xxxxxxxxxxxxxxxx
Hello,

I don't know whether this would be the right section to my problem.
We are planning to set a new domain for a company. This company is
using
the
ip range of 198.x.x.x on their network. There are 3 IP network
addresses

Use 192.168 (not an arbitrary value in the second octet),
172.16-172.31,
or
anything in the 10.x.y.z range.


reserved for private networks - 10.0.0.0 to 10.255.255.255,
172.16.0.0
to
172.31.255.255 and 192.168.0.0 to 192.168.255.255.

1) Does it matter for the DNS anyhow to use 198.x.x.x range in ther
network ?

No. DNS does NOT care -- you care but DNS doesn't.

Also they want to use a domain name which is used by someone on the
internet.

Don't let them do that. At best they will never be able to contact
THAT
Internet domain which legitimately owns the record, and worse, when
they
want to contact themselves (or publish themselves on the Internet for
EMail
web etc) they will not be able to resolve their own addresses with
THAT
already owned name.

Please guide about this scenerio, if this would create any problems
for
the
existing the DNS structure.

1) Pick a PRIVATE name (e.g., something.local) OR

2) Pick a CHILD of Public name which they MUST own/buy
(e.g., child.something.com )OR

3) Pick a Public name they OWN, but only after explaining the minor
but
significant issues they will encounter with this choice

A variation on #1/#3 is to pick a TECHNICALLY Public name (they
they buy/own) that is an ALTERNATIVE to their "real" Internet name
but isn't actively used by them, e.g.,

Something.com on the Internet (web, email etc) AND
Something.net for the (mostly) private names

This latter breaks the spirit of the purpose for ".net" (or .org)
names
but is done by many people and there is nothiung to actually prevent
it in practice.

I like #4 best for people who don't really understand DNS thoroughly
which seems it may apply to your clients.
Thanks in advance.

abckid.








.



Relevant Pages

  • Re: Non-domain connection problem
    ... For some reason the DNS is persistent. ... connect new PC to the internet from the non-domain network: ... In server 2000 gpoedit.msc showed them but in SBS it is different. ...
    (microsoft.public.windows.server.sbs)
  • Re: How do my server 2003 (DNS) know the Internet?
    ... The Multihomed function is not for Internet access. ... has an ip of 156.40.10.10 for that network. ... It is due to a number of reasons, mainly DNS registration of both NICs, whereas you do not want that. ... It's highly recommended to single home all DCs and use a non-DC for the multihoming purposes. ...
    (microsoft.public.windows.server.dns)
  • Re: Non-domain connection problem
    ... You said that you "hard coded the DNS server to a known DNS on the internet: ... Connect to Internet from Internal Network ... NSLOOKUP always looks for the SBS as the default gateway. ...
    (microsoft.public.windows.server.sbs)
  • Re: ISA 2006 Basic Configuration
    ... Why would we point Preferred DNS to itself? ... Configuring the Internal Network Interface ... In the Internet Protocol Properties dialog box, ... Select the Use the following DNS server addresses option. ...
    (microsoft.public.isa.configuration)
  • Re: IE cant connect to any sites
    ... On the General tab in the Temporary Internet Files Folder, ... Click on "LAN Settings" and make sure everything is blank, ... Network settings ... IP address automatically", click on the DNS tab, disable DNS here, click ...
    (microsoft.public.windows.inetexplorer.ie6.browser)