CN106412000A - Domain name query processing method - Google Patents
Domain name query processing method Download PDFInfo
- Publication number
- CN106412000A CN106412000A CN201610598887.8A CN201610598887A CN106412000A CN 106412000 A CN106412000 A CN 106412000A CN 201610598887 A CN201610598887 A CN 201610598887A CN 106412000 A CN106412000 A CN 106412000A
- Authority
- CN
- China
- Prior art keywords
- domain name
- inquiry
- query
- domain
- suffix
- 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.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/30—Managing network names, e.g. use of aliases or nicknames
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
The invention discloses a domain name query processing method. The method comprises the steps of receiving domain name query request information and obtaining multiple pieces of domain name query request data comprising domain name bodies and domain name suffixes; grouping the obtained domain name query request data according to the domain name suffixes and carrying out batched asynchronous query on domain names in each domain name suffix group by taking a preset value as a unit; obtaining query interfaces corresponding to the domain name suffixes and query server addresses corresponding to the query interfaces from a configuration file; sending the domain name query request data with the same domain name suffixes to the corresponding query servers for domain name query, wherein the domain name query data take the preset value as the unit; and receiving and analyzing domain name query results returned by the query servers. According to the domain name query method provided by the invention, the domain name query times and the query pressure of the query servers are reduced, the query response time is accelerated, and moreover, a query success rate is improved.
Description
Technical field
The present invention relates to field of computer technology, particularly to a kind of processing method of inquiry of the domain name.
Background technology
Inquiry of the domain name is to go whether nslookup can be registered by registration office, facilitates user to carry out domain name registration.Generally
Inquiry of the domain name has two ways, and one kind is single inquiry of the domain name, and another kind is that multiple domain names are inquired about together, and at present, great majority are used
The family multiple domain name themes of selection are added a domain suffix and are inquired about together.But, the inquiry due to registration office limits, and inquiry of the domain name is every
Secondary at most can only inquire about 5 domain names, inquiry of the domain name excessively frequently can lead to network timeout problem, impact search efficiency and user's body
Test.
Content of the invention
In view of the above problems, the present invention provides a kind of a kind of domain name overcoming the problems referred to above or solving the above problems at least in part
The processing method of inquiry.
The technical solution adopted for the present invention to solve the technical problems is:
A kind of processing method of inquiry of the domain name, including:
Receive inquiry of the domain name solicited message, obtain and include domain name main body and the inquiry of the domain name request data of domain suffix, domain name
Request data includes one or more;
The inquiry of the domain name getting request data is grouped by domain suffix, and by the domain name in each domain suffix group with preset value
Asynchronous query is conducted batch-wise for unit;
The corresponding query interface of domain suffix and query interface corresponding inquiry server address is obtained from configuration file;
Identical for domain suffix and in units of preset value inquiry of the domain name request data is sent to corresponding inquiry server carry out
Inquiry of the domain name;
Receive and parse through the inquiry of the domain name result that inquiry server returns.
Preferably, when a domain suffix corresponds to multiple queries interface, when a domain suffix corresponds to multiple queries interface, every time
Randomly choose a query interface corresponding inquiry server to go to carry out inquiry of the domain name.
Preferably, described inquiry server includes master server and standby server, and acquiescence sends domain name inquiry request data to master
Server.
Preferably, if Query Result is unsuccessfully and failure cause is network timeout, inquiry of the domain name request data is sent to correspondence
Standby server inquired about.
Preferably, described the inquiry of the domain name getting request data is grouped by domain suffix, and by each domain suffix group
Before domain name is conducted batch-wise asynchronous query in units of preset value, also include:Detection domain name inquiry request data, if described domain
Name inquiry request data is not inconsistent and normally confirms inquiry of the domain name failure.
Preferably, described rule includes the judgement to domain name body format, domain name principal length and this inquiry of the domain name total quantity.
Preferably, described obtain from configuration file the corresponding query interface of domain suffix and the corresponding interface IP address of query interface it
Before, also include:Detect the inquiry of the domain name request data receiving, if domain name inquiry request data is not inconsistent normally confirmed
Inquiry of the domain name failure.
Preferably, described rule include to Domain Name Form registering sites, domain name length and be whether legitimate request judgement.
Preferably, described identical for domain suffix and in units of preset value inquiry of the domain name request data is sent to corresponding interface
Address carry out inquiry of the domain name and described receive and parse through interface IP address return inquiry of the domain name result between, including:
Domain name inquiry request data conversion is become inquiry xml document by inquiry server calls xml operation class, and according to domain name
The difference of suffix adds corresponding xml extension in inquiry xml document;
Inquiry server connects domain name registration office, and the inquiry xml document that transmission generates carries out domain name to each domain name registration office and looks into
Ask;
Inquiry server receives the Query Result of xml form of each domain name registration office return and returns Query Result.
A kind of processing method of inquiry of the domain name of the present invention, domain name supervising main frame receives inquiry of the domain name solicited message, obtains and includes domain
Name main body and a plurality of inquiry of the domain name request data of domain suffix, and then the demand of the multiple domain name of one query can be met;To obtain
The inquiry of the domain name request data got is grouped by domain suffix, and the domain name in each domain suffix group is divided in units of preset value
Batch carry out asynchronous query, thus using the inquiry of the domain name upper limit of registration office as the domain name one query of system the upper limit, at utmost
Upper minimizing inquiry of the domain name number of times;Randomly choosed by way of the acquisition corresponding query interface of domain suffix random from configuration file
Inquiry server, reduces server domain name inquiry pressure, also accelerates query responding time;Inquiry server includes master server
And standby server, give tacit consent to and inquired about using master server, when network timeout in Query Result, system is switched to standby clothes
Business device is inquired about, and improves the success rate of inquiry.
Described above is only the general introduction of technical solution of the present invention, in order to more clearly understand the technological means of the present invention, thus
Can be practiced according to the content of description, and in order to allow the above and other objects, features and advantages of the present invention can be brighter
Aobvious understandable, it is exemplified below the specific embodiment of the present invention.
According to the detailed description to the specific embodiment of the invention below in conjunction with accompanying drawing, those skilled in the art will become more apparent that this
The above-mentioned and other purpose of invention, advantages and features.
Brief description
Fig. 1 is the main flow chart of the domain name inquiry method of the present invention;
Fig. 2 is the flow chart of a preferred embodiment of domain name inquiry method of the present invention;
Fig. 3 is the xml format chart of the inquiry of the domain name request of the present invention.
Specific embodiment
For making the object, technical solutions and advantages of the present invention clearer, below in conjunction with accompanying drawing embodiment of the present invention is made into
The detailed description of one step.
It should be noted that the executive agent of the method for present embodiment be terminal, described terminal can for mobile phone, panel computer,
The equipment such as palm PC PDA, notebook or desktop computer, it is, of course, also possible to have the equipment of identity function, this enforcement for other
Mode is not any limitation as.
Referring to Fig. 1, a kind of processing method of inquiry of the domain name of the present invention, comprise the steps:
Step 101:Receive inquiry of the domain name solicited message, acquisition includes domain name main body and some inquiries of the domain name of domain suffix please
Seek data.
Specifically, described inquiry request information includes one or more domain name main bodys and the combination of one or more domain suffix.This
In embodiment, 100 can be less than in the domain name of inquiry of the domain name interface input, domain suffix selects by way of choosing.Need
It is noted that the domain name in the input of inquiry of the domain name interface can be domain name main body or the domain name including suffix, such as
Fruit input is domain name main body, and the domain name request data of generation is the domain name main body of input and combining of the domain suffix selecting, such as
What fruit inputted is the domain name including suffix, then the domain name request data producing only includes the domain name inputting, and will not go combination selection again
Suffix.Domain name as the input of inquiry of the domain name interface is " a.com " and " b ", suffix option " .com ", " .net ", " .cn ",
The inquiry request data then actually generating includes:“a.com”、“b.com”、“b.net”、“b.cn”.
It will be appreciated that user's triggering domain name inquiry request can be carried out, such as in several ways:By click client
The interaction triggering element at end, or click on the interaction triggering element of client on the touchscreen, present embodiment is not any limitation as to this.
Step 102:The inquiry of the domain name getting request data is grouped by domain suffix, and by the domain in each domain suffix group
Name is conducted batch-wise asynchronous query in units of preset value.
Specifically, after front end gets legal inquiry of the domain name request, the domain name of requesting query can be grouped by suffix, often
The domain name of group suffix is again asynchronous in units of 5 to send domain name inquiry request to the back-end.When the domain name quantity of one group of suffix is less than 5
When individual, send domain name inquiry request by current domain name number, when the domain name quantity of one group of suffix is more than 5, can carry out several times
Inquiry, sends inquiry request to the back-end less than or equal to 5 domain names every time.If any 8 com domain names whenever necessary, can send
Inquiry of the domain name twice is asked, and sends 5 inquiry of the domain name requests for the first time, can send 3 inquiry of the domain name requests for second.
Step 103:The corresponding query interface of domain suffix and query interface corresponding inquiry server ground is obtained from configuration file
Location.
Specifically, after rear end receives the inquiry request of domain name, domain suffix is got for corresponding inquiry by configuration file
Interface.The query interface of each suffix defined in configuration file, each suffix may correspond to one or more interfaces, interface pair
Answer the registrar of registration office or cooperation.Obtain an interface when the corresponding multiple queries interface of a domain suffix at random, each connects
The function of mouth is the same, and simply the address of interface is different, and program can obtain this interface according to query interface from configuration file
The interface IP address of corresponding bottom inquiry of the domain name, assembling query argument is simultaneously sent to query interface and carries out inquiry of the domain name operation.
Step 104:Identical for domain suffix and in units of preset value inquiry of the domain name request data is sent to corresponding inquiry clothes
Business device carries out inquiry of the domain name.
Specifically, after inquiry server receives the domain name request of domain name supervising main frame transmission, according to query argument domain, launch
Call xml operation class, and the query expansion according to domain suffix interpolation domain name, such as premium extension, generate the xml of registration office inquiry
Format parameter, as shown in Figure 3.Then inquiry server is connected with registration office, sends xml query argument, the phase of nslookup
Pass information.
Step 105:Receive and parse through the inquiry of the domain name result that inquiry server returns.
Specifically, the xml of inquiry is sent to after registration office by inquiry server, and registration office can return the xml with Query Result,
The xml that registration office returns is carried out parsing and again registration office is returned to domain name supervising main frame by inquiry server, and domain name supervising main frame connects
Receive and parse Query Result and be prompted to user.
In the embodiment of the processing method of inquiry of the domain name of the present invention, domain name supervising main frame can receive inquiry of the domain name solicited message, obtains
Take a plurality of inquiry of the domain name request data including domain name main body and domain suffix, and then the multiple domain name of one query can be met
Demand;The inquiry of the domain name getting request data is grouped by domain suffix, and by the domain name in each domain suffix group with default
It is worth and asynchronous query is conducted batch-wise for unit, thus the inquiry of the domain name upper limit of registration office is upper as the domain name one query of system
Limit, reduces inquiry of the domain name number of times to the full extent;By the acquisition corresponding query interface of domain suffix random from configuration file
Mode randomly chooses inquiry server, reduces server domain name inquiry pressure, also accelerates query responding time;Inquiry server
Including master server and standby server, acquiescence is inquired about using master server, when network timeout, system in Query Result
It is switched to standby server to be inquired about, improve the success rate of inquiry.
Be the processing method of the inquiry of the domain name of the embodiment of the present invention is illustrated must become apparent from clearer, now with a particular flow sheet pair
It illustrates.The flow chart that Fig. 2 shows domain name inquiry method according to a preferred embodiment of the present invention.Referring to Fig. 2,
Method at least includes:
Step 201:Receive inquiry of the domain name solicited message, acquisition includes domain name main body and some inquiries of the domain name of domain suffix please
Seek data.
Specifically, described inquiry request information includes one or more domain name main bodys and the combination of one or more domain suffix.This
In embodiment, 100 can be less than in the domain name of inquiry of the domain name interface input, domain suffix selects by way of choosing.
Step 202:Detection domain name inquiry request data, if domain name inquiry request data fit is regular, execution step 203,
Otherwise prompting user error reason, so that user re-enters.
Specifically, described rule includes the judgement to domain name body format, domain name principal length and this inquiry of the domain name total quantity.
Step 203:The inquiry of the domain name getting request data is grouped by domain suffix, and by the domain in each domain suffix group
Name is conducted batch-wise asynchronous query in units of preset value.
Specifically, after front end gets legal inquiry of the domain name request, the domain name of requesting query can be grouped by suffix, often
The domain name of group suffix is again asynchronous in units of 5 to send domain name inquiry request to the back-end.When the domain name quantity of one group of suffix is less than 5
When, send domain name inquiry request by current domain name number, when the domain name quantity of one group of suffix is more than 5, can be looked into several times
Ask, send inquiry request to the back-end less than or equal to 5 domain names every time.If any 8 com domain names whenever necessary, domain twice can be sent
Name inquiry request, sends 5 inquiry of the domain name requests for the first time, can send 3 inquiry of the domain name requests for second.
Step 204:Detection domain name inquiry request data, if domain name inquiry request data fit is regular, execution step 205,
Otherwise, execution step 209, point out error reason.
Specifically, described rule include to Domain Name Form registering sites, domain name length and be whether legitimate request judgement.Whether described be conjunction
The judgement of method request is mainly used for judging, when the number of user's inquiry of the domain name is more than 5, judging whether request is derived from this domain name
Management system.Because using asynchronous query, prevent malice from inquiring about.
Step 205:The corresponding query interface of domain suffix and query interface corresponding inquiry server ground is obtained from configuration file
Location.
Specifically, after rear end receives the inquiry request of domain name, domain suffix is got for corresponding inquiry by configuration file
Interface.The query interface of each suffix defined in configuration file, each suffix may correspond to one or more interfaces, interface pair
Answer the registrar of registration office or cooperation.Obtain an interface when the corresponding multiple queries interface of a domain suffix at random, each connects
The function of mouth is the same, and simply the address of interface is different, and program can obtain this interface according to query interface from configuration file
The interface IP address of corresponding bottom inquiry of the domain name, assembling query argument is simultaneously sent to query interface and carries out inquiry of the domain name operation.As
The domain suffix of cn can correspond to 2,3,9,13,15 totally 5 interfaces, and rear end randomly selects an interface and inquired about.
Step 206:Identical for domain suffix and in units of preset value inquiry of the domain name request data is sent to corresponding inquiry clothes
Business device carries out inquiry of the domain name.
Specifically, after inquiry server receives the domain name request of domain name supervising main frame transmission, according to query argument domain, launch
Call xml operation class, and the query expansion according to domain suffix interpolation domain name, such as premium extension, generate the xml of registration office inquiry
Format parameter, as shown in Figure 3.Then inquiry server is connected with registration office, sends xml query argument, the phase of nslookup
Pass information.
Step 207:Receive and parse through the inquiry of the domain name result that inquiry server returns.
Specifically, registration office can return the xml with Query Result, and the xml that registration office returns is solved by inquiry server
Registration office is returned to domain name supervising main frame by analysis again, and domain name supervising main frame receives and parses through Query Result.
Step 208:Detection domain name Query Result.
If returning result is successful inquiring, execution step 209, registration office return Query Result is prompted to user;Otherwise,
Analysis inquiry failure cause, if failure cause is network timeout, enables standby server, execution step 206 is inquired about again,
If failure cause is not network timeout, execution step 209, registration office return Query Result is prompted to user.Should be noted
If standby server Query Result remains as failure, direct execution step 209.
Step 209:Page display processing result.
Specifically, the Query Result after parsing is prompted to user by domain name supervising main frame.
Described above is only the general introduction of technical solution of the present invention, in order to more clearly understand the technological means of the present invention, thus
Can be practiced according to the content of description, and in order to allow the above and other objects, features and advantages of the present invention can be brighter
Aobvious understandable, it is exemplified below the specific embodiment of the present invention.
The foregoing is only presently preferred embodiments of the present invention, not in order to limit the present invention, all the spirit and principles in the present invention it
Interior, any modification, equivalent substitution and improvement made etc., should be included within the scope of the present invention.
Claims (9)
1. a kind of processing method of inquiry of the domain name is it is characterised in that include:
Receive inquiry of the domain name solicited message, obtain and include domain name main body and the inquiry of the domain name request data of domain suffix, domain name
Request data includes one or more;
The inquiry of the domain name getting request data is grouped by domain suffix, and by the domain name in each domain suffix group with preset value
Asynchronous query is conducted batch-wise for unit;
The corresponding query interface of domain suffix and query interface corresponding inquiry server address is obtained from configuration file;
Identical for domain suffix and in units of preset value inquiry of the domain name request data is sent to corresponding inquiry server carry out
Inquiry of the domain name;
Receive and parse through the inquiry of the domain name result that inquiry server returns.
2. the processing method of inquiry of the domain name according to claim 1 is it is characterised in that a domain suffix correspondence is multiple
During query interface, randomly choose a query interface corresponding inquiry server every time and carry out inquiry of the domain name.
3. the processing method of inquiry of the domain name according to claim 2 is it is characterised in that described inquiry server includes leading
Server and standby server, acquiescence sends domain name inquiry request data to master server.
If 4. the processing method of inquiry of the domain name according to claim 3 it is characterised in that Query Result be unsuccessfully and
Failure cause is network timeout, inquiry of the domain name request data is sent to corresponding standby server and is inquired about.
5. the processing method of inquiry of the domain name according to claim 1 is it is characterised in that described look into the domain name getting
Ask request data and press domain suffix packet, and the domain name in each domain suffix group is conducted batch-wise asynchronous looking in units of preset value
Before inquiry, also include:Detection domain name inquiry request data, if domain name inquiry request data is not inconsistent normally confirmation domain name
Inquire about unsuccessfully.
6. the processing method of inquiry of the domain name according to claim 5 is it is characterised in that described rule is included to domain name master
The judgement of physique formula, domain name principal length and this inquiry of the domain name total quantity.
7. the processing method of inquiry of the domain name according to claim 1 is it is characterised in that described obtain from configuration file
Before the corresponding query interface of domain suffix and the corresponding interface IP address of query interface, also include:Detect the inquiry of the domain name receiving
Request data, if domain name inquiry request data is not inconsistent normally confirms inquiry of the domain name failure.
8. the processing method of inquiry of the domain name according to claim 7 is it is characterised in that described rule is included to domain name lattice
Formula, domain name length and be whether legitimate request judgement.
9. inquiry of the domain name according to claim 1 processing method it is characterised in that described by identical for domain suffix and
Inquiry of the domain name request data in units of preset value is sent to corresponding inquiry server and carries out inquiry of the domain name with described reception simultaneously
Between the inquiry of the domain name result that parsing inquiry server returns, including:
Domain name inquiry request data conversion is become inquiry xml document by inquiry server calls xml operation class, and according to domain name
The difference of suffix adds corresponding xml extension in inquiry xml document;
Inquiry server connects domain name registration office, and the inquiry xml document that transmission generates carries out domain name to each domain name registration office and looks into
Ask;
Inquiry server receives the Query Result of xml form of each domain name registration office return and returns Query Result.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201610598887.8A CN106412000B (en) | 2016-07-27 | 2016-07-27 | A kind of processing method of inquiry of the domain name |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201610598887.8A CN106412000B (en) | 2016-07-27 | 2016-07-27 | A kind of processing method of inquiry of the domain name |
Publications (2)
Publication Number | Publication Date |
---|---|
CN106412000A true CN106412000A (en) | 2017-02-15 |
CN106412000B CN106412000B (en) | 2019-05-31 |
Family
ID=58004286
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN201610598887.8A Active CN106412000B (en) | 2016-07-27 | 2016-07-27 | A kind of processing method of inquiry of the domain name |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN106412000B (en) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107231454A (en) * | 2017-07-06 | 2017-10-03 | 深圳互联先锋科技有限公司 | The method and device of domain name high-volume asynchronous query |
CN109495598A (en) * | 2018-10-23 | 2019-03-19 | 新华三技术有限公司合肥分公司 | Domain name system parameter selection method and relevant apparatus |
CN110784553A (en) * | 2019-11-05 | 2020-02-11 | 南京亚信智网科技有限公司 | Message encapsulation method, device and domain name resolution system |
CN111866197A (en) * | 2019-04-29 | 2020-10-30 | 贵州白山云科技股份有限公司 | Domain name resolution method and system |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101207507A (en) * | 2006-12-20 | 2008-06-25 | 中国电信股份有限公司 | System for managing mobile terminal capability information |
CN102801814A (en) * | 2012-08-29 | 2012-11-28 | 易莲无限(北京)科技发展有限责任公司 | Internet access method, device and system |
CN102984297A (en) * | 2012-12-10 | 2013-03-20 | 中国科学院计算机网络信息中心 | Method and system for realizing IDN registration based on domain name group |
CN102984298A (en) * | 2012-12-10 | 2013-03-20 | 中国科学院计算机网络信息中心 | Method and system for realizing domain name registration based on domain name group |
-
2016
- 2016-07-27 CN CN201610598887.8A patent/CN106412000B/en active Active
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101207507A (en) * | 2006-12-20 | 2008-06-25 | 中国电信股份有限公司 | System for managing mobile terminal capability information |
CN102801814A (en) * | 2012-08-29 | 2012-11-28 | 易莲无限(北京)科技发展有限责任公司 | Internet access method, device and system |
CN102984297A (en) * | 2012-12-10 | 2013-03-20 | 中国科学院计算机网络信息中心 | Method and system for realizing IDN registration based on domain name group |
CN102984298A (en) * | 2012-12-10 | 2013-03-20 | 中国科学院计算机网络信息中心 | Method and system for realizing domain name registration based on domain name group |
Cited By (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN107231454A (en) * | 2017-07-06 | 2017-10-03 | 深圳互联先锋科技有限公司 | The method and device of domain name high-volume asynchronous query |
CN107231454B (en) * | 2017-07-06 | 2020-07-07 | 深圳互联先锋科技有限公司 | Method and device for large-batch asynchronous domain name query |
CN109495598A (en) * | 2018-10-23 | 2019-03-19 | 新华三技术有限公司合肥分公司 | Domain name system parameter selection method and relevant apparatus |
CN111866197A (en) * | 2019-04-29 | 2020-10-30 | 贵州白山云科技股份有限公司 | Domain name resolution method and system |
CN111866203A (en) * | 2019-04-29 | 2020-10-30 | 贵州白山云科技股份有限公司 | Domain name resolution method and device, readable storage medium and equipment |
CN111866197B (en) * | 2019-04-29 | 2021-09-21 | 贵州白山云科技股份有限公司 | Domain name resolution method and system |
CN111866203B (en) * | 2019-04-29 | 2022-04-19 | 贵州白山云科技股份有限公司 | Domain name resolution method and device, readable storage medium and equipment |
CN110784553A (en) * | 2019-11-05 | 2020-02-11 | 南京亚信智网科技有限公司 | Message encapsulation method, device and domain name resolution system |
CN110784553B (en) * | 2019-11-05 | 2021-12-21 | 南京亚信智网科技有限公司 | Message encapsulation method, device and domain name resolution system |
Also Published As
Publication number | Publication date |
---|---|
CN106412000B (en) | 2019-05-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN110119292B (en) | System operation parameter query method, matching method, device and node equipment | |
CN107294908B (en) | Account information processing method, device and system in instant messaging application | |
CN1901547B (en) | Method and apparatus for making web service policy agreement | |
CN106412000A (en) | Domain name query processing method | |
CN105530175A (en) | Message processing method, device and system | |
US20110145270A1 (en) | Service personas for address books | |
CN113366815B (en) | Network resource request method, device, electronic equipment and storage medium | |
CN106453414B (en) | Third party login authentication method, proxy server, client and system | |
CN102377617A (en) | Systems, methods, and apparatus to monitor and authenticate mobile internet activity | |
CN104901955A (en) | Early warning method, early warning device and processing server | |
CN103269479A (en) | Call ticket processing method, device and system | |
WO2020228038A1 (en) | Domain name processing method, apparatus, electronic device, and storage medium | |
US20170289243A1 (en) | Domain name resolution method and electronic device | |
CN110769080B (en) | Domain name resolution method, related product and computer readable storage medium | |
CN101924799A (en) | Method and system for querying information of domain name | |
CN103581351A (en) | Method and device for having access to network | |
WO2015158150A1 (en) | Method and apparatus enabling user to establish communication with third party | |
CN109561167A (en) | A kind of domain name analytic method and device | |
CN113794999B (en) | Short message distribution method, device and storage medium | |
CN108282455A (en) | Web-page requests method, apparatus and domain-name information analysis result processing method, device | |
CN113806104A (en) | Interface access request processing method, API gateway, server and system | |
CN104270357A (en) | Service information sending method and device | |
CN101626628B (en) | Digital number and web address mapping and pushing system | |
CN108737350B (en) | Information processing method and client | |
CN103179541B (en) | The acquisition processing method of sip terminal logarithmic chart unit and system |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
GR01 | Patent grant | ||
GR01 | Patent grant |