CN101729291A - Domain name inquiry method and system - Google Patents
Domain name inquiry method and system Download PDFInfo
- Publication number
- CN101729291A CN101729291A CN200910147322A CN200910147322A CN101729291A CN 101729291 A CN101729291 A CN 101729291A CN 200910147322 A CN200910147322 A CN 200910147322A CN 200910147322 A CN200910147322 A CN 200910147322A CN 101729291 A CN101729291 A CN 101729291A
- Authority
- CN
- China
- Prior art keywords
- domain name
- client
- service parameter
- inquiry
- resource record
- 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.)
- Pending
Links
Images
Landscapes
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention provides a domain name inquiry method which comprises the following steps: a client sends an inquiry packet carrying service parameters to a domain name system server, and the domain name system server returns resource records which are matched with the service parameters to the client. The invention further provides a domain name inquiry system. The adoption of the method and the system can realize that the DNS server can carry out matching processing locally according to the service parameters carried in the inquiry packet, and the resource records after matching can be directly returned to the client, thereby leading the DNS client to obtain more precise NAPTR resource records, reducing the screening burden on the client, reducing the cost of the packet and improving the inquiry efficiency.
Description
Technical field
The present invention relates to the communications field, relate in particular to the domain name inquiry method and the system that have multiple network protocol service characteristic.
Background technology
DNS (Domain Name System) domain name system is a key foundation service of internet, its conduct can be with a distributed data base of domain name and IP address mutual mapping, can make people's access internet more easily, not remember the IP string that can directly be read by machine and do not spend.
DNS is made up of following three parts:
Name space and resource record.Name space is a tree, shows the structure chart of name space tree as Fig. 1.Resource record is some data relevant with name.From conceptive, each node on the name space tree all has certain information, and some associated customizing messages are promptly obtained in inquiry.
Dns server.Dns server is a server program, it keeps tree of domain names structure and corresponding information, it can cushion various data, preserve any part in the tree of domain names, but it preserves a subclass of name space usually, inquires about out of Memory if desired and can seek by the address of pointing to other dns server.This dns server is this a part of certification authority (CA), and all authentication informations are formed a unit and are called the district, and these districts can be distributed on the different servers to guarantee the redundancy of data.
Resolver (Resolver).Resolver proposes query requests and the result is returned to client's program to dns server, and it must visit at least one dns server, and the result is directly returned to the user or to other dns server inquiry.It is the systems approach that can visit of user normally, does not need agreement between Resolver and user program.
In simple terms, the using method of DNS is as described below.For a name is mapped to address information, the process in the storehouse of a Resolver by name of application call, and this name passed to this process as parameter.Fig. 2 shows the flow process that application call Resolver carries out domain name mapping.Resolver sends a UDP message or TCP message to dns server, dns server is searched this name, and the IP address of finding is returned to resolver, and Resolver returns to application program with the IP address again, and application program just can be carried out IP with target machine and communicated by letter like this.
Fig. 3 is the structure of the problem part of existing DNS message, comprises query name (QNAME), query type (QTYPE) and three territories of inquiry class (QCLASS), the name that query name promptly will be searched, the resource record types that query type promptly will be searched, inquiry class normally 1 refers to internet address.
DNS provides multiple RR (Resource Record, resource record) inquiry service of type, and promptly each domain name can have one group of resource record that is associated with it.Such as the most frequently used A/AAAA class inquiry, be the IPv4/IPv6 address lookup that carries out the domain name correspondence.The resource record that also has many other kinds in addition.When Resolver passed to dns server to a domain name, dns server returned the resource record that is associated with this domain name.Therefore, basic function that we can say dns server is that domain name is mapped on the resource record.
As shown in Figure 4, resource record is made up of 6 territories, comprising:
Name (NAME) is represented the domain name of this resource record correspondence, variable-length.
Type (TYPE), i.e. the type of resource record, length is 2 bytes.
Class (CLASS), the class of resource record, length are 2 bytes.
Life span (TTL, Time to Live), unit is second, represents the cache-time of this resource record, length is 32bit.
The data length of resource record (RDLENGTH) refers to the length (is unit with the byte) of resource record data division, and length is 16bit.
Resource record data (RDATA), the data division of resource record, the data structure of dissimilar resource records is inequality, variable-length.
There is a kind of NAPTR of being named as (Name Authority Pointer in the prior art, the inquiry of the resource record domain name grant pointers), it is a kind of new DNS RR resource record types, it is actually a regular expression based on rewriting rule, finishes the parsing translation of a specific character string to the new domain name sign.It allows DNS to finish inquiry service more widely.Briefly, by NAPTR class resource record inquiry to specific character string, one or more domain-name informations that can obtain to be correlated with, and in these information, comprise network service and the protocol characteristic that domain name representative main frame provides.Fig. 5 shows the message structure of naptr resource record type, comprises six territory: order (order), preference (priority), flags (sign), services (service parameter), regexp regular expression) and replacement (replacement value).Fig. 6 shows the flow chart of NAPTR inquiry, input domain name " example.com ", and after the NAPTR routine processes, the naptr resource record of three correspondences of output.
An important parameter is arranged: service parameter (Service Parameter) in the naptr resource record, according to the definition among the RFC3958, service parameter is made up of " app-service (application service) " and " service-protocol (application protocol) ", and concrete definition is decided in its sole discretion by various application.In 3GPP with network node types corresponding to " app-service ", the interface that node is supported is corresponding to " app-protocol ".Promptly express support for P-GW on the PMIP s2b interface such as " x-3gpp-pgw:x-s2b-pmip ".
The inquiry of NAPTR class is highly suitable for the discovery and the selection of System Architecture Evolution (System Architecture Evolution abbreviates SAE as) network element.SAE also can become EPS (grouping system of evolution, Evolved Packet System).The network element of SAE network portion is used to provide the bearer management and the mobile management of bottom.Fig. 7 shows the network architecture under the non-roaming scene of SAE.The network element of SAE network portion comprises: the wireless base station of enhancing (eNodeB), Mobility Management Entity (Mobility ManagementEntity abbreviates MME as) and user face data route processing net element (SAE GW); SAE GW comprises packet data network gateway (Packet Data Network Gateway abbreviates P-GW as) and gateway (Serving GW abbreviates S-GW as).The context that MME was in charge of and stored UE (for example, UE sign/user ID, mobility management states, user security parameters, carry out the DNS inquiry of P-GW etc.), for the user distributes temporary mark, when UE quarters at tracing area or network, be responsible for UE is carried out authentication.P-GW is the intrasystem mobile anchor point of SAE, is the borde gateway of SAE and packet data network (Packet Data Network abbreviates PDN as), is responsible for the access of PDN, transmits function such as data between SAE and PDN.
The PDN that UE sets up based on distinct interface and agreement under different scenes is connected, and this just needs MME to carry out P-GW DNS inquiry, and the naptr resource record that obtains is carried out the corresponding interface and the coupling of agreement.Under prior art, dns server can return the naptr resource record of finding that comprises all Service information usually, carries out the needed NAPTR information of Service screening coupling by DNS client self.Because response message may carry many naptr resource records, increased the expense of message, and the DNS client also will travel through screening for unwanted resource record, has reduced search efficiency.
Summary of the invention
Technical problem to be solved by this invention provides a kind of domain name inquiry method and system, improves the DNS client-side productivity.
In order to address the above problem, the invention provides a kind of domain name inquiry method, comprise: client sends query message to domain name system server, carries service parameter in described query message, and the domain name system server returns with the resource record of described service parameter coupling and gives client.
Further, said method also can have following characteristics, comprises interface and/or protocol information in the described service parameter.
Further, said method also can have following characteristics, also comprises the function information that described interface is supported in the described service parameter.
Further, said method also can have following characteristics, and described client is carried service parameter in the following way: increase by an inquiry service territory in query message, carry described service parameter.
Further, said method also can have following characteristics, also carries domain name and the query type that will inquire about in the described query message, and wherein, described query type is a domain name grant pointers class;
After the domain name system server inquires all domain name grant pointers resource records corresponding with the described domain name that will inquire about, mate with described service parameter, the domain name grant pointers resource record that matches is included in sends to described client in the response message.
The present invention also provides a kind of domain name inquiry system, comprising: client and domain name system server, wherein:
Described client is used for sending query message to domain name system server, carries service parameter in described query message;
The domain name system server is used to receive the query message of described client, returns with the resource record of described service parameter coupling and gives client.
Further, said system also can have following characteristics, comprises interface and/or protocol information in the described service parameter.
Further, said system also can have following characteristics, also comprises the function information that described interface is supported in the described service parameter.
Further, said system also can have following characteristics, and described client is used for increasing by an inquiry service territory in described query message, carries described service parameter.
Further, said system also can have following characteristics, and described client also is used for carrying domain name and the query type that will inquire about in query message, and described query type is a domain name grant pointers class;
The domain name system server, also be used to inquire about all domain name grant pointers resource records corresponding with the described domain name that will inquire about, mate with service parameter, the domain name grant pointers resource record that matches is included in sends to described client in the response message.
Adopt method of the present invention, service parameter is carried in a newly-increased inquiry service (Query Service) territory in DNS NAPTR query message, make dns server can carry out the matching treatment of protocol service characteristic in this locality according to the service parameter that query message is carried, resource record after the coupling is directly returned to client, thereby make the DNS client can obtain more accurate naptr resource record, reduce the screening burden of client, reduced the expense of message, improved search efficiency.
Description of drawings
Fig. 1 shows the structure of name space tree;
Fig. 2 shows the flow process that application call Resolver carries out domain name mapping;
Fig. 3 is the problem part-structure schematic diagram of existing DNS query message;
Fig. 4 is the resource record part schematic diagram of DNS message;
Fig. 5 shows the message structure of naptr resource record type;
Fig. 6 shows the flow process of existing NAPTR inquiry;
Fig. 7 shows the network architecture under the non-roaming scene of SAE;
Fig. 8 is the structure that the problem of DNS query message is partly expanded of the invention process, increases the inquiry service territory (QSERVICE) of a variable-length;
Fig. 9 shows that SAE network mobility management entity (MME) under the invention process is to the DNS NAPTR querying flow figure of packet data network gateway (P-GW);
Figure 10 shows Release-8 Serving GPRS Support Node (SGSN) in the SAE network under the invention process or the MME DNS NAPTR querying flow figure to S-GW;
Figure 11 shows main frame in the network under the invention process to desired service DNS NAPTR querying flow.
Embodiment
Describe the present invention below in conjunction with drawings and Examples.
Core concept of the present invention is, when client sends query message, carries service parameter, and dns server returns the resource record with the service parameter coupling.
Because the restriction of query message problem part can't be carried Service information, the present invention expanded the query message Problem Areas when DNS client was carried out the inquiry of DNS NAPTR class.Fig. 8 is the structure of the problem part of the DNS message expanded of the present invention, partly increase inquiry service territory (QSERVICE) in former problem, be the variable-length territory, service parameter is carried in this inquiry service territory, service parameter can be interface and/or protocol information, and its definition can be consistent with " Service Parameters " among the RFC3958.When query type (QTYPE) was the NAPTR type, dns server can carry out further NAPTR resource type coupling according to QSERVICE in the process of carrying out the NAPTR inquiry, thus the naptr resource record of output and inquiry service territory content match.
In addition, the incoming end node that hope is searched under certain scene also will be supported the function that some are specific, such as supporting many PDN to connect and stream migration (MAPIM, Multi Access PDN connectivity andIP flow mobility) or based on the many PDN on the PMIP interface of same APN connect (MAPSUP, Multiple PDN Connection to the Same APN for PMIP-basedInterfaces) etc., the present invention also carries the function information that interface is supported in the inquiry service territory, when the service parameter in dns server and the inquiry service territory mates, except matched interfaces and agreement, the function that also further matched interfaces is supported.
Fig. 9 with MME in the SAE network to dns server inquiry service type for the naptr resource record of the packet data network gateway P-GW of " x-3gpp-pgw:x-s5-pmip " be example present invention is described, specifically comprise the steps:
Step 901, MME is converted to the complete domain name of APN according to the value of the APN that send on the UE (Access PointNetwork, access network) according to certain rule, sends query message as the nslookup of DNS NAPTR to dns server.Here, suppose that the domain name that the complete domain name of APN is promptly inquired about is imsTV2.apn.epc.mnc990.mcc311.3gppnetwork.org, query type is the NAPTR class, the inquiry service territory is x-3gpp-pgw:x-s5-pmip, the COS support of the naptr resource record of the P-GW of expression hope feedback is based on the PMIP on the s5 interface (Proxy Mobile IP, proxy mobile internet protocol) agreement.
Step 902, dns server sends response message to MME, and the answer of message partly comprises the naptr resource record information of all matching inquiry service-domain x-3gpp-pgw:x-s5-pmip in the resource record of domain name correspondence of inquiry.
If among Fig. 9 MME except the COS support of the naptr resource record of the P-GW of hope feedback based on the PMIP agreement on the s5 interface, also to support mapsup (connecting) or mapim (supporting many PDN to connect supports many PDN to be connected and stream migration with stream migration) functional characteristic based on the many PDN on the PMIP interface of same APN, then in the QSERVICE that carries, increase the one-level functional description, specifically describe as follows:
Step 901a, MME is converted to the complete domain name of APN according to the value of the access network APN that send on the UE (Access Point Network) according to certain rule, sends query message as the nslookup of DNS NAPTR to dns server.Here, suppose that the domain name that the complete domain name of APN is promptly inquired about is imsTV2.apn.epc.mnc990.mcc311.3gppnetwork.org, query type is the NAPTR class, the inquiry service territory be x-3gpp-pgw:x-s5-pmip-mapsup (or-mapim), the COS of the naptr resource record of the P-GW of expression hope feedback is based on the PMIP agreement on the s5 interface, and supports MAPSUP (perhaps mapim) function.
Step 902a, dns server sends response message to MME, the answer of message partly comprise all matching inquiry service-domain x-3gpp-pgw:x-s5-pmip-mapsup (or-mapim) naptr resource record information.
Figure 10 is example to dns server inquiry service type for the naptr resource record of the gateway S-GW of " x-3gpp-sgw:x-s5-gtp " with Release-8SGSN (or MME) in the SAE network, and present invention is described, specifically comprises the steps:
Step 1001, MME (perhaps Release-8SGSN) sends query message to dns server, the domain name of inquiring about is tac-lb11.tac-hb40.tac.3gppnetwork.org, query type is the NAPTR class, the inquiry service territory is x-3gpp-sgw:x-s5-gtp, and the COS of the naptr resource record of the P-GW of expression hope feedback is based on the GTP agreement on the s5 interface.
Step 1002, dns server sends response message to MME (perhaps Release-8SGSN), and the answer of response message partly comprises the naptr resource record information of all matching inquiry service-domain x-3gpp-sgw:x-s5-gtp.
Figure 11 has described more general a kind of embodiment.A main frame that is linked into Internet is to the naptr resource record of dns server nslookup for " example.com ", in the inquiry service territory, insert the resource record that " serviceX:protocolY " promptly search and comprise the protocolY agreement of supporting under the serviceX service, specifically comprise the steps:
Step 1102, the naptr resource record that dns server finds domain name example.com correspondence has three, further matching inquiry service-domain, hit the 3rd resource record, dns server sends response message to main frame, and the answer of message partly comprises the resource record of matching inquiry service-domain serviceX:protocolY.
With Fig. 6 more as can be known, the present invention is screened resource record by dns server, has reduced the message expense, has reduced the screening burden of client, has improved search efficiency.
The invention is not restricted to the SAE network.
Claims (10)
1. domain name inquiry method, it is characterized in that, comprise: client sends query message to domain name system server, carries service parameter in described query message, and the domain name system server returns with the resource record of described service parameter coupling and gives client.
2. the method for claim 1 is characterized in that, comprises interface and/or protocol information in the described service parameter.
3. method as claimed in claim 2 is characterized in that, also comprises the function information that described interface is supported in the described service parameter.
4. the method for claim 1 is characterized in that, described client is carried service parameter in the following way: increase by an inquiry service territory in query message, carry described service parameter.
5. as the arbitrary described method of claim 1 to 4, it is characterized in that, also carry domain name and the query type that will inquire about in the described query message, wherein, described query type is a domain name grant pointers class;
After the domain name system server inquires all domain name grant pointers resource records corresponding with the described domain name that will inquire about, mate with described service parameter, the domain name grant pointers resource record that matches is included in sends to described client in the response message.
6. a domain name inquiry system is characterized in that, comprising: client and domain name system server, wherein:
Described client is used for sending query message to domain name system server, carries service parameter in described query message;
The domain name system server is used to receive the query message of described client, returns with the resource record of described service parameter coupling and gives client.
7. system as claimed in claim 6 is characterized in that, comprises interface and/or protocol information in the described service parameter.
8. system as claimed in claim 7 is characterized in that, also comprises the function information that described interface is supported in the described service parameter.
9. system as claimed in claim 6 is characterized in that, described client is used for increasing by an inquiry service territory in described query message, carries described service parameter.
10. as the arbitrary described system of claim 6 to 9, it is characterized in that,
Described client also is used for carrying domain name and the query type that will inquire about in query message, and described query type is a domain name grant pointers class;
The domain name system server, also be used to inquire about all domain name grant pointers resource records corresponding with the described domain name that will inquire about, mate with service parameter, the domain name grant pointers resource record that matches is included in sends to described client in the response message.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200910147322A CN101729291A (en) | 2009-06-11 | 2009-06-11 | Domain name inquiry method and system |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200910147322A CN101729291A (en) | 2009-06-11 | 2009-06-11 | Domain name inquiry method and system |
Publications (1)
Publication Number | Publication Date |
---|---|
CN101729291A true CN101729291A (en) | 2010-06-09 |
Family
ID=42449563
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN200910147322A Pending CN101729291A (en) | 2009-06-11 | 2009-06-11 | Domain name inquiry method and system |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN101729291A (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102075592A (en) * | 2010-12-30 | 2011-05-25 | 吕晓雯 | Method for screening DNS (Domain Name System) request |
CN103222252A (en) * | 2010-12-02 | 2013-07-24 | 瑞典爱立信有限公司 | Service access apparatus, method, computer program and computer program product for selective initiation of communication |
CN104065734A (en) * | 2014-07-02 | 2014-09-24 | 北京润通丰华科技有限公司 | Method and system for file transmission via DNS |
CN114697393A (en) * | 2020-12-28 | 2022-07-01 | 北京金山云网络技术有限公司 | Data storage method, device, equipment and medium |
-
2009
- 2009-06-11 CN CN200910147322A patent/CN101729291A/en active Pending
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103222252A (en) * | 2010-12-02 | 2013-07-24 | 瑞典爱立信有限公司 | Service access apparatus, method, computer program and computer program product for selective initiation of communication |
CN102075592A (en) * | 2010-12-30 | 2011-05-25 | 吕晓雯 | Method for screening DNS (Domain Name System) request |
CN104065734A (en) * | 2014-07-02 | 2014-09-24 | 北京润通丰华科技有限公司 | Method and system for file transmission via DNS |
CN114697393A (en) * | 2020-12-28 | 2022-07-01 | 北京金山云网络技术有限公司 | Data storage method, device, equipment and medium |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN1965515B (en) | Arrangement for reaching IPv4 public network nodes by a node in an IPv4 private network via an IPv6 access network | |
CN101420762B (en) | Access gateway selection method, system and gateway selection execution node | |
US7313631B1 (en) | DNS updating in communication network | |
CA2464065C (en) | Method and apparatus for resolving an entity identifier into an internet address using a domain name system (dns) server and an entity identifier portability database | |
CN101483672B (en) | Processing method, system, gateway server and mobile terminal for service information access | |
AU2004303189B2 (en) | Reachability maintainance on a moving network based on temporary name identifiers | |
US8953609B1 (en) | Packet-data-network-specific addressing solutions for clients relying on proxy-based mobility | |
US9584466B2 (en) | Method of establishing an IP connection in a mobile network and various corresponding equipment items | |
US9485799B2 (en) | Method to connect a mobile node to a network | |
US20190174451A1 (en) | Method and device for supplying location information to an apparatus connected to a network access point | |
CN111866201B (en) | IPv6 multicast address generation method and device | |
JP4699530B2 (en) | Methods, systems, and applications for service addressing | |
JP2004364271A (en) | Mobile router, location management server, mobile network management system, and mobile network management method | |
CN101729291A (en) | Domain name inquiry method and system | |
US7447162B1 (en) | Methods and apparatus for anchoring of mobile nodes using DNS | |
CN101938789B (en) | Method and system for selecting packet network gateway with designated capability | |
CN106792657B (en) | A kind of network identity method and device for supporting identity and position to decouple | |
JP2019087908A (en) | IPv6 network system, home gateway device, migration technology application method, and application program | |
FI113996B (en) | Subscriber ID Portability | |
KR102185665B1 (en) | Server, Terminal, Method, and Recording Medium for IPv6-based Communication in All-IP environment | |
CN101754173B (en) | Home address allocation, method and system for transmitting message by using same | |
US20230421527A1 (en) | Method and apparatus for supporting remote access to internet of things device connected to private networks | |
Gohar et al. | A hash‐based distributed mapping control scheme in mobile locator‐identifier separation protocol networks | |
CN102684972A (en) | Communication method and communication system compatible with IP (internet protocol)v4 address | |
KR101288875B1 (en) | System and method for processing data call of roaming subscriber |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
C12 | Rejection of a patent application after its publication | ||
RJ01 | Rejection of invention patent application after publication |
Application publication date: 20100609 |