WIND & DNS - Moved - Feedback here please

I have updated wind and dns.

WIND

Wind is on a new server and also a new version. I have forked wind and it’s now hosted here: https://github.com/southern-wind/wind
PRs welcome if you want to improve wind.

FYI: Fixed a long time problem with password reset emails. Please still check your spam as it might just actually be there.

DNS

We used to run a bind install with a custom MySQL driver that read the dns records from MySQL with other masters syncing from this server. We are replacing this with 2 PowerDNS instances that read MySQL data (one for wnet view and one for inet view). These sync to a local bind server. This bind server then talks to the rest of the masters as per usual.

Why this DNS setup?

We went with it mainly because PowerDNS has built in support for a MySQL backend which is sort of what WIND is. Bind also has this sort of thing but we need a MySQL driver which is complex and custom. Also the newest version of Bind changes the API for drivers and I can’t rewrite it. So to reduce future maintenence I switched.

Problem with PowerDNS is that it doesn’t support multiple views. We have 2 views. One from internet which serves internet ips for some of our sites (I call it inet) and one from wug which serves wug ips (I call it wnet).

So I run two PowerDNS instances on centrifuge. They both access MySQL views of WIND data that look slightly different. One runs on port 5353 (wnet view) and one on 5354 (inet view). I then also run bind which does support views on port 53 that syncs via axfr to PowerDNS and other dns servers.

So PowerDNS is always up to date as it directly access WIND data.

We stuck with bind elsewhere because of view support and ease of setup on other dns servers. PowerDNS also doesn’t seem to be very fast (probably due to the complex MySQL views I’ve set up to access WIND data directly).

Bind configs and scripts to roll them out here if you are interested:

I’m delaying this. Not as ready as I thought. Old WIND will be available again shortly.

OK this time I’ve done my homework. Going to switch it across now. Should be done in about 30mins.

30 minutes almost exactly. New wind now live.
If you get a index of / folder you need to refresh your dns cache.

Updated first post with info.

thanks successful login for me

new wind looks great just 1 thing clicking on your node or nodes you co admin loads long

not a problem just saying

Hi,
If I try and enter my Nick (NyvenZA) in the login box, Wind says that the node doesn’t exist. If i enter my Node name (IO), it shows my node.
So I can’t login at the moment.

Also Since last night (it was still working around 20:00) I have some funny DNS issues. If I use my local RB that I have been using as a DNS for years, it can’t lookup any ctwug.za.net domains, but it can lookup other domains. If I use nslookupto point directly to 172.18.1.1, i can still lookup domains. It is only the Mikrotik DNS that doesn’t lookup ctwug domains. The DNS cache on my RB shows the domain and then type “Unknown” for any domain that fails.

Ok so this was a PEBKAC problem. Logged in now.

Still having the DNS issues.

Thanks for the effort spin.
Its not too happy on mobile phones though. I can login in fine, once you go to your node all the details are cut off so can’t see any information and there’s no way to scroll to the right to view.

Would it be possible to disable mobile view? Or have an option to select mobile/desktop view.

Can we not change the code on line 22 - https://github.com/southern-wind/wind/blob/master/templates/basic/includes/html.tpl

to

<meta id=“windViewport” name=“viewport” content=“width = 740”>
<script>
if (screen.width > 750) {
var mvp = document.getElementById(‘windViewport’);
mvp.setAttribute(‘content’,‘width=1200’);
}
</script>

Hi Spin,
I have now done some testing re the DNS:

  1. Changed my PC DNS to 172.18.1.1, to use it directly.
  2. nslookup works to any service (e.g. music.ctwug.za.net)
  3. Tried EDGE browser to music.ctwug.za.net and it works.
  4. Tried Chrome to music.ctwug.za.net and it fails to load the DNS entry. But if I try music.io.ctwug.za.net it works.
  5. Tried to reboot. No difference.
  6. Clear the Chrome DNS cache, ipconfig /flashdns and restarted dnscache service, all still the same.
  7. Tried Firefox and Opera and one site started working in opera, but not other browsers.
  8. ran net stop dnscache another 2 times and then the sites started working now.

For now the DNS seems to be working.

Can you tell me the rb ip in question and create a ctwug/ctwug login if it doesn’t have one?

Can you post tracert 172.18.1.1?

It doesn’t sound like a general dns issue if some browsers work and others don’t. If nslookup works then it has to be cacheing related.
In chrome you can view and clear the host cache by going to chrome://net-internals/#dns
You can clear the windows one by running ipconfig /fushdns. (from a command line with admin priveleges i think)

See this: mobile friendly · Issue #10 · southern-wind/wind · GitHub
I will have a look at the change you suggest.

tracert 172.18.1.1

Tracing route to dns.ctwug.za.net [172.18.1.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.150.1
2 <1 ms <1 ms <1 ms 172.18.10.17
3 <1 ms <1 ms <1 ms rb5.io.ctwug.za.net [172.18.10.4]
4 10 ms 2 ms 4 ms link-io.jellybean.ctwug.za.net [172.18.10.78]
5 4 ms 4 ms 5 ms 172.18.10.132
6 9 ms 8 ms 15 ms 172.18.10.150
7 12 ms 9 ms 9 ms rb3-fubar.fubar.ctwug.za.net [172.18.108.25]
8 18 ms 13 ms 9 ms 172.18.46.238
9 13 ms 12 ms 18 ms ospf-rb600.ogon.ctwug.za.net [172.18.46.253]
10 25 ms 46 ms 26 ms 172.18.46.244
11 52 ms 36 ms 31 ms dns.ctwug.za.net [172.18.1.1]

I have cleared both as per point 6.
DNS not working again.

Did a tracert again and most of the IPs don’t resolve eaither. But i assume this is because it it possibly timing out?
tracert 172.18.1.1

Tracing route to ntp.ctwug.za.net [172.18.1.1]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.150.1
2 <1 ms <1 ms <1 ms rb3-client.io.ctwug.za.net [172.18.10.17]
3 1 ms <1 ms <1 ms rb5.io.ctwug.za.net [172.18.10.4]
4 21 ms 5 ms 4 ms 172.18.10.78
5 3 ms 7 ms 3 ms 172.18.10.132
6 11 ms 7 ms 7 ms ospf-jellybean.fubar.ctwug.za.net [172.18.10.150]
7 9 ms 19 ms 19 ms 172.18.108.25
8 11 ms 12 ms 14 ms 172.18.46.238
9 11 ms 12 ms 22 ms 172.18.46.253
10 41 ms 23 ms 80 ms 172.18.46.244
11 33 ms 35 ms 36 ms ntp.ctwug.za.net [172.18.1.1]

Also having same issues…

Tracert to 172.18.1.1 doesnt go via the DNS server hosted by me

Hi Spin,
Just in case,I can login to the new page at http://wind.ctwug.za.net/. Everything seems OK, but the login and navigation was slow the first time, seems to be faster now.
Cheers

Rules breach

Ok I haven’t changed anything on all the wugpi dna servers. This change can’t affect the routing to dns. I’m driving this pm and should be able to look early evening at this in any case.