知识产权问题 [英] IP dns question

查看:68
本文介绍了知识产权问题的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一系列网站,让我们称之为customer1.mydomain.co.uk。 - >

" customer200.mydomain.co.uk" ;.


每个网址都绑定到一个单独的IP地址,可以使用

nslookup。


所以,例如

customer1.mydomain.co.uk = 100.200.300.1

customer200.mydomain.co.uk = 100.200.300.200


买了4台服务器,serverA - > serverD。


我随意将客户1-50放在serverA上,客户51-100放在serverB上




完成所有这些后,我现在发现客户1-50代表了大部分

的负载,所以我想更均匀地分配负载。您可以想象

场景。


作为管理工具的一部分,我创建了一个动态查找显示器

的URL并返回DNS A记录中的IP地址。但是,我想要有一些方法可以找到这个IP实际绑定的机器

到。我经常将经销商从一台服务器迁移到另一台服务器并且保持手动跟踪这是非常令人头疼的问题。有没有人知道一个

方法说我知道网站地址由a)URL和b)IP

地址,我现在需要找出它所在的服务器的名称

bound"。每个服务器具有永久的主IP地址。而不是

与任何客户的网站相关联。


任何想法?


谢谢


Griff

I have a series of websites, let''s call them "customer1.mydomain.co.uk" -->
"customer200.mydomain.co.uk".

Each URL is bound to an individual IP address which can be resolved using
nslookup.

So, for example
customer1.mydomain.co.uk = 100.200.300.1
customer200.mydomain.co.uk = 100.200.300.200

However, I can''t fit all these 200 websites on the same server, so I have
bought 4 servers, serverA -> serverD.

I have arbitrarily put customer 1-50 on serverA, customer 51-100 on serverB
etc.

Having set all this up, I now find that customers 1-50 represent most of the
load, so I want to distribute the load a bit more evenly. You can imagine
the scenario.

As part of my Admin tools, I''ve created a display that does dynamic lookups
of the URLs and returns me the IP address from the DNS A record. However, I
want to have some way of finding out which machine this IP is actually bound
to. I''m constantly migrating dealers from one server to another and keeping
track of this manually is too great a headache. Does anyone know of a
method of saying "I''ve know the web site address by a) the URL and b) the IP
address, I now need to find out the name of the server on which it is
bound". Each server has a primary IP address that is "permanent" and not
associated with any customers'' web site.

Any ideas?

Thanks

Griff

推荐答案

" GriffithsJ"写道:

<! - SNiP - >


自从你发布到
microsoft.public.windows.server.dns

microsoft.public.win2000.dns

microsoft.public.scripting.vbscript

microsoft.public.vb.general.discussion

microsoft.public.inetserver.asp.general

microsoft.public.inetserver.misc


除非你的网络服务器在W2K上运行,否则这对于b

microsoft.public.win2000.dns

这些肯定与DNS没有任何关系:


microsoft.public.scripting.vbscript

microsoft.public .vb.general.discussion

microsoft.public.inetserver.asp.general


这个真的不是,但它与服务器有关:

microsoft.public.inetserver.misc


这让我们留下了这个;

microsoft.public.windows.server.d ns


它也不是真正的DNS问题,因为它是一种哲学或方法论

与主机名命名实践相关的问题。它应该更多地落入安全领域,因为在您的URL中添加服务器名称是一个安全性问题。您的服务器应该在防火墙后面。你的内部DNS可以有任何它想要的东西,但外部应该只有公共域命名。


请关注mpwindow.server.dns

-

Roland


这些信息的发布是希望它有用,但是

没有任何保证;甚至没有适销性的暗示保证

或特定用途的适用性。

-Technet知识库 -
http://support.microsoft .com / default ...& ln = EN-US& FR = 0

-Technet Script Center-
http://www.microsoft.com/technet/tre ... er / default.asp

-WSH 5.6文档下载 -
http://www.microsoft.com/downloads/d...displaylang=en

-MSDN Library-
http:// msdn.microsoft.com/library/defau lt.asp
"GriffithsJ" wrote:
<!--SNiP-->

You''re probably going to catch hell for this post since you posted to
microsoft.public.windows.server.dns
microsoft.public.win2000.dns
microsoft.public.scripting.vbscript
microsoft.public.vb.general.discussion
microsoft.public.inetserver.asp.general
microsoft.public.inetserver.misc

Unless your web servers are running on W2K, this does not have anything to
do with:
microsoft.public.win2000.dns

These definitely do NOT have anything to do with DNS:

microsoft.public.scripting.vbscript
microsoft.public.vb.general.discussion
microsoft.public.inetserver.asp.general

This one really doesn''t either but it is server related:
microsoft.public.inetserver.misc

That leaves us with this;
microsoft.public.windows.server.dns

It is also not really a DNS question since it is a philosophy or methodology
question related to host name naming practices. It should fall more into
the security arena because adding the server name to your URL is a security
issue. Your servers should be behind firewalls. Your internal DNS can have
anything it wants but external should only have public domain naming.

Please only follow up in m.p.window.server.dns
--
Roland

This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose.
-Technet Knowledge Base-
http://support.microsoft.com/default...&ln=EN-US&FR=0
-Technet Script Center-
http://www.microsoft.com/technet/tre...er/default.asp
-WSH 5.6 documentation download-
http://www.microsoft.com/downloads/d...displaylang=en
-MSDN Library-
http://msdn.microsoft.com/library/default.asp


你好Roland


如果我发布到你不认为是的团体,我会道歉适当的。

然而,在我看来,他们似乎是最适合接触那些很可能面临类似的人群的人。

问题。


Griff
Hi Roland

Apologies if I posted to groups that you don''t think were appropriate.
However, to my mind they seemed the most appropriate ones for reaching the
groups of people who would most likely have been faced with a similar
problem.

Griff


然后你需要学习如何使用新闻组。

第一条规则:不要咬手可以喂你的手。

" GriffithsJ" <的Gr ************ @ hotmail.com>在消息中写道

新闻:#e ************** @ TK2MSFTNGP10.phx.gbl ...
then you need to learn how to use newsgroups.
first rule: don''t bite the hands that could feed you.
"GriffithsJ" <Gr************@hotmail.com> wrote in message
news:#e**************@TK2MSFTNGP10.phx.gbl...
嗨Roland 但是,在我看来,他们似乎是最适合接触最多人群的人。可能一直面临类似的问题。

Griff
Hi Roland

Apologies if I posted to groups that you don''t think were appropriate.
However, to my mind they seemed the most appropriate ones for reaching the
groups of people who would most likely have been faced with a similar
problem.

Griff



这篇关于知识产权问题的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆