NorthWest Kayak Anglers
Not Necessarily Kayak Fishing => Site Discussion => Topic started by: polepole on October 17, 2017, 09:02:36 AM
-
So after a lengthy debug, we have decided to move servers once again, this time to fix AOTY/DOTY. I will be scheduling it for some time this weekend. So if you see the server down, and it will be for ~24 hours, maybe longer, you know why.
-Allen
-
The move is schedule to start this Saturday, Oct 21. Some time Friday night or first thing Saturday, I'll put the forum into maintenance mode. You'll see a message and you won't be able to do much. Come back Monday, when hopefully the migration is complete.
-Allen
-
Much appreciated Allen!
-
Good luck and thanks.
-
Choot yeah! Thanks!
Sent from my iPhone using Tapatalk
-
Thanks for taking care of this, Allen! :icon_thumright: :occasion14:
-
Reminder, site going down for the weekend. I've decided that at 9PM tonight, I'll shut it off, and we'll begin the server transfer.
-Allen
-
BUMP.
Server going down at 9PM tonight. Back on Monday.
-Allen
-
Beep beep beep ... 1.5 hours until server down.
-Allen
-
And ... we’re back up!
-Allen
-
Looks good!
-
And ... we’re back up!
-Allen
Thanks for the awesome migration work here, Allen. I've been through a few of those and I can't say that I've been terribly consistent in having everything back up and running before the end of the planned maintenance window. Well done! :occasion14:
-
AOTY still doesn't work.
-
AOTY still doesn't work.
It will. Just need to fix up a configuration issue to make it that you don't have to go to http://aoty.northwestkayakanglers.com/index and can just go tohttp://aoty.northwestkayakanglers.com .
-Allen
-
AOTY still doesn't work.
It will. Just need to fix up a configuration issue to make it that you don't have to go to http://aoty.northwestkayakanglers.com/index and can just go tohttp://aoty.northwestkayakanglers.com .
-Allen
Ah very nice. Happy to see this back up and running.
-
BTW, not everyone may be able to access the site yet. DNS updates need to propagate through the web. While for some, this occurs relatively soon, for others it may take up to 48 hours to propagate.
-Allen
-
I updated the AOTY link in the main NWKA site menu to point to http://aoty.northwestkayakanglers.com/index
-
BTW, not everyone may be able to access the site yet. DNS updates need to propagate through the web. While for some, this occurs relatively soon, for others it may take up to 48 hours to propagate.
-Allen
The time-to-live on the DNS record is only 4 hours, so it would take some seriously misconfigured DNS servers to still be hanging onto the old cached IP address this long. ;D
-
BTW, not everyone may be able to access the site yet. DNS updates need to propagate through the web. While for some, this occurs relatively soon, for others it may take up to 48 hours to propagate.
-Allen
The time-to-live on the DNS record is only 4 hours, so it would take some seriously misconfigured DNS servers to still be hanging onto the old cached IP address this long. ;D
Actually, it is set to 1 hour. But I've seen time and time again where this didn't happen.
But, I also have doubts about it taking this long, and I have sent the data center a note stating as much. They double checked the settings and assured me that everything is ok. That being said, every other site on the server is back up (at least resolves to the correct server) except NCKA, so I'm back to wondering ...
-Allen
-
Well, the NCKA DNS is propagating, albeit slowly. Not sure why, as all the other sites seem to have propagated by now.
https://www.whatsmydns.net/#A/norcalkayakanglers.com
-Allen
-
Regardless of what you requested, TTL is currently 4 hours. I've run DNS lookups from a few different locations today and they all showed me 4 hours for TTL on the A record and MX records for northwestkayakanglers.com, with 24 hour TTLs on the NS and SOA records.
Here's one web-based tool that I used for a simple lookup.
https://mxtoolbox.com/SuperTool.aspx?action=a%3ano&run=toolpage#
Here's another that a DIG directed straight at the authoritative name servers for the domain.
http://www.kloth.net/services/dig.php
Here's the result:
; <<>> DiG 9 <<>> @ns2-lg.kayakfishingfrontiers.com northwestkayakanglers.com ANY
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26009
;; flags: qr aa rd; QUERY: 1, ANSWER: 9, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;northwestkayakanglers.com. IN ANY
;; ANSWER SECTION:
northwestkayakanglers.com. 14400 IN MX 50 aspmx3.googlemail.com.
northwestkayakanglers.com. 14400 IN MX 10 aspmx.l.google.com.
northwestkayakanglers.com. 14400 IN MX 20 alt1.aspmx.l.google.com.
northwestkayakanglers.com. 14400 IN MX 30 alt2.aspmx.l.google.com.
northwestkayakanglers.com. 14400 IN MX 40 aspmx2.googlemail.com.
northwestkayakanglers.com. 86400 IN SOA ns1.kayakfishingfrontiers.com. monitor.ace-host.net. 2017102302 3600 7200 1209600 86400
northwestkayakanglers.com. 86400 IN NS ns2.kayakfishingfrontiers.com.
northwestkayakanglers.com. 86400 IN NS ns1.kayakfishingfrontiers.com.
northwestkayakanglers.com. 14400 IN A 173.230.249.151
;; Query time: 109 msec
;; SERVER: 173.230.249.171#53(173.230.249.171)
;; WHEN: Tue Oct 24 00:22:23 2017
;; MSG SIZE rcvd: 303
-
Maybe you want to remove that post. It's a hacker's dream...
-
(https://uploads.tapatalk-cdn.com/20171023/7ec3c7273631a007f27ac2ae366a9a51.png)
It doesn’t like my photos. Does anyone know what I need to do different? I tried submitting them the same way I did before.
Sent from my iPhone using Tapatalk
-
Regardless of what you requested, TTL is currently 4 hours. I've run DNS lookups from a few different locations today and they all showed me 4 hours for TTL on the A record and MX records for northwestkayakanglers.com, with 24 hour TTLs on the NS and SOA records.
Here's one web-based tool that I used for a simple lookup.
https://mxtoolbox.com/SuperTool.aspx?action=a%3ano&run=toolpage#
Here's another that a DIG directed straight at the authoritative name servers for the domain.
http://www.kloth.net/services/dig.php
Here's the result:
; <<>> DiG 9 <<>> @ns2-lg.kayakfishingfrontiers.com northwestkayakanglers.com ANY
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26009
;; flags: qr aa rd; QUERY: 1, ANSWER: 9, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;northwestkayakanglers.com. IN ANY
;; ANSWER SECTION:
northwestkayakanglers.com. 14400 IN MX 50 aspmx3.googlemail.com.
northwestkayakanglers.com. 14400 IN MX 10 aspmx.l.google.com.
northwestkayakanglers.com. 14400 IN MX 20 alt1.aspmx.l.google.com.
northwestkayakanglers.com. 14400 IN MX 30 alt2.aspmx.l.google.com.
northwestkayakanglers.com. 14400 IN MX 40 aspmx2.googlemail.com.
northwestkayakanglers.com. 86400 IN SOA ns1.kayakfishingfrontiers.com. monitor.ace-host.net. 2017102302 3600 7200 1209600 86400
northwestkayakanglers.com. 86400 IN NS ns2.kayakfishingfrontiers.com.
northwestkayakanglers.com. 86400 IN NS ns1.kayakfishingfrontiers.com.
northwestkayakanglers.com. 14400 IN A 173.230.249.151
;; Query time: 109 msec
;; SERVER: 173.230.249.171#53(173.230.249.171)
;; WHEN: Tue Oct 24 00:22:23 2017
;; MSG SIZE rcvd: 303
I get that, but once I update things on my end, the rest is sort of out of my control, isn't it? If not, please educate me, because NCKA is taking a super long time.
-Allen
-
Maybe you want to remove that post. It's a hacker's dream...
That info is freely available to anyone at anytime. There's nothing private about it, and anyone with experience with online services and websites knows how to get the info easily. You can go to that site I linked or lots of others and see the same info yourself. It has to be public or it wouldn't be good for anything. :)
The public data there is part of how the internet works, and is how a web browser turns a URL like northwestkayakanglers.com into an IP address so that the computer can know what destination to request a web page from. The "SOA" record is the start of authority that knows about the domain (northwestkayakanglers.com). The "NS" records are the name servers that store the different types of DNS records for the domain. The "A" record is the host record that actually contains the IP address to go with the northwestkayakanglers.com hostname. The "MX" record is the mail exchange record that mail server around the world send mail to for email addresses that end with @northwestkayakanglers.com. The number (14400 or 86400) is the time to live (TTL) for the record in seconds, which is how long a DNS server other than the authoritative DNS server or a client is supposed to cache, or hold onto the results, from a DNS query for the domain. For that length of time, if someone tries to access that same URL again from the same client machine, the saved IP address from the previous DNS query is used as the IP address to contact. After that time expires, the next attempt to access the URL is supposed to cause a new query to the authoritative DNS servers to get a new IP address for the URL.
In this case, from the time that the IP address got changed it should have taken a maximum of whatever the TTL is for the "A" record before anyone trying to access the site got the new IP address instead of the old one. There are some types of clients and even some DNS servers around the world that are configured to cache results for a specific minimum amount of time, regardless of what the TTL specified by the authoritative DNS server said it should be. Those are the ones causing the delays in people being able to access the site on the new IP address after the migration.
-
I get that, but once I update things on my end, the rest is sort of out of my control, isn't it? If not, please educate me, because NCKA is taking a super long time.
-Allen
Was the TTL For the DNS hostname (A) record before also 4 hours, or was it much longer? If it was much longer, the records could have been cached from just before you changed it with whatever TTL they had specified at the time. If so, there's not much else to do other than wait. It's possible to reach out to major ISPs that have cached DNS records and have them flush their DNS cache. I have had to do it a couple times over the years in unusual circumstances with services for work (online service at Microsoft), but it's a royal pain to do and not worth it in almost all cases. If the TTL was only 4 hours before, then there's not much else to do but wait yet again unless you can find one of your hosting service's DNS servers not serving up the new IP address. I guess you could also push your DNS hosting provider to make sure that the TTL for the DNS record gets changed from 4 hours to 1 hour, but we're far enough past even the 4-hour TTL that the only remaining issues are going to be with systems that are misbehaving and not following the TTL specified by the DNS servers.
I'll check again when I get home from work (90 minutes from now or so) to see if it's still getting delayed. If it is, I'll check a little deeper into the DNS server configurations to make sure there's nothing wonky.
-
I get that, but once I update things on my end, the rest is sort of out of my control, isn't it? If not, please educate me, because NCKA is taking a super long time.
-Allen
Was the TTL For the DNS hostname (A) record before also 4 hours, or was it much longer? If it was much longer, the records could have been cached from just before you changed it with whatever TTL they had specified at the time. If so, there's not much else to do other than wait. It's possible to reach out to major ISPs that have cached DNS records and have them flush their DNS cache. I have had to do it a couple times over the years in unusual circumstances with services for work (online service at Microsoft), but it's a royal pain to do and not worth it in almost all cases. If the TTL was only 4 hours before, then there's not much else to do but wait yet again unless you can find one of your hosting service's DNS servers not serving up the new IP address. I guess you could also push your DNS hosting provider to make sure that the TTL for the DNS record gets changed from 4 hours to 1 hour, but we're far enough past even the 4-hour TTL that the only remaining issues are going to be with systems that are misbehaving and not following the TTL specified by the DNS servers.
I'll check again when I get home from work (90 minutes from now or so) to see if it's still getting delayed. If it is, I'll check a little deeper into the DNS server configurations to make sure there's nothing wonky.
All the sites use the same DNS servers and reference the same records file at kayakfishingfrontiers.com. Therefore, it was all switched over at the same time. All the other sites I run have come back up (for the most part, still a lingering issue with AOTY(s), but not DNS related), but for whatever reason, NCKA is taking it's own sweet time. The data center folks tell me to wait up to 48 hours.
-Allen
-
BTW JasonM, thanks so much for your insights and help. I really appreciate it. This is not something I do every day, if you can't tell. ::)
-Allen
-
FYI, NCKA just started working for me.
-Allen
-
It looks like the new IP address is propagating across the world, but there's still a misconfig with the DNS domain for northwestkayakanglers.com in the DNS zones on the primary and secondary servers themselves. The NS servers are configured incorrectly.
You can use this site to do the queries: http://www.kloth.net/services/dig.php
If you query domain "northwestkayakanglers.com" with server "localhost" or any of the global DNS .com root servers and query "any" you get these results, in addition to getting the "A" host record with the 173.230.249.151 address:
- SOA ns1-lg.kayakfishingfrontiers.com
- NS ns2-lg.kayakfishingfrontiers.com
- NS ns1-lg.kayakfishingfrontiers.com
Notice that the above data says that ns1-lg.kayakfishingfrontiers.com is the start of authority and ns1-lg and ns21-lg are the name servers. That means that if you query either of those server, you should see the same SOA and NS records. Unfortunately, you don't.
If you repeat the query above and ask the ns1-lg server directly by having domain"northwestkayakanglers.com" with server "ns1-lg.kayakfishingfrontiers.com" and query "any" to see what the ns1-lg server has for that DNS zone, you get this:
- SOA ns1.kayakfishingfrontiers.com
- NS ns2.kayakfishingfrontiers.com
- NS ns1.kayakfishingfrontiers.com
Notice that they are changed. That means that the DNS servers that are supposed to be the DNS servers for that domain think that other servers are the DNS servers for that domain. If the ns1 and ns2 servers gave the same replies to DNS queries, it wouldn't have any negative results. The problem is that the servers at ns1.kayakfishingfrontiers.com (173.230.249.230) and ns2.kayakfishingfrontiers.com (173.230.249.231) are refusing DNS queries and therefore the queries fail. The SOA and NS entries in the zone files for the northwestkayakanglers.com domain on the ns1-lg.kayakfishingfrontiers.com (68.171.217.196) and ns2-lg.kayakfishingfrontiers.com (68.171.217.197) servers need to be corrected. Until then, some queries may work but results will be inconsistent.
-
It looks like the new IP address is propagating across the world, but there's still a misconfig with the DNS domain for northwestkayakanglers.com in the DNS zones on the primary and secondary servers themselves. The NS servers are configured incorrectly.
You can use this site to do the queries: http://www.kloth.net/services/dig.php
If you query domain "northwestkayakanglers.com" with server "localhost" or any of the global DNS .com root servers and query "any" you get these results, in addition to getting the "A" host record with the 173.230.249.151 address:
- SOA ns1-lg.kayakfishingfrontiers.com
- NS ns2-lg.kayakfishingfrontiers.com
- NS ns1-lg.kayakfishingfrontiers.com
Notice that the above data says that ns1-lg.kayakfishingfrontiers.com is the start of authority and ns1-lg and ns21-lg are the name servers. That means that if you query either of those server, you should see the same SOA and NS records. Unfortunately, you don't.
If you repeat the query above and ask the ns1-lg server directly by having domain"northwestkayakanglers.com" with server "ns1-lg.kayakfishingfrontiers.com" and query "any" to see what the ns1-lg server has for that DNS zone, you get this:
- SOA ns1.kayakfishingfrontiers.com
- NS ns2.kayakfishingfrontiers.com
- NS ns1.kayakfishingfrontiers.com
Notice that they are changed. That means that the DNS servers that are supposed to be the DNS servers for that domain think that other servers are the DNS servers for that domain. If the ns1 and ns2 servers gave the same replies to DNS queries, it wouldn't have any negative results. The problem is that the servers at ns1.kayakfishingfrontiers.com (173.230.249.230) and ns2.kayakfishingfrontiers.com (173.230.249.231) are refusing DNS queries and therefore the queries fail. The SOA and NS entries in the zone files for the northwestkayakanglers.com domain on the ns1-lg.kayakfishingfrontiers.com (68.171.217.196) and ns2-lg.kayakfishingfrontiers.com (68.171.217.197) servers need to be corrected. Until then, some queries may work but results will be inconsistent.
I was going to say that exact same thing but JasonM beat me to it.
-
I think I may have found an easier place to explain the issue with northwestkayakanglers.com here.
http://www.dnsstuff.com/tools#dnsReport|type=domain&&value=northwestkayakanglers.com (http://www.dnsstuff.com/tools#dnsReport|type=domain&&value=northwestkayakanglers.com)
Here's the same site's analysis of norcalkayakanglers.com showing a version mismatch of the DNS zone files (and therefore likely different results depending on which DNS server a user query goes to):
http://www.dnsstuff.com/tools#dnsReport|type=domain&&value=norcalkayakanglers.com (http://www.dnsstuff.com/tools#dnsReport|type=domain&&value=norcalkayakanglers.com)
Note that the analysis is run again each time you load the page with the URLs I added above, so if you fix things and load the page again you can see if the fix replicated to the DNS servers and whether it worked to fix the issues.
-
Sure Nobaddays, but how about those mariners lol..pretty deep discussion. I just appreciate all the effort.
-
I think I may have found an easier place to explain the issue with northwestkayakanglers.com here.
http://www.dnsstuff.com/tools#dnsReport|type=domain&&value=northwestkayakanglers.com (http://www.dnsstuff.com/tools#dnsReport|type=domain&&value=northwestkayakanglers.com)
Here's the same site's analysis of norcalkayakanglers.com showing a version mismatch of the DNS zone files (and therefore likely different results depending on which DNS server a user query goes to):
http://www.dnsstuff.com/tools#dnsReport|type=domain&&value=norcalkayakanglers.com (http://www.dnsstuff.com/tools#dnsReport|type=domain&&value=norcalkayakanglers.com)
Note that the analysis is run again each time you load the page with the URLs I added above, so if you fix things and load the page again you can see if the fix replicated to the DNS servers and whether it worked to fix the issues.
But both site use the same NS's, however return different results above. How is that?
-Allen
-
They use the same nameservers but they are still different DNS zones (domains) with different configurations (zone files) for each zone.
-
Allen, it's not the most important thing, of course, but emails from the new server don't seem to be getting sent since the move.
-
Allen, it's not the most important thing, of course, but emails from the new server don't seem to be getting sent since the move.
Thanks. On it. The data center peeps assured me it wouldn't get turned off again. Uggh.
-Allen
-
Ok after trying to read the last 4 or so posts my head is pounding......All I can say is you guys are amazingly awesome, how much Tylenol and Jack Daniel’s does that take? :o
-
Ok after trying to read the last 4 or so posts my head is pounding......All I can say is you guys are amazingly awesome, how much Tylenol and Jack Daniel’s does that take? :o
Haha... All we've talked about is DNS. It's just a tiny part of what Allen does for this forum.
-
Ok after trying to read the last 4 or so posts my head is pounding......All I can say is you guys are amazingly awesome, how much Tylenol and Jack Daniel’s does that take? :o
Haha... All we've talked about is DNS. It's just a tiny part of what Allen does for this forum.
That’s an awful long paragraph that Nobaddays days quoted just to talk about 3 capital letters!
-
True , Shannon, but those 3 letters are at the heart of almost every site and web broswer used across the world.
Think of them as the card file part of the old Dewey Decimal system used in public libraries before they went digital. If they are mis-filed , or improperly duplicated, we end up with the problem Jason and Allen are talking about.
That's about the best this ex wrench turner turned C4ISR Tech can explain it. They might say something else.
-
Sorry for the unexpected downtime this weekend. The data center peeps were tweaking the DNS and Nameserver settings to address some lingering instabilities. You know, some of the stuff JasonM brought up in his informative posts. ;) But they actually did something wrong which brought everything down. :'(
-Allen
-
Sorry for the unexpected downtime this weekend. The data center peeps were tweaking the DNS and Nameserver settings to address some lingering instabilities. You know, some of the stuff JasonM brought up in his informative posts. ;) But they actually did something wrong which brought everything down. :'(
-Allen
Thanks for giving us a forum to hang out at! I'll continue hanging out here while NCKA is being improved further. ;-)
-
Sorry for the unexpected downtime this weekend. The data center peeps were tweaking the DNS and Nameserver settings to address some lingering instabilities. You know, some of the stuff JasonM brought up in his informative posts. ;) But they actually did something wrong which brought everything down. :'(
-Allen
Thanks for giving us a forum to hang out at! I'll continue hanging out here while NCKA is being improved further. ;-)
Looks like we're all back up now, including NCKA.
-Allen
-
Is the AOTY site fixed now? I still cant upload pictures. I dont get an error that says anything about why it wont upload. This is all I get.
-
I was having the same problem. I reduced my file sizes below 1 MB and the problem went away.
-
I was having the same problem. I reduced my file sizes below 1 MB and the problem went away.
Reducing the file size for your images is an almost universal fix for images not uploading on AOTY. I'm sorry it doesn't give a useful error message - I have no control over it.
-
As far as I can tell, there isn't a file size restriction currently in place.
-
As far as I can tell, there isn't a file size restriction currently in place.
It may not be a filesize restriction per se: it may be a timeout issue or something else, but I have regularly had larger images not upload and smaller images upload just fine.
-
As far as I can tell, there isn't a file size restriction currently in place.
It may not be a filesize restriction per se: it may be a timeout issue or something else, but I have regularly had larger images not upload and smaller images upload just fine.
I'll try resizing and let you know.
-
Yep resizing worked. I compressed them from 1.2M to about 240K and then they uploaded.
-
I don't know if anyone else is experiencing DNS issues (i.e. the server can not be found). The NWKA and AOTY sites are up and running, but your DNS server (the webservice that converts URLs to IP addresses) just has a bad record for NWKA. In theory this should work it's way out in time, but it has been days and I've begun to get frustrated. I went ahead and switched to using Google's public DNS servers. Now I have not problem getting onto NWKA.
Here's a link for instructions..
https://developers.google.com/speed/public-dns/docs/using
-
I don't know if anyone else is experiencing DNS issues (i.e. the server can not be found). The NWKA and AOTY sites are up and running, but your DNS server (the webservice that converts URLs to IP addresses) just has a bad record for NWKA. In theory this should work it's way out in time, but it has been days and I've begun to get frustrated.
I'm having the same issue on my PC and occasionally on my phone. I don't think my nerd level is high enough to attempt the fix you suggested. Any other suggestions.
-
Allen, the incorrect configuration on the name servers for northwestkayakanglers.com is still there. I've been having intermittent issues accessing the site due to DNS lookup failures, and I'm betting that many others are still having trouble. This is not a problem with other DNS servers around the internet caching DNS results longer than they should, and won't ever eventually fix itself. If you run the report, you'll see that ns1 and ns2 are still in the list of name servers but lookups for those hostnames fail so no queries can get sent to them. When users try to access the forum, they are going to occasionally try to send the DNS queries to those servers but they won't be able to find the servers to send them queries and won't be able to successfully resolve the site's hostname into an IP address.
http://www.dnsstuff.com/tools#dnsReport|type=domain&&value=northwestkayakanglers.com (http://www.dnsstuff.com/tools#dnsReport|type=domain&&value=northwestkayakanglers.com)
You can use the report for the NorCalKayakAnglers forum to compare results, and to show the hosting provider.
http://www.dnsstuff.com/tools#dnsReport|type=domain&&value=norcalkayakanglers.com (http://www.dnsstuff.com/tools#dnsReport|type=domain&&value=norcalkayakanglers.com)
The DNS lookups for both sites give the same 173.230.249.151 IP address, so I assume that both sites are on the same server and the server software just uses the host header to know which site to serve content from. If the hosting provider doesn't seem to be the most knowledgeable with taking care of this, just tell them that they should go to the the ns1-lg and ns2-lg DNS servers and make the zone file for "northwestkayakanglers.com" look exactly like the zone file for "norcalkayakanglers.com" except for the domain name. That may be as simple as just changing "ns1" to "ns1-lg" and "ns2" to "ns2-lg" everywhere in the zone files so that there are no references to ns1.kayakfishingfrontiers.com or ns2.kayakfishingfrontiers.com in the zone file, but it should be very easy for them to just make the zone file for this domain look exactly like the zone file for the working site except for the domain name.
This shouldn't be that difficult for the hosting provider to fix. The name servers are running Bind on Redhat, specifically 9.8.2rc1-RedHat-9.8.2-0.62.rc1.el6_9.4, (which is a security risk that they actually respond to the query on what software they're running to make them easier targets for exploits) so they don't appear to be running some deeply customized distributed solution that's hard to manage. Let me know if you need me to work with them directly and explain things. I'm off work on vacation through next week and should have time.
-
Allen, the incorrect configuration on the name servers for northwestkayakanglers.com is still there. I've been having intermittent issues accessing the site due to DNS lookup failures, and I'm betting that many others are still having trouble. This is not a problem with other DNS servers around the internet caching DNS results longer than they should, and won't ever eventually fix itself. If you run the report, you'll see that ns1 and ns2 are still in the list of name servers but lookups for those hostnames fail so no queries can get sent to them. When users try to access the forum, they are going to occasionally try to send the DNS queries to those servers but they won't be able to find the servers to send them queries and won't be able to successfully resolve the site's hostname into an IP address.
http://www.dnsstuff.com/tools#dnsReport|type=domain&&value=northwestkayakanglers.com (http://www.dnsstuff.com/tools#dnsReport|type=domain&&value=northwestkayakanglers.com)
You can use the report for the NorCalKayakAnglers forum to compare results, and to show the hosting provider.
http://www.dnsstuff.com/tools#dnsReport|type=domain&&value=norcalkayakanglers.com (http://www.dnsstuff.com/tools#dnsReport|type=domain&&value=norcalkayakanglers.com)
The DNS lookups for both sites give the same 173.230.249.151 IP address, so I assume that both sites are on the same server and the server software just uses the host header to know which site to serve content from. If the hosting provider doesn't seem to be the most knowledgeable with taking care of this, just tell them that they should go to the the ns1-lg and ns2-lg DNS servers and make the zone file for "northwestkayakanglers.com" look exactly like the zone file for "norcalkayakanglers.com" except for the domain name. That may be as simple as just changing "ns1" to "ns1-lg" and "ns2" to "ns2-lg" everywhere in the zone files so that there are no references to ns1.kayakfishingfrontiers.com or ns2.kayakfishingfrontiers.com in the zone file, but it should be very easy for them to just make the zone file for this domain look exactly like the zone file for the working site except for the domain name.
This shouldn't be that difficult for the hosting provider to fix. The name servers are running Bind on Redhat, specifically 9.8.2rc1-RedHat-9.8.2-0.62.rc1.el6_9.4, (which is a security risk that they actually respond to the query on what software they're running to make them easier targets for exploits) so they don't appear to be running some deeply customized distributed solution that's hard to manage. Let me know if you need me to work with them directly and explain things. I'm off work on vacation through next week and should have time.
Thanks Jason. The data center guys keep messing this up. I have 1 server for NCKA and NWKA. But I have another server for other stuff. NCKA and NWKA server use ns1-lg and ns2-lg, and the other server uses ns1 and ns2. This is like the 4th time they've swapped the 2.
-Allen
-
Time to get my old postings organized and work on uploading them. THANK YOU for the fixes, I know this stuff can be a hole in the space-time continuum.
-
I'm getting complete DNS failure from all devices for this forum currently. I'm not sure if anyone else will be able to get to the forum right now to read this since I had to add an entry for www.northwestkayakanglers.com to my hosts file and point it to the server IP address (173.230.249.151) so I could get here.
A quick investigation shows that the root DNS servers are pointing to ns1-lg and ns2-lg, but those servers are refusing DNS queries for the northwestkayakanglers.com domain. I'm hoping that this is because the zone files for norcalkayakanglers.com are being copied and updated for northwestkayakanglers.com domain, so all will be right with the world once that's complete.
Edit at 9:58 PST: Right as I posted this, things started working normally even without using my hosts file entry. I just ran a new DNS check on the domain and it looks great! Well done! :)
-
I'm glad you guys understand DNS stuff much deeper than I do!
-
I'm getting complete DNS failure from all devices for this forum currently. I'm not sure if anyone else will be able to get to the forum right now to read this since I had to add an entry for www.northwestkayakanglers.com to my hosts file and point it to the server IP address (173.230.249.151) so I could get here.
A quick investigation shows that the root DNS servers are pointing to ns1-lg and ns2-lg, but those servers are refusing DNS queries for the northwestkayakanglers.com domain. I'm hoping that this is because the zone files for norcalkayakanglers.com are being copied and updated for northwestkayakanglers.com domain, so all will be right with the world once that's complete.
Edit at 9:58 PST: Right as I posted this, things started working normally even without using my hosts file entry. I just ran a new DNS check on the domain and it looks great! Well done! :)
Yeah, I noticed it was still effed up and told them to just use a copy of the NCKA zone file.
-Allen
-
So is everyone good now? I gotta start planning the upgrades now ...
-Allen
-
For the last couple days I have only been able to access NCKA and NWKA intermittently. Sometimes I can’t access either, sometimes one or the other works, and sometimes both are accessible.
I’ve tried clearing my cache, it didn’t help.
Any ideas?
-
For the last couple days I have only been able to access NCKA and NWKA intermittently. Sometimes I can’t access either, sometimes one or the other works, and sometimes both are accessible.
I’ve tried clearing my cache, it didn’t help.
Any ideas?
Any error messages?
-Allen
-
For the last couple days I have only been able to access NCKA and NWKA intermittently. Sometimes I can’t access either, sometimes one or the other works, and sometimes both are accessible.
I’ve tried clearing my cache, it didn’t help.
Any ideas?
Any error messages?
-Allen
Only a couple times, it's usually my ISP's search landing page on wifi or a server cannot be reached on my cellular data.
Right now I can reliably reach nwka and cannot reach ncka. that goes for my phone and my laptop, both on my wifi (suddenlink) and my data carrier (verizon).
-
Now I can access both.
I didn't do anything differently.
-
I haven't been able to upload anything today or yesterday. I resized the two pictures to 999kb also in case there was a size limit or something. I'm getting this message each time I try and submit a new fish.
-
I haven't been able to upload anything today or yesterday. I resized the two pictures to 999kb also in case there was a size limit or something. I'm getting this message each time I try and submit a new fish.
You might have to go smaller. I had to compress mine to about 200k if I remember correctly.
-
I'll give it a shot. They posted just fine in regular resolution on the forum itself, just not AOTY submission.