The widening gyre of DNS records...
Dec. 28th, 2014 07:07 pmSo there I was, plodding through the last thousand words of a 4,000-word translation when I happened to notice a "Delivery Status Notification (Failure)" in my work Gmail account.
As it turned out, the failure was due to an attempt to send mail to my primary work email account.
Upon seeing this, I recalled the words of the manager of a hotel I once stayed at in Ludwigshafen (Das ist nicht gut!) and immediately realized the source of my problem.
Over the past several days, I have been reconfiguring some domains that I use, and as part of the reconfiguration, my work domain became the domain assigned to a hosting account. This basically meant that all of the IP addresses associated with those domains (including my work domain) were changed.
At first, the problem with not being able to call these domains up in a browser were due to my not having properly configured the associated "nameservers," which are the machines that provide the essential link between a name (like 'fubar.com') and the actual IP address where the files for 'fubar.com' are stored.
After allowing the requisite time for the nameserver changes to propagate throughout the Internet, I was still having problems, but a chat with a tech support rep helped fix that. However, fixing the problem broke the configuration I had set up to route mail to a certain webmail provider I've been using for about a decade.
I was frankly at something at a loss to figure out how to solve my problem when I sort of came up with a Gordian knot approach: forget the setup with my webmail provider and just set up a user email account in my domain.
As far as I can tell, I'm still getting my mail at my work address (the acid test will occur tomorrow, if and when folks start sending me stuff). The only down side I can see is having to create a new email account in Thunderbird, but considering how many I have there already, there's very little performance impact.
I'm sure there will be some unexpected 'gotchas' as things progress, but nothing I can't handle.
Now, to get back to the translation... :)
As it turned out, the failure was due to an attempt to send mail to my primary work email account.
Upon seeing this, I recalled the words of the manager of a hotel I once stayed at in Ludwigshafen (Das ist nicht gut!) and immediately realized the source of my problem.
Over the past several days, I have been reconfiguring some domains that I use, and as part of the reconfiguration, my work domain became the domain assigned to a hosting account. This basically meant that all of the IP addresses associated with those domains (including my work domain) were changed.
At first, the problem with not being able to call these domains up in a browser were due to my not having properly configured the associated "nameservers," which are the machines that provide the essential link between a name (like 'fubar.com') and the actual IP address where the files for 'fubar.com' are stored.
After allowing the requisite time for the nameserver changes to propagate throughout the Internet, I was still having problems, but a chat with a tech support rep helped fix that. However, fixing the problem broke the configuration I had set up to route mail to a certain webmail provider I've been using for about a decade.
I was frankly at something at a loss to figure out how to solve my problem when I sort of came up with a Gordian knot approach: forget the setup with my webmail provider and just set up a user email account in my domain.
As far as I can tell, I'm still getting my mail at my work address (the acid test will occur tomorrow, if and when folks start sending me stuff). The only down side I can see is having to create a new email account in Thunderbird, but considering how many I have there already, there's very little performance impact.
I'm sure there will be some unexpected 'gotchas' as things progress, but nothing I can't handle.
Now, to get back to the translation... :)