Why is there 192.168.0.1 adddress ?

till the timeout or deleting the static DNS, the entry exist
No, It is exist until reboot.
at RouterOS 6.15 and 6.16…CCR1036, x86, mipsbe…

Nice, you report also what version of routeros you use.
Well done, you found the solution.
how to reproduce it?
If not previous static DNS entry exist, add one static dns, after that change the ip on that static rule and save: done, you have get “duplicate entry”, not realy duplicate, but is work like previous static rule already exist.
But this probem do not exist for me on 6.15 mipsbe/ppc/x86 , but I’m absolutely sure I have obtained that error on previous version.
I really hope you spend the time for fix webfig bug: missing ftp and winbox right when creating script prevent the creation of script or scheduling containing “export” or other command working on files folder.
Replace static IP address a few times.
hi Guys,
I have same problem on 6.12 and 6.17
It’s problem with update of DNS static records over WinBox (can’t reproduce it over terminal)
to reproduce:
- create new record
- edit ip in WinBox
- BOOOM - DNS server resolving two addresses
- edit ip in WinBox
- BOOOM - DNS server resolving three addresses
- remove DNS static rule
- BOOOM - only last one IP removed from result
Hope it help you and you are able to fix it quick.
Thanks,
Bartek
need more details - on test router everythign stops at BOOOM. and static entries are updated correctly in cache every single time.
tried to create inital entry via winbox or via cli, no difference.
same…

need more details - on test router everythign stops at BOOOM. and static entries are updated correctly in cache every single time.
tried to create inital entry via winbox or via cli, no difference.
check shed video - looks same on my site
hi,
there is any news in that case? can we expect fix soon?
EDIT:
oh i just found in last change log “) dns-update - fix zone update;” it means that it’s fixed already?
Thanks,
Bartek
dns-update has nothing in common with dns cache. (except obvious 3 letters) so no it is not fixed.
out of curiosity, what happens if you do something like this:
for i from=1 to=255 do={/ip dns static set [find] address="127.0.0.
$i" }}
or (with delay)
for i from=1 to=255 do={/ip dns static set [find] address="127.0.0.
$i";:delay 5 }}
can you send support output file from latest release of routeros with this problem visible?
what is RP filtering, settings, btw ?
are you referring to DNS cache?