Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 2 added, 0 removed)
  • image-20240827145055-4.png
  • image-20240827150121-5.png

Details

Page properties

Content

...	...	@@ -848,7 +848,7 @@
848	848
849	849	[[image:image-20240820113015-60.png]]
850	850
851		-== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.3 What is the Downlink Command by the NB device?(%%) ==
	851	+== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.3 What is the Downlink Command by the -CB device?(%%) ==
852	852
853	853	(% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
854	854	=== UDP: ===
...	...	@@ -902,3 +902,31 @@
902	902
903	903
904	904	​
	905	+
	906	+== 6.4 What if the signal is good but the domain name resolution fails? ==
	907	+
	908	+
	909	+If the domain name resolution fails, first check whether the domain name is correct, users can use their own website domain name resolution tool to verify the domain name.
	910	+
	911	+If the domain name is correct, but the domain name cannot be resolved, the user can turn off the domain name resolution function(AT+GDNS=1) and use the domain name communication directly.
	912	+
	913	+* Set the DNS
	914	+
	915	+(% style="color:blue" %)**AT Command: AT+GDNS**
	916	+
	917	+**AT+GDNS=0**  ~/~/Default. Automatically resolves the domain name and uses the resolved IP to communicate.
	918	+
	919	+**AT+GDNS=1  **~/~/Disabling Domain name resolution. Use the domain name directly to communicate.
	920	+
	921	+(% style="color:red" %)**Note: For -CB products, with the exception of AT+PRO=2,5, all protocols and payload formats support direct domain communication.**
	922	+
	923	+Example:
	924	+
	925	+
	926	+
	927	+
	928	+
	929	+
	930	+
	931	+
	932	+

image-20240827145055-4.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+74.2 KB

Content

image-20240827150121-5.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+86.0 KB

Content