CN100474858C - Domain name analytic method, domain name server and domain name system - Google Patents
Domain name analytic method, domain name server and domain name system Download PDFInfo
- Publication number
- CN100474858C CN100474858C CNB2004100666979A CN200410066697A CN100474858C CN 100474858 C CN100474858 C CN 100474858C CN B2004100666979 A CNB2004100666979 A CN B2004100666979A CN 200410066697 A CN200410066697 A CN 200410066697A CN 100474858 C CN100474858 C CN 100474858C
- Authority
- CN
- China
- Prior art keywords
- domain name
- type
- query
- resource record
- resolver
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides a domain name resolution method, which comprises following steps: receiving a piece of query information from analyzer; when the query style belongs to the appointed, finding out matched domain name and style (A or AAAA)record from database; constructing response information to return to analyzer. It also provides opposite DNS and domain name system. This invention decreases communication delay in double stack nodes IP address analysis process, saves network bandwidth and treated resource in DNS.
Description
Technical field
The present invention relates to network communicating system, and relate more specifically to domain name analytic method, name server and domain name system.
Background technology
IPv4 address and IPv6 address are with long-term co-existence.Two stack main frames will have the address of IPv4 and IPv6 simultaneously.At present, in order to keep the compatibility with the IPv4 agreement, IPv6 application program newly developed will become flexible to the use of address, by introduce the new SOCKET API (API) of a cover on the protocol stack upper strata, such program will not only may operate on the IPv4 protocol stack but also may operate on the IPv6 protocol stack.Yet these new application programs will have problems when carrying out domain name mapping, because it can't confirm the IP version number of the machine that it will be visited.In order to resolve a given domain name, the domain name system of this application program (DNS) resolver has to start two DNS inquiries: the inquiry of an AAAA (or A6) type, and the inquiry of a category-A type.
For example, if during web browser (as the Internet Explorer) website of visit (as www.shanghaionline.com) on two stack main frames of operation WindowsXP operating system, because resolver is not known the IP version of this website, so resolver has to start respectively the inquiry of the inquiry of an AAAA type and a category-A type to obtain possible IPv6 address and IPv4 address.
The above-mentioned existing domain name analytic method that relates to two DNS inquiries makes application program have to wait for the result of two DNS inquiries, so increased communication delay.Have, the network bandwidth has been wasted in twice communication again, has unnecessarily consumed the processing resource of dns server.
Summary of the invention
Therefore, the objective of the invention is to solve the technical problem that the above-mentioned communication delay, network bandwidth waste and the dns server that exist in the prior art are handled the wasting of resources, a kind of domain name analytic method, name server and domain name system of novelty is provided.
For this reason, the invention provides a kind of domain name analytic method, it is characterized in that may further comprise the steps:
Receive a query messages from resolver;
When the query type in the described query messages is specified type, from dns database, search with described query messages in domain name coupling and with the resource record of query type A or AAAA coupling, wherein said specified type shows that content that needs are inquired about comprises the IPv4 and the IPv6 address of contained domain name in the described inquiry;
According to the described resource record that finds, tectonic response message;
Described response message is returned to described resolver.
The present invention also provides a kind of name server, comprising:
Dns database;
Be used for receiving the device of a query messages from resolver;
Be used for response message is returned to the device of described resolver;
It is characterized in that also comprising:
Resource record is searched device, be used for when the query type of described query messages is specified type, from the domain name database, search with described query messages in domain name coupling and with the resource record of query type A or AAAA coupling, wherein said specified type shows that content that needs are inquired about comprises the IPv4 and the IPv6 address of contained domain name in the described inquiry;
Be used for constructing the device of described response message according to the resource record of described coupling.
The present invention also provides a kind of domain name system, it is characterized in that comprising:
Resolver is used for the IP address lookup request according to application program, constructs the query messages that query type is a specified type, and wherein said specified type shows that the content of needs inquiry comprises the IPv4 and the IPv6 address of contained domain name in the described inquiry; And
Name server is used for carrying out the IP address resolution in response to described query messages, and described IP address is returned to described resolver, and the domain name server comprises:
Dns database;
Be used for receiving the device of a query messages from resolver;
Resource record is searched device, is used for when the query type of described query messages is described specified type, from the domain name database, search with described query messages in domain name coupling and with the resource record of query type A or AAAA coupling;
Be used for constructing the device of described response message according to the resource record of described coupling; And
Be used for response message is returned to the device of described resolver.
According to domain name analytic method of the present invention, name server and domain name system, by one query, can obtain the IP address of the various version of dual stack node, so reduced communication delay in the dual stack node IP address resolution procedure, saved the network bandwidth and dns server is handled resource.
After detailed description of reading embodiment of the present invention in conjunction with the accompanying drawings according to the present invention, other characteristics of the present invention and advantage will become clearer.
Description of drawings
Fig. 1 is the schematic configuration diagram of domain name system (DNS);
Fig. 2 is the schematic configuration diagram of the message that adopts in the communication of domain name agreement;
Fig. 3 is the flow chart according to a kind of embodiment of domain name analytic method of the present invention.
Embodiment
Describe embodiments of the invention in detail below in conjunction with accompanying drawing.
Fig. 1 is the schematic configuration diagram of domain name system (DNS).Label 101 expression user applications, 102 expression resolvers, 103 expression name servers, 104 expression high-speed caches.When user application 101 wished to obtain host address relevant with specific domain name or e-mail messages, user application 101 had this specific domain name to the inquiry of a suitable type of resolver 102 transmissions in the inquiry.After resolver 102 was received the user inquiring that user application 101 sends, resolver 102 sent inquiry to a name server 103 known to it, and request for information about.As response, resolver 102 or obtain desired information from name server 103 perhaps obtains the reference information to another name server (not shown in figure 1).Utilize these reference information, resolver 102 can be understood the identity and the content of other name servers, and and then from the desired information of other name servers acquisitions.That is to say that in order to answer a user inquiring, resolver 102 may have to carry out the several inquiry to several different external nameservers.
In order to improve the performance of above-mentioned inquiry and retrieving, before sending inquiry to name server 103, resolver 102 is at first retrieved high-speed cache 104.If preserved desired information in the high-speed cache 104, then resolver 102 directly obtains relevant referenced items from high-speed cache 104.Only can not obtain in high-speed cache 104 under the situation of desired information, resolver 102 just sends inquiry to name server 103.After having obtained desired information, with the corresponding content of upgrading in the high-speed cache 104 that adds from name server 103 or other name servers.Data in the high-speed cache 104 may be incomplete, but have improved the performance of retrieving under the situation that does not have local data to be repeated to visit.Among Fig. 1, user inquiring and user's response are specific for local host and operating system thereof.User inquiring generally is that operating system is called, and resolver 102 and high-speed cache 104 are parts of host operating system.
Fig. 2 is the schematic configuration diagram of the message that adopts in the communication of domain name agreement.Single structure shown in Figure 2 is all adopted in resolver 102 among Fig. 1 and the inquiry between the name server 103 and response.As shown in Figure 2, message is divided into five parts, i.e. stem 201, enquirement 202, answer 203, agent authorized 204 and additional information 205.
Every message all has stem 201.Stem 201 in a piece of news comprises and is used to specify the field whether this message comprises other parts, and specifying this message is the field of inquiry or response, and specifying this message is standard queries or other command code, or the like.What specify is that stem 201 has a QDCOUNT field, is used to specify to put question to the inlet number that comprises in 202 parts.The general value of QDCOUNT is 1.Stem 201 also has an ANCOUNT, is used to specify the number of answering the resource record in 203 parts.
Put question to 202 parts, be used to carry " enquirement " of inquiry.Put question to each inlet in 202 parts to comprise three partial contents, i.e. domain name, query type, query categories.
Answer 203, agent authorized 204, additional information 205 all adopt identical form, promptly comprise the resource record of variable number.Comprise domain name, resource record types, data division type, time interval length, data division length and data division in every resource record.
About the more detailed description of Fig. 1 and Fig. 2, can be referring to RFC 1034 " DomainConcepts and Facilities " and RFC 1035 " Domain Implementationand Specification ".
Fig. 3 is the flow chart according to a kind of embodiment of domain name analytic method of the present invention.This method may operate in any conventional name server.
As shown in Figure 3, flow process starts from step 301.
Then, in step 302, name server receives a query messages from resolver 102.Then, in step 303, partly obtain information such as domain name, query type and query categories from the enquirement of the query messages received.
Then, in step 304, whether the query type that obtains in the determining step 303 is according to specified type of the present invention.
Here it should be explained that, stipulated a kind of new query type " DSR " among the present invention, as the specified type among the present invention.The type codes of specified type " DSR " for example can be 248.Query messages with specified type " DSR " means that this inquiry hope obtains the IPv4 and the IPv6 address of domain name contained in this inquiry, and other possible resource records relevant with this domain name.
If the judged result of step 304 is for being that then flow process proceeds to step 3052, otherwise proceeds to step 3051.
In step 3051, name server from dns database, search with step 303 in the resource record of the couplings such as domain name, query type, query categories that obtain.Concrete search procedure needn't be done detailed description with of the prior art the same.
In step 3052, name server from dns database, search with step 303 in domain name, query type " A " or the query type " AAAA ", the resource record of query categories " IN " coupling that obtain.Concrete search procedure and of the prior art similar needn't be done detailed description.Need to prove that query type " A " means the needs inquiry IPv4 address corresponding with domain name, query type " AAAA " means the needs inquiry IPv6 address corresponding with domain name, and query categories " IN " means that the address of inquiry is an IP address.
After step 3051 and step 3052, flow process all proceeds to step 306.
In step 306, according to one or more resource record that has found, the various piece of tectonic response message.As mentioned before, response message is followed structure shown in Figure 2 equally.
The process of tectonic response message is broadly directed to these contents.At first, what answer parts in message header, should have been indicated.The number of answering part is identical with the number of the resource record that finds.If do not find the resource record of any coupling, the number of then answering part is zero.Secondly, at the resource record that each bar finds, construct a corresponding part of answering.For every the resource record that finds in the step 3052, the answer of being constructed partly comprises: domain name, resource record types (" A " or " AAAA "), IP address contents such as (IPv4 or IPv6).
Then, in step 307, name server returns at the good response message of step 306 structure to resolver.
At last, flow process finishes in step 308.Certainly, flow process also can directly turn back to step 302, constitutes a circulation.
Provide the example of an inquiry below.
Suppose that the resolver 102 among Fig. 1 provides inquiry to name server 103: " www.shanghaionline.com, DSR, IN ".
And suppose that zone (zone) content of domain name " www.shanghaionline.com " in dns database is:
The database file shanghaionline.com.dns in shanghaionline.com zone; Zone version: 23
@ IN SOA DNSserver. hostmaster.(
23 ； serial?number
900 ； refresh
600 ； retry
86400 ； expire
3600 )； default?TTL
Zone NS record
@ NS DNSserver.
Regional record
@ A 202.112.0.1
@ AAAA 3ffe::2b0：d0ff:fee3:e183
www A 201.201.221.5
CNAME?shanghaionline.com
AAAA fe80::2b0:d0ff:fee4:e131
AAAA fe80::2b0:dlff:fee4:e131
clientl.comm. A 201.201.221.1
AAAA 3ffe::2b0:d0ff:cfee:e303
ftp AAAA fe80::2b0:d0ff:fee4:e133
AAAA fe80::2b0:d0ff:fee4:e131
ftp2 AAAA fe80::2b0:d0ff:fe3d:1234
6tel AAAA fe80::2b0:d0ff:fe3c:29e
mail A 202.112.0.201
AAAA fe80::2b0:d0ff:fee4:e131
www1 A 202.112.0.202
AAAA fe80::2b0:d0ff:fee4:e131
Like this, in the step 304 of Fig. 3, will judge query type is to specify type " DSR ", thereby flow process proceeds to step 3052.In step 3052, from dns database, find following resource record:
www A 201.201.221.5
AAAA fe80::2b0:d0ff:fee4:e131
AAAA fe80::2b0:dlff:fee4:e131
Then, in the step 306 of Fig. 3, the response message that is constructed as follows:
(following is stem)
......00010003
(following) for puing question to part
www.shanghaionline.com ...00f8...
(following) for answering part
shanghaionline.com ...0001...201.201.221.5
shanghaionline.com ...001c...fe80::2b0:d0ff:fee4:e131
shanghaionline.com ...001c...fe80::2b0:d1ff:fee4:e131
In the stem of above response message, " 0001 " expression is putd question in the part has only 1 inlet, and " 0003 " represents that this response message comprises 3 answers.Put question in the part value (being metric 248) of " 00f8 " (hexadecimal) expression query type DSR.First is answered in the part, and " 0001 " expression resource record types is " A ".Answer in the part for second and the 3rd, " 001c " expression resource record types is " AAAA ".
Method for example shown in Figure 3 is applied in the name server shown in Figure 1 103, has promptly realized according to name server of the present invention.
In addition, can make following modification to resolver shown in Figure 1 102.After resolver 102 was received user inquiring from user application 101, resolver 102 structures were inquired about, so that comprise the given query type (as DSR) among the present invention in inquiry.After resolver 102 is received response from name server 103, IPv4 or the IPv6 address that comprises in the response can be encapsulated in user's response, and user's response is returned to user application 101.
Though described embodiments of the present invention in conjunction with the accompanying drawings, those skilled in the art can make various distortion or modification within the scope of the appended claims in this area.
Claims (10)
1. domain name analytic method is characterized in that may further comprise the steps:
Receive a query messages from resolver;
When the query type in the described query messages is specified type, from dns database, search with described query messages in domain name coupling and with the resource record of query type A or AAAA coupling, wherein said specified type shows that content that needs are inquired about comprises the IPv4 and the IPv6 address of contained domain name in the described inquiry;
According to the described resource record that finds, tectonic response message;
Described response message is returned to described resolver.
2. according to the domain name analytic method of claim 1, it is characterized in that the described resource record that finds comprises at least a in category-A type resource record and the AAAA resource type record.
3. according to the domain name analytic method of claim 2, it is characterized in that described response message comprises at least a in IPv4 address and the IPv6 address.
4. name server comprises:
Dns database;
Be used for receiving the device of a query messages from resolver;
Be used for response message is returned to the device of described resolver;
It is characterized in that also comprising:
Resource record is searched device, be used for when the query type of described query messages is specified type, from the domain name database, search with described query messages in domain name coupling and with the resource record of query type A or AAAA coupling, wherein said specified type shows that content that needs are inquired about comprises the IPv4 and the IPv6 address of contained domain name in the described inquiry;
Be used for constructing the device of described response message according to the resource record of described coupling.
5. according to the name server of claim 4, it is characterized in that: the resource record of described coupling comprises at least a in category-A type resource record and the AAAA resource type record.
6. according to the name server of claim 5, it is characterized in that: described response message comprises at least a in IPv4 address and the IPv6 address.
7. domain name system is characterized in that comprising:
Resolver is used for the IP address lookup request according to application program, constructs the query messages that query type is a specified type, and wherein said specified type shows that the content of needs inquiry comprises the IPv4 and the IPv6 address of contained domain name in the described inquiry; And
Name server is used for carrying out the IP address resolution in response to described query messages, and described IP address is returned to described resolver, and the domain name server comprises:
Dns database;
Be used for receiving the device of a query messages from resolver;
Resource record is searched device, is used for when the query type of described query messages is described specified type, from the domain name database, search with described query messages in domain name coupling and with the resource record of query type A or AAAA coupling;
Be used for constructing the device of described response message according to the resource record of described coupling; And
Be used for response message is returned to the device of described resolver.
8. according to the domain name system of claim 7, it is characterized in that: the resource record of described coupling comprises at least a in category-A type resource record and the AAAA resource type record.
9. domain name system according to Claim 8 is characterized in that: described response message comprises at least a in IPv4 address and the IPv6 address.
10. according to the domain name system of claim 7, it is characterized in that also comprising a high-speed cache, be used for described response message is carried out buffer memory.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100666979A CN100474858C (en) | 2004-09-27 | 2004-09-27 | Domain name analytic method, domain name server and domain name system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100666979A CN100474858C (en) | 2004-09-27 | 2004-09-27 | Domain name analytic method, domain name server and domain name system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1756263A CN1756263A (en) | 2006-04-05 |
| CN100474858C true CN100474858C (en) | 2009-04-01 |
Family
ID=36689192
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2004100666979A Active CN100474858C (en) | 2004-09-27 | 2004-09-27 | Domain name analytic method, domain name server and domain name system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100474858C (en) |
Families Citing this family (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1317876C (en) * | 2006-04-10 | 2007-05-23 | 王立俊 | Server end domain name analytical error control method and system |
| CN101262410B (en) * | 2007-03-07 | 2010-12-08 | 上海亿人通信终端有限公司 | Implementation method for DNS application gateway based on NAT-PT |
| CN101378427A (en) * | 2007-08-28 | 2009-03-04 | 杨汉民 | Server for implementing network communication number service |
| CN101170585B (en) * | 2007-11-13 | 2011-08-24 | 中兴通讯股份有限公司 | A domain name inquiry method |
| CN101499996B (en) * | 2008-01-28 | 2012-05-23 | 中国电信股份有限公司 | Domain name differentiate parsing method and domain name server |
| CN101527900B (en) * | 2008-03-05 | 2011-05-04 | 华为技术有限公司 | Method, entity and system for matching IP version information |
| CN101431539B (en) * | 2008-12-11 | 2011-04-20 | 华为技术有限公司 | Domain name resolution method, system and apparatus |
| JP5812008B2 (en) * | 2010-10-18 | 2015-11-11 | 日本電気株式会社 | Name database server, name resolution system, entry search method, and entry search program |
| CN102098351A (en) * | 2010-12-13 | 2011-06-15 | 山东科技大学 | Method for analyzing color numerical value domain name |
| CN103685585B (en) * | 2012-09-07 | 2016-11-23 | 中国科学院计算机网络信息中心 | A kind of highly reliable DNS data update method and system |
| CN104702707B (en) * | 2013-12-06 | 2018-05-01 | 中国联合网络通信集团有限公司 | A kind of data processing method and device |
| WO2015100566A1 (en) * | 2013-12-30 | 2015-07-09 | 华为技术有限公司 | Method and device for processing domain name request |
| CN106161667A (en) * | 2015-04-27 | 2016-11-23 | 中国移动通信集团公司 | A kind of domain name analytic method and device |
| CN106470195B (en) * | 2015-08-20 | 2019-12-17 | 互联网域名系统北京市工程研究中心有限公司 | Message signature method and domain name server |
| CN105245631B (en) * | 2015-09-25 | 2018-10-26 | 中国互联网络信息中心 | A kind of method and system of optimization DNS root service access |
| CN106899707A (en) * | 2017-01-18 | 2017-06-27 | 中国互联网络信息中心 | A kind of method and system based on pseudo- resource record OPT extension support multiple domain name record queries |
| CN108848205B (en) * | 2018-07-27 | 2021-12-28 | 北京网瑞达科技有限公司 | CNAME domain name resolution method for distinguishing IPv4 and IPv6 |
| CN109547583B (en) * | 2018-11-22 | 2022-02-25 | 中国移动通信集团江苏有限公司 | Domain name resource query method, device, equipment and computer storage medium |
| CN114731338B (en) * | 2019-12-03 | 2024-05-03 | 北京嘀嘀无限科技发展有限公司 | System and method for controlling load of domain name system server |
| CN110995888A (en) * | 2019-12-17 | 2020-04-10 | 互联网域名系统北京市工程研究中心有限公司 | Intelligent resolution method of domain name system |
| CN111010462A (en) * | 2019-12-30 | 2020-04-14 | 互联网域名系统北京市工程研究中心有限公司 | IPv6 domain name resolution method based on TRANS record |
-
2004
- 2004-09-27 CN CNB2004100666979A patent/CN100474858C/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN1756263A (en) | 2006-04-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100474858C (en) | Domain name analytic method, domain name server and domain name system | |
| US10148612B2 (en) | Method and system for increasing speed of domain name system resolution within a computing device | |
| US7558880B2 (en) | Dynamic DNS registration method, domain name solution method, DNS proxy server, and address translation device | |
| KR100453050B1 (en) | Method for communicating data between IPv4 and IPv6 and apparatus thereof | |
| CN103141074B (en) | Name database server, name resolving system, entry searching method | |
| US20070124487A1 (en) | DNS server | |
| US7415536B2 (en) | Address query response method, program, and apparatus, and address notification method, program, and apparatus | |
| KR100423500B1 (en) | Converting Apparatus for converting internet protocol address and Home network system using thereof | |
| JP4075318B2 (en) | Protocol conversion method and address conversion server | |
| CN103141073B (en) | Name database server, name resolving system, item search method and item search device | |
| US20050111384A1 (en) | Apparatus for and method of setting communication path | |
| KR20050086925A (en) | System and method for establishing communication between a client and a server in a heterogenous ip network | |
| CN101156147A (en) | Method and apparatus for handling ipv4 dns ptr queries across ipv4 and ipv6 networks | |
| DE60033162D1 (en) | FACILITATING DATA TRANSFER | |
| CN103338151A (en) | Method of accessing private network server on public network client side, and router | |
| US20040125801A1 (en) | Intermediary device and forwarding method | |
| CN107070988A (en) | Message processing method and device | |
| US7440466B2 (en) | Method, apparatus and system for accessing multiple nodes on a private network | |
| CN115668889A (en) | Domain Name System (DNS) service for Variable Length Address (VLA) networks | |
| CN114422469B (en) | IPv4/IPv6 flow intelligent scheduling method, device and scheduling system | |
| CN113472873B (en) | Method for fixing pseudo IP address to access router homepage | |
| CN107040616B (en) | Conversion method and message receiving and transmitting method for TCP/DN/IP network compatible with TCP/IP network | |
| JP2002152253A (en) | Communication management system, communication terminal, and communication management method, and program storage medium | |
| JP4288698B2 (en) | DNS proxy for IPv6 / IPv4 translator | |
| Kabelova et al. | DNS in action: A detailed and practical guide to DNS implementation, configuration, and administration |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| C56 | Change in the name or address of the patentee |
Owner name: SHANGHAI ALCATEL-LUCENT CO., LTD. Free format text: FORMER NAME: BEIER AERKATE CO., LTD., SHANGHAI |
|
| CP01 | Change in the name or title of a patent holder |
Address after: 201206 Pudong Jinqiao Export Processing Zone, Nanjing Road, No. 388, Shanghai Patentee after: Shanghai Alcatel-Lucent Co., Ltd. Address before: 201206 Pudong Jinqiao Export Processing Zone, Nanjing Road, No. 388, Shanghai Patentee before: Beier Aerkate Co., Ltd., Shanghai |
|
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 201206 Pudong Jinqiao Export Processing Zone, Nanjing Road, No. 388, Shanghai Patentee after: Shanghai NOKIA Baer Limited by Share Ltd Address before: 201206 Pudong Jinqiao Export Processing Zone, Nanjing Road, No. 388, Shanghai Patentee before: Shanghai Alcatel-Lucent Co., Ltd. |
|
| CP01 | Change in the name or title of a patent holder |