[Coder-Com] ircd resolver issue
Hello! I run a ircd and named on the same server. My resolver (/etc/resolver.conf) is setup so that it points only to localhost (DNS is running on the same server). Now for a reason not related to ircd I changed the IP address of one of my DNS. Everything else works except ircd, it still queries the old IP address (confirmed by stracing ircd). I do not want to kill ircd, is there a way to refresh the internal resolver in ircd? If not why in earth does it cache the nameservers and why doesn't it timeout the entries properly (DNS refresh periods). I'm running 2.10.10-pl18 on Linux 2.4. Thank you in advance for your assistance.
Re: [Coder-Com] ircd resolver issue
At 09:32 28/08/2002, you wrote: >Hello! > >I run a ircd and named on the same server. My resolver >(/etc/resolver.conf) is setup so that it points only to localhost (DNS >is running on the same server). > >Now for a reason not related to ircd I changed the IP address of one >of my DNS. Everything else works except ircd, it still queries the old >IP address (confirmed by stracing ircd). I do not want to kill ircd, >is there a way to refresh the internal resolver in ircd? If not why in >earth does it cache the nameservers and why doesn't it timeout the >entries properly (DNS refresh periods). I'm running 2.10.10-pl18 on >Linux 2.4. Hello, sorry but you NEED to /restart ircd for it to re-read your /etc/resolv.conf file. regards, >Thank you in advance for your assistance. -- nighty
[Coder-Com] Re: [Bugs] ircd resolver issue
> no I didn't change the IP in /etc/resolv.conf, I changed the IP > address of my DNS server. /etc/resolv.conf has only "server > localhost". This is problematic because the old IP address is no > longer reachable and that is the one that ircd keeps on querying. > > What I am not 100% sure about is that did /etc/resolv.conf have the IP > address of the now unreachable DNS server instead of localhost when I > started ircd 81 days ago. It is possible although unlikely. > > I have /rehash'ed several times, doesn't help. I just tried "/rehash > q" that doesn't seem to help either. I'm afraid /restart will be your best option, then. The resolver is one of the things we're hoping to address with the u2.10.12 release. Sorry for the inconvenience :( -- Kevin L. Mitchell <[EMAIL PROTECTED]>
[Coder-Com] Re: [Bugs] ircd resolver issue
On Wed, Aug 28, 2002 at 03:10:59PM +0300, EQU wrote: > What I am not 100% sure about is that did /etc/resolv.conf have the IP > address of the now unreachable DNS server instead of localhost when I > started ircd 81 days ago. It is possible although unlikely. [Not really a bug, possibly a feature request. bugs@ taken off, since those people are basically all on coder-com anyway. Kev also taken off CC, he'll see this anyway.] As I'm sure you've noticed, ircu has no nameserver configuration options. That's normally handled on a system-wide basis via resolv.conf. If ircu is querying the wrong server, it's doing so because that's what resolv.conf told libresolv to do when you started the process. The resolver isn't going to pick up those changes unless it gets re-initialized, and there's no good way to do that from within ircu (currently). This is maybe a feature request (please note that .11 is feature-frozen, iirc, so it'll be a while), but resolv.conf is not something that needs to be changed very often, if at all, and isn't a high priority for most people. Generally speaking, I'd recommend running a current rev of BIND or some other caching nameserver locally, and possibly configuring a trusted (emphasis on the trusted; these should also be running current code revs) backup nameserver or two additionally. > I have /rehash'ed several times, doesn't help. I just tried "/rehash > q" that doesn't seem to help either. You're gonna have to /restart. Sorry :/ --msa
[Coder-Com] Re: [Bugs] ircd resolver issue
> I run a ircd and named on the same server. My resolver > (/etc/resolver.conf) is setup so that it points only to localhost (DNS > is running on the same server). > > Now for a reason not related to ircd I changed the IP address of one > of my DNS. Everything else works except ircd, it still queries the old > IP address (confirmed by stracing ircd). I do not want to kill ircd, > is there a way to refresh the internal resolver in ircd? If not why in > earth does it cache the nameservers and why doesn't it timeout the > entries properly (DNS refresh periods). I'm running 2.10.10-pl18 on > Linux 2.4. If you mean you changed the IP in /etc/resolv.conf, a /rehash should refresh that. As for ircu, it has a built-in cache that we've tried to remove before with little success--a "/rehash" or "/rehash q" might manage to do the right thing... -- Kevin L. Mitchell <[EMAIL PROTECTED]>
[Coder-Com] Re: [Bugs] ircd resolver issue
Hello, no I didn't change the IP in /etc/resolv.conf, I changed the IP address of my DNS server. /etc/resolv.conf has only "server localhost". This is problematic because the old IP address is no longer reachable and that is the one that ircd keeps on querying. What I am not 100% sure about is that did /etc/resolv.conf have the IP address of the now unreachable DNS server instead of localhost when I started ircd 81 days ago. It is possible although unlikely. I have /rehash'ed several times, doesn't help. I just tried "/rehash q" that doesn't seem to help either. Thanks. On Wed, 28 Aug 2002, Kev wrote: > > I run a ircd and named on the same server. My resolver > > (/etc/resolver.conf) is setup so that it points only to localhost (DNS > > is running on the same server). > > > > Now for a reason not related to ircd I changed the IP address of one > > of my DNS. Everything else works except ircd, it still queries the old > > IP address (confirmed by stracing ircd). I do not want to kill ircd, > > is there a way to refresh the internal resolver in ircd? If not why in > > earth does it cache the nameservers and why doesn't it timeout the > > entries properly (DNS refresh periods). I'm running 2.10.10-pl18 on > > Linux 2.4. > > If you mean you changed the IP in /etc/resolv.conf, a /rehash should > refresh that. As for ircu, it has a built-in cache that we've tried > to remove before with little success--a "/rehash" or "/rehash q" > might manage to do the right thing... >
[Coder-Com] Re: [Patches] m_gline.c in 2.10.11
> If no target is specified in /gline command for opers a local gline is > still added evne if FEAT_LGLINE is false. patch by darren coleman. The patch you sent wouldn't have worked quite the way you intended--it would require you to have the PRIV_LOCAL_GLINE privilege to set global G-lines. While it could be argued that you should have both to set global G-lines, it does break the separation of privilege I was intending. Of course, fixing this was easy--I just replaced the "PRIV_LOCAL_GLINE" with a ?: operator testing on whether the GLINE_LOCAL flag got set. I also removed the now redundant tests from where the target is checked. While I was in there, I also noted another burr having to do with wide glines and the WIDE_GLINE privilege, which I corrected. Thanks for pointing this problem out! -- Kevin L. Mitchell <[EMAIL PROTECTED]>
Re: [Coder-Com] Re: [Patches] m_gline.c in 2.10.11
On Wed, Aug 28, 2002 at 08:30:41AM -0400, Kev wrote: > > If no target is specified in /gline command for opers a local gline is > > still added evne if FEAT_LGLINE is false. patch by darren coleman. > Was actually Darren Smith, but no harm no foul :) > The patch you sent wouldn't have worked quite the way you intended--it > would require you to have the PRIV_LOCAL_GLINE privilege to set global > G-lines. While it could be argued that you should have both to set > global G-lines, it does break the separation of privilege I was intending. > Of course, fixing this was easy--I just replaced the "PRIV_LOCAL_GLINE" > with a ?: operator testing on whether the GLINE_LOCAL flag got set. I > also removed the now redundant tests from where the target is checked. > While I was in there, I also noted another burr having to do with > wide glines and the WIDE_GLINE privilege, which I corrected. > > Thanks for pointing this problem out! > -- > Kevin L. Mitchell <[EMAIL PROTECTED]> > Cheers for fixing this kev, saved us a patch :) -- Joe "Pilsner" Cise(__) e::[EMAIL PROTECTED] Co-Founder, b0rk UKoo\\\~ w::www.b0rk.co.uk Senior IRC Admin, QuakeNet w::www.quakenet.org
Re: [Coder-Com] Re: [Bugs] ircd resolver issue
- Original Message - From: "Majdi S. Abbas" <[EMAIL PROTECTED]> To: "EQU" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Wednesday, August 28, 2002 3:20 PM Subject: [Coder-Com] Re: [Bugs] ircd resolver issue ... > > Generally speaking, I'd recommend running a current rev > of BIND or some other caching nameserver locally, and possibly > configuring a trusted (emphasis on the trusted; these should also > be running current code revs) backup nameserver or two additionally. > perhaps use forwarders in bind ( named.conf ) and put some of your ISP's nameservers in there instead of /etc/resolve.conf if you are already using bind for example. works for me... if ircu won't like resolve.conf changes without restart, then fix it at the bind level :) > > I have /rehash'ed several times, doesn't help. I just tried "/rehash > > q" that doesn't seem to help either. > > You're gonna have to /restart. Sorry :/ > > --msa >
[Coder-Com] Can't connect
I have set up ircd on my server but I am having an issue. Most likely it is a DFU error, but any help would be appreciated. I went through the install process and all seemed to go well. No error notices, etc. I edited the example config file to match my server then started up ircd. When I run ps at the console I can see ircd running. Problem is that I cannot connect to the server at all. When I run one of my net utils to see what ports are active the port I assigned to ircd does not return anything. (I have tried a few ports in the config file with no luck.) Attempting to connect via mIRC gives me a time out. Any ideas of what may be the problem other than or in addition to the fact that I am clueless? Thanks, D
