/system ntp client
set enabled=yes primary-ntp=193.140.100.40 secondary-ntp=217.198.219.102

Finally they have updated the glue records: Now it works dig ns mynetname.net @c.gtld-servers.net ; <<>> DiG 9.10.3-P4-Debian <<>> ns mynetname.net @c.gtld-servers.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53924 ;; flags: qr rd; QUERY: 1, ANSWER: ...

It is working for me (Brazil). Maybe some geographic cache? :~> dig ns1.kissthenet.net ; <<>> DiG 9.11.2 <<>> ns1.kissthenet.net ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11756 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 13, ADDITIONAL: 11 ;;...

I think that you have to use queue (simple or tree, depends from your requirements) to do that

GTLD nameservers are still returning the old records. May want to check that. https://r-1.ch/r1dns/dnscheck.cgi?domain=mynetname.net I confirm that now glue records of domain mynetname.net are wrong and pointing to ns1.kissthenet.net (81.198.87.240) ns2.kissthenet.net (91.188.51.139) instead of ns1...

Check the protected-routerboot setting

https://wiki.mikrotik.com/wiki/Manual:R ... D_settings

1st rule) Prevent 10.10.1.15 to perform connection to 192.168.1.14 ip firewall filter add action=drop src-address=10.10.1.15 dst-address=192.168.1.14 chain=forward 2nd rule) Prevent 192.168.1.14 to perform connection to 10.10.1.15 ip firewall filter add action=drop src-address=192.168.1.14 dst-addre...

You cannot exclude IP/MAC, you can only exclude topics.

So
/system logging
set 0 topics=info,!dhcp
set 0 topics=warning,!dhcp

But doing this will exclude any DHCP info/warning log from your log system.

config is pretty default ... plain accespoint, all interfaces in 1 bridge, no firewall rules, dhcp from core-router /interface wireless set [ find default-name=wlan1 ] band=2ghz-g/n channel-width=20/40mhz-eC \ disabled=no distance=indoors frequency=2462 mode=ap-bridge \ security-profile=home ssid=h...

Don't hesitate and buy the hAP AC (RB962UiGS-5HacT2HnT) , the best SOHO Router Gigabit with 2.4GHz and 5GHz WiFi

According with the documentation you can easy set the APN, PIN and scan the network : https://wiki.mikrotik.com/wiki/Manual:Interface/LTE
My suggestion is to keep the LTE part and LTE IP on the Mikrotik, and NAT outside from the lte interface.

The issue is the masquerade in different order. You're masquerading site1 behing ether1-wan and site2 behing ppp-out-1 site1 /ip firewall nat add action=masquerade chain=srcnat out-interface=ether1-wan add action=masquerade chain=srcnat out-interface=ppp-out1 site2 /ip firewall nat add action=masque...

add the following lines and then open a new incognito tab and try to reach http://www.akamai.com/ (it should fail and you will see packets increasing for that rule on /ip firewall filter print stats ) /ip firewall layer7-protocol add name=l7_akamai regexp="(^|.\\.)akamai\\.." /ip firewall ...

/ip firewall address-list add address=54.xx.xx.107 list=Allowed_IP_TCP add address=54.xx.xx.64 list=Allowed_IP_TCP add address=54.xx.xx.241 list=Allowed_IP_TCP add address=54.xx.xx.51 list=Allowed_IP_TCP add address=54.xx.xx.45 list=Allowed_IP_TCP add address=54.xx.xx.107 list=Allowed_IP_UDP add add...

This regexp
regexp="(^|.\\.)akamaitechnologies\\.."
filter every akamaitechnologies.*** and ***.akamaitechnologies.*** domain