This month's newsletter is brought to you by …
Welcome to the May 2016 edition of our community newsletter, the DaniWeb Digest
This time last year the newsletter kicked off with mention that people were posting their questions on DaniWeb in the wrong places. With the revamped interface and structure of our community, we could understand that some members may have got confused when the changes first went live but really shouldn't be problematical any longer. Which turns it into a problem for everyone else when they are posted where they shouldn't be, if you see what we mean. After all, by not posting in the appropriate forum you are not only adding to the workload of the volunteer moderating team (who scan the whole of DaniWeb and move such things manually to the correct forum) but you are running the risk of not getting the help you are looking for. At the very least that help will be delayed as people reading the Apple Hardware and Devices forum are not necessarily the same ones who read the C++ forum and have the knowledge to answer C++ coding queries. Just dumping a question in the first place you find yourself makes as much sense as buying an airplane ticket to Las Vegas when you want to go to New York. All that said, how do you ensure you get the best out of the DaniWeb community when asking us for help? We can help you with that...
Search first ask second
Before you post your question, use the DaniWeb search function to check if someone has not only already asked the same thing but importantly whether the answer you seek is already sitting there waiting for you to find it rather than have to wait for someone to answer it all over again.
Use the forum dropdown and use tags
When composing your question you will be asked where it should go, by way of that forum dropdown right next to the title box. Use it wisely as you want it to sit where it will be before the right experts. If you really are not sure, and even if you are, make good use of the DaniWeb tagging system to help those searching for similar problems to find yours. So, if your question is code related but you can't find the language listed in the forums, for example, then just post it to the Software Development top level category instead. However, ensure that you use the tagging system to enter keywords that will highlight the query for our community to find and answer. Tags also help when a question covers multiple possible forums. Pick the best fit, and tag for the others. So, another example, if posting a question in the PHP forum about not being able to connect to MySQL, then use a MySQL tag so your post gets exposure in the MySQL forum when anyone does a tag search on that keyword.
Think about that title
The title is the first thing most people will see, and if they are quickly scanning through forum posts then a poor title that lacks any meaningful information is likely to get overlooked. Make sure that the title is concise and relevant to the question you are asking, don't be generic and don't just say 'help!'
In the same way that your post title needs to be descriptive, so does your post itself. However, the difference between the two is that your question should be as detailed as possible. If you are asking for help with code, post the code you have already so we can see what you've done and where the problem is (remember we won't do your homework for you, but we will help point you in the right direction if you've made the effort) and if it's a non-code problem then make sure you give us as much information as possible to enable us to help you out.
The small question
Welcome to a new feature of the DaniWeb Digest where we address one of those questions that have a really easy answer. This month we look at the small question of signature files.
We all like to say something about ourselves, beyond the impression given by our contributions to the community of course. That's where the signature file comes in, which enables members to say something and include a link to their website or somewhere else interesting if they wish. The small question this month is courtesy of a new member who was concerned that they couldn't link to their website in their signature, and that their signature was invisible on some posts and not others. The first part, the link not working thing, was really easy to answer because the member in question had forgotten to include the http:// part of the URL when composing their signature in the first place. The second part, funnily enough, is also easy to answer: signatures only display when you start a discussion topic, and are not displayed with the replies. When DaniWeb switched to the new layout, it was determined that signatures were taking up too much screen estate, especially in long discussions, and so the 'Original Poster Only' solution was imposed.
The big question
Yes, it's another new regular feature of our revamped newsletter: the big question. How does this differ from the small question, you may ask, well it's all a matter of scale. The big question will address an issue that the DaniWeb community has been talking about and give you the opportunity to join in and add your weight to the debate.
The big question this month has a title of 'Access Point Won't go out to the internet' and was posed by Drew29 who explained that following a server migration for a small business the Access Point (AP) went offline despite working fine beforehand. "We reset and reconfigured it to received the appropriate IP settings" Drew29 said "Users are able to connect to it just fine, however when it comes time to go out to the internet, we keep getting a message about DNS cannot be found." Drew could ping the gateway, other machines on the network, and even 126.96.36.199 (Google's DNS), but not a website. So assumed the issue had to be DNS related and asked for help...
rproffitt was first up, asking for client IP settings to move forward with the helping. Unfortunately, he was unable to find how the client resolves addresses as the client's DNS entry wasn't obvious in the information provided. After a little to-and-fro, Drew posted that the first set of ip addresses shown were from the server/domain controller, with an ip of 192.168.0.3. and because its also the DNS server its DNS is 127.0.0.1. Every other machine on the network is assigned 192.168.0.3 for the DNS, Drew explained.
CimmerianX then joined the discussion to suggest that "From server at 192.168.0.3. it is the DNS for the network. Thus it should also have Forwarders setup in it's DNS config so that anything it can't resolve gets sent out to another 3rd party dns server (i.e. 188.8.131.52 or 184.108.40.206). From the client, if you can ping something internally, but dns fails when going to an external site, then the Forwarders are probably incorrect." CimmerianX also provided a NSLOOKUP example to test the DNS choices.
Drew29 replied that, regarding the nslookup "I was working with Ubiquity support exclusively for a while, as I thought the issue was with them. They ran a couple of NSLOOKUP commands and saw that the AP was working fine with DNS. They concluded the issue is with the DNS server." However, he agreed to try the provided NSLOOKUP command from the server which CimmerianX said he'd bet was where the problem lay.
As we go to press with the newsletter, this is where the big question sits: "I tried the forwarders and that didn't work. I put in all the public DNS that were recommended, 220.127.116.11, 18.104.22.168 and 22.214.171.124. I think the DNS component of the server might be corrupted. I was thinking of removing the DNS entirely and re-add it again on the server. This server was added to an existing forest, so I think some of the DNS properties from the old server is still playing a role somehow. The old server has been taken down. If I deleted the current DNS settings and configured a new one, would that make a difference? Somehow I think it will. However, I'm not sure what the consequences of deleting the current settings will be..."
Why not check out the full thread and add your help here if you can?