[7.460][BUG][FIXED] DNS Forwarders delete and add shows wrong setting in traceroute

[utm_kid]

Hi Friends !

when we configure system at that time we add DNS Forwarders setting ,after that if u delete/change(?) that setting remain with DNS Forwarders
in Support>.tools>>traceroute

new added entry doesnt come under this option ,do u think it need to be chage

After delete DNS Forwarders object it show new name

Thanks

[BAlfson]

when we configure system at that time we add DNS Forwarders setting ,after that if u delete/change(?) that setting remain with DNS Forwarders
in Support>.tools>>traceroute

How do you see that the settings don't change? I'm not sure I understand how this would change the behavior of traceroute.

new added entry doesnt come under this option ,do u think it need to be chage

Is this a "vew added entry" in 'forwarders'? What "option" are you asking about? What do you think needs to be changed?

After delete DNS Forwarders object it show new name

What object are you deleting and where? Can you show a picture or tell us how to reproduce this?

Cheers - Bob

[Billybob]

Confused about what utm-kid is saying...I started writing the following text

I thought it was a bug the other day. I was testing an IP that was being blocked by opendns.com (which I use as forwarder). So I deleted the forwarders and when I queried the IP again, I got the same opendns.com error message.

Long story short, the problem is coming from caching. I looked at /var/chroot-bind/etc/named.conf and indeed the forwarders are removed when you remove them via webadmin. But the configuration is reloaded and bind is not restarted which means that cache is not flushed. I guess it can be classified as a bug.

You can observe the behavior by removing forwarders while looking at the dns logs and then clear cache while looking at the logs. Clear cache restarts bind completely.

Decided to start a seperate thread about the issue here but credit should go to utm-kid if that is what he intended to say.

[BAlfson]

Yes, I think that's exactly what he's describing in the first part of his post. I think you guys should both get credit though because you nailed it down independently. It seems like a bug if "clear cache" should be run whenever the DNS config changes and that's not done.

Good job utm_kid and Billybob!

[Astaro Beta Bot]

Astaro Beta Report
--------------------------------
Version: 7.460
Type: BUG
State: FIXED
Reporter: utm_kid
Contributor: 
MantisID: 10781
--------------------------------

[fhudl]

Fixed in Version 7.500