Skip to content
GitLab
Projects
Groups
Snippets
Help
Loading...
Help
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
Kea
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
415
Issues
415
List
Boards
Labels
Service Desk
Milestones
Merge Requests
67
Merge Requests
67
Operations
Operations
Incidents
Packages & Registries
Packages & Registries
Container Registry
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
ISC Open Source Projects
Kea
Commits
cd77eba4
Unverified
Commit
cd77eba4
authored
May 28, 2012
by
Michal 'vorner' Vaner
Browse files
Options
Browse Files
Download
Plain Diff
Merge #1948
This is the guide update to mention the listen_on workaround for multi-homed hosts.
parents
21d3d1aa
b75e92de
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
18 additions
and
0 deletions
+18
-0
doc/guide/bind10-guide.xml
doc/guide/bind10-guide.xml
+18
-0
No files found.
doc/guide/bind10-guide.xml
View file @
cd77eba4
...
...
@@ -1352,6 +1352,24 @@ This may be a temporary setting until then.
and
<varname>
port
</varname>
number.
By default,
<command>
b10-auth
</command>
listens on port 53
on the IPv6 (::) and IPv4 (0.0.0.0) wildcard addresses.
<note>
<simpara>
The default configuration is currently not appropriate for a multi-homed host.
In case you have multiple public IP addresses, it is possible the
query UDP packet comes through one interface and the answer goes out
through another. The answer will probably be dropped by the client, as it
has a different source address than the one it sent the query to. The
client would fallback on TCP after several attempts, which works
well in this situation, but is clearly not ideal.
</simpara>
<simpara>
There are plans to solve the problem such that the server handles
it by itself. But until it is actually implemented, it is recommended to
alter the configuration
—
remove the wildcard addresses and list all
addresses explicitly. Then the server will answer on the same
interface the request came on, preserving the correct address.
</simpara>
</note>
</simpara>
</listitem>
</varlistentry>
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
.
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment