Skip to content

fixed dynamic_resolver_port.t: cannot listen on dns server port#1677

Merged
chobits merged 1 commit into
alibaba:masterfrom
chobits:master
Nov 5, 2022
Merged

fixed dynamic_resolver_port.t: cannot listen on dns server port#1677
chobits merged 1 commit into
alibaba:masterfrom
chobits:master

Conversation

@chobits

@chobits chobits commented Nov 5, 2022

Copy link
Copy Markdown
Member

Use "resolver 127.0.0.01:8xxx" instead of "resolver 127.0.0.1:8xxxx". Otherwise, write_file_expand()/port() in Nginx.pm will listen on that port firstly.

Use "resolver 127.0.0.01:8xxx" instead of "resolver 127.0.0.1:8xxxx".
Otherwise, port() in Nginx.pm will listen on that port firstly.
@chobits

chobits commented Nov 5, 2022

Copy link
Copy Markdown
Member Author

cc @wangfakang


$t->run_daemon(\&dns_daemon, 8900, $t);
$t->waitforfile($t->testdir . '/dns_server.pid')
or die "\n+ failed to create dns server!\n\n";

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if dns server failed to be created, stop the case

@chobits
chobits merged commit 24b156d into alibaba:master Nov 5, 2022
@chobits chobits added this to the 2.3.5 milestone Nov 5, 2022
@chobits chobits modified the milestones: 2.3.5, 2.4.0 Feb 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant