installing_irc_at_home
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | |||
| installing_irc_at_home [2020/07/11 16:59] – waxphilosophic | installing_irc_at_home [2020/07/13 01:01] (current) – waxphilosophic | ||
|---|---|---|---|
| Line 77: | Line 77: | ||
| === CONNECTIONS CONFIGURATION === | === CONNECTIONS CONFIGURATION === | ||
| - | After commenting out the last two lines of PORT CONFIGURATION, | + | After commenting out the last two lines of PORT CONFIGURATION, |
| - | The reason for this is entirely because of DNS. Unless you are running a robust DNS infrastructure on your LAN, chances are good that your ISP's router (the typical home LAN DNS server) will not do reverse look-ups. Setting resolvehostnames=" | + | The reason for changing resolvehostnames |
| If you have a more robust DNS server on your network, you can certainly leave this as-is. If you see errors like "Could not resolve your hostname: Malformed answer" | If you have a more robust DNS server on your network, you can certainly leave this as-is. If you see errors like "Could not resolve your hostname: Malformed answer" | ||
| Line 90: | Line 90: | ||
| Do not give into the temptation to comment the lines out. This is not the same as setting it to no. | Do not give into the temptation to comment the lines out. This is not the same as setting it to no. | ||
| + | |||
| + | As for the IP address range that needs changing, this is in the example < | ||
| + | |||
| + | < | ||
| + | allow=" | ||
| + | </ | ||
| === Enabling Server Operators === | === Enabling Server Operators === | ||
| Line 386: | Line 392: | ||
| > #<bind address="" | > #<bind address="" | ||
| > #<bind address=" | > #<bind address=" | ||
| + | 278c278 | ||
| + | < allow=" | ||
| + | --- | ||
| + | > allow=" | ||
| 313c313 | 313c313 | ||
| < resolvehostnames=" | < resolvehostnames=" | ||
installing_irc_at_home.1594486743.txt.gz · Last modified: 2020/07/11 16:59 by waxphilosophic