| Recorded | |||||
|---|---|---|---|---|---|
| 02/20/2022 | |||||
| 02/26/2022 | |||||
| 02/26/2022 | |||||
| 05/21/2022 | |||||
| 05/25/2022 | |||||
| 05/25/2022 | |||||
| 06/04/2022 | |||||
| 06/05/2022 |
| A couple of weeks ago I was talking with a fellow IT guy who had recently built his own website, using the WordPress platform. He was explaining to me that he needed to include a comment feature to his website in order to add domain name IP to it; however, he ran into some difficulty. His problem was not with the comment feature; rather, it was with the way he handled the " Register" button on his website. He was having trouble inserting the IP address of the domain name in the " Register" form. It turns out that WordPress doesn't have a built-in mechanism for doing this. His problem wasn't necessarily with WordPress but with the way he integrated WordPress with the system. He used a third party service to provide WordPress support and install some of the more advanced features. One of these included the chkconfig boot service. This is a very useful feature for a blog server but unfortunately it doesn't work with the IP address type. The chkconfig boot service is provided by the "systemd" service which is part of the Linux kernel. Systemd is a utility service that controls the operation of a Linux system. Among its many duties is the ability to set up and configure the Linux machine in question. Among its abilities is the ability to establish a file timer, a process that helps the system remain as snappy and responsive as possible. In addition, the service also provides support for multiple MySQL databases and has support for setting up process management task queues. If you're familiar at all with setting up and running Linux, you probably already understand how useful this tool is. The problem was that this particular feature didn't work when WordPress started up. WordPress had been installed as a dynamic or open source program and was configured with the use of a template. As the blog started to be used, the file hosting service experienced an influx of traffic. All of the pages on the blog used the same domain name but each one had its own entry point. Because there were several processes going on at once, WordPress couldn't see any of them and hence had no way to know which ones were running and which ones were resting. I simplified the problem by adding a simple script to load the data at a certain URL and then rewrite the page automatically each time the domain name system responded. I added a new feature to the WordPress admin area where the user could specify an arbitrary number of alternate servers to use for their session. By setting up a few additional plug-ins, I was able to make this simple process go live. One of these was called "iterative abfrage". This simple Perl script added a new feature to the WordPress administration area where the user specified an arbitrary number of servers to use for the domain name system's session. It was a quick and easy fix. Using that application, I was able to register names using wildcard DNS entries and have the names reflect the IP addresses. Because Google's Resolver tool was not yet available, I had to find another way to resolve the domain name. I used the same wildcard DNS entries for the names of the domains and sub-domains. In the mean time, I had started working on my rewrite project. The rewrite project was related to the Google dns ressource project that I was already working on. I had been having some difficulty getting the Google dns ressource to work with my reverse lookup domain name lookups. However, after making some changes to the Google dns ressource application, I was able to get the names resolve properly and obtain my reverse lookup domain name information. From that point on, I could easily log into my domain name account at Google and check to see what the IP address was and how I matched up to the IP address of the other party. Also, from that point on, I was able to generate reports and perform analysis on the data that I had gathered. In essence, my experience at that point in time has been a pleasant one dealing with the Google dns ressource. Overall, my experience with the Google dns Resolver was enjoyable. It was a pleasant change from the domain name verification processes that I had been experiencing previously. Like I had mentioned earlier, there were some minor issues that I had to work through, but overall, it did well. In summary, I was satisfied with the service that I got and would recommend it to anyone who may need to use an IP address to access the Internet. |